nextjs/saas-starter dependency check
nextjs/saas-starter: 4 critical findings, each with a fixed version. Plus 5 warnings.
Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date.
9 things your coding agent doesn’t know about this repo
nextjs/saas-starter on GitHub (opens in a new tab)
4 critical5 warnings14 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
4 known vulnerabilities in next 15.6.0-canary.59
EPSS: top 3%2 rated high or critical. Most serious: CVE-2025-67779, Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up. Upgrading to 16.1.5 fixes all of them.
15.6.0-canary.5916.1.5View advisory, source: OSV.dev (opens in a new tab)Upgrade notes (opens in a new tab) - CriticalVulnerabilitypackage.json
4 known vulnerabilities in postcss 8.5.3
EPSS: top 53%2 rated high or critical. Most 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.
- CriticalVulnerabilitypackage.json
CVE-2026-39356 in drizzle-orm 0.43.1
EPSS: top 66%Drizzle ORM has SQL injection via improperly escaped SQL identifiers. Fixed in 0.45.2.
- CriticalEnd of lifepackage.json
Tailwind CSS 4.1 is end-of-life
Support ended 2026-02-18. No more security fixes — upgrade to Tailwind CSS 4.3 (4.3.3).
- 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.
- WarningOutdatedpackage.json
@types/node 22.15.18 is 4 major versions behind
Latest release is 26.6.5.
- WarningOutdatedpackage.json
dotenv 16.5.0 is 2 major versions behind
Latest release is 18.0.8.
- WarningOutdatedpackage.json
stripe 18.1.0 is 5 major versions behind
Latest release is 23.0.0.
- WarningOutdatedpackage.json
typescript 5.8.3 is 2 major versions behind
Latest release is 7.0.2.
Checked 27 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/nextjs/saas-starter)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 nextjs/saas-starter
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 nextjs/saas-starter and checked its 27 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.