Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
151 changes: 78 additions & 73 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

8 changes: 4 additions & 4 deletions package.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,16 +26,16 @@
"@dnd-kit/core": "^6.3.1",
"clsx": "^2.1.1",
"cmdk": "^1.1.1",
"framer-motion": "^14.3.0",
"framer-motion": "^14.9.0",
"idb": "^8.0.4",
"lucide-react": "^1.58.0",
"next": "16.4.2",
"lucide-react": "^1.65.0",
"next": "16.4.3",

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[P2] next 16.4.3 is inside published vulnerable ranges

The production pin is next 16.4.3, which is inside the ranges of GHSA-7qx7-33qx-rqx2, GHSA-pc58-hwjq-p385, GHSA-f3mh-rxg3-f5g2, GHSA-rhh4-g77r-r9qj, GHSA-vvgp-ww4w-46vf, GHSA-vc7v-qv4w-wrv8, and GHSA-mfr8-8qww-v76h (each covers versions through 16.4.4). This repo has no use cache, no edge runtime, and no next/image, and its route handlers rebuild JSON, but next start still ships the image optimizer those advisories mark vulnerable.

How to see it: next@16.4.3 matches >= 16.0.0, <= 16.4.4 on GHSA-7qx7-33qx-rqx2. next@16.4.5 does not, and the 16.4.5 release lists these fixes.

Smallest fix: set next to 16.4.5 and refresh the lockfile entries for next, @next/env, and the @next/swc-* packages.

"react": "19.3.1",
"react-dom": "19.3.1",
"react-server-dom-webpack": "^19.3.1",
"server-only": "^0.0.1",
"tailwind-merge": "^3.7.0",
"zustand": "^5.0.15"
"zustand": "^5.0.16"
},
"devDependencies": {
"@cloudflare/vite-plugin": "^1.64.0",
Expand Down
Loading