vercel/commerce dependency check
Next.js Commerce
vercel/commerce: 1 critical finding, fixed by upgrading next to 16.1.5. Plus 2 warnings.
Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date.
3 things your coding agent doesn’t know about this repo
vercel/commerce on GitHub (opens in a new tab)
1 critical2 warnings11 low priority
One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.
- CriticalVulnerabilitypackage.json
3 known vulnerabilities in next 15.6.0-canary.60
EPSS: top 16%1 rated high or critical. Most serious: CVE-2026-23864, Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components. Upgrading to 16.1.5 fixes all of them.
15.6.0-canary.6016.1.5View advisory, source: OSV.dev (opens in a new tab)Upgrade notes (opens in a new tab) - WarningVulnerabilitypackage.json
4 known vulnerabilities in postcss 8.5.3
EPSS: top 53%Dev onlyMost serious: CVE-2026-45623, PostCSS: Arbitrary file read and information disclosure via attacker-controlled sourceMappingURL in CSS comments. Upgrading to 8.5.23 fixes all of them.
- WarningEnd of lifepackage.json
Next.js 15 reaches end-of-life in 4 days
Support ends 2026-10-21. Plan an upgrade to Next.js 16 LTS.
Checked 19 packages from package.json and pnpm-lock.yaml against:
Add this badge to your README
It shows today’s result and links to this report, so anyone opening the repo sees what needs fixing.
[](https://stackprism.ai/check/github/vercel/commerce)What next
Want your agent to check before it adds a package? Connect Claude Code, Cursor or Codex to StackPrism. Setup steps
Ask Prism Agent about vercel/commerce
Map the repo (free) and ask what to fix first, whether an upgrade is safe, or what breaks if a service goes down. Prism Agent checks live sources before it answers.
How this report works
StackPrism read package.json and pnpm-lock.yaml from the default branch of vercel/commerce and checked its 19 packages against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date. Nothing was installed or run, and there’s no AI in the findings: each one comes from a source you can open.
Vulnerabilities come from OSV.dev, with known-exploited ones from CISA marked and listed first. Runtimes, frameworks and base images are checked against endoflife.date, and packages against their registry for deprecations and major versions you’ve fallen behind. The fix task above lists every change with the file to edit.
This page refreshes every few hours; after you push a fix, “Check again” runs it now. Only the repo’s root is read. For an app in a sub-folder, paste the folder’s link into the dependency check, and for a private repo, connect GitHub.