ixartz/SaaS-Boilerplate dependency check
ixartz/SaaS-Boilerplate: 1 critical finding, fixed by upgrading next to 16.3.8. 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
ixartz/SaaS-Boilerplate on GitHub (opens in a new tab)
1 critical2 warnings44 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
17 known vulnerabilities in next 16.2.9
EPSS: top 19%8 rated high or critical. Most serious: CVE-2026-75604, Next.js: Unauthenticated Remote Code Execution on windows-hosted servers. Upgrading to 16.3.8 fixes all of them.
- WarningVulnerabilitypackage.json
CVE-2026-73653 in @vitest/browser 4.1.9
EPSS: top 45%Dev only@vitest/browser: Browser Mode provider commands bypass the file-access permission gate. Fixed in 4.1.10.
- WarningVulnerabilitypackage-lock.json
CVE-2026-104850 in @modelcontextprotocol/sdk 1.29.0
EPSS: top 94%Dev onlyMCP TypeScript SDK: OAuth client could send credentials to an authorization server chosen by the MCP server. Fixed in 1.31.0.
Checked 400 packages from package.json and package-lock.json 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/ixartz/saas-boilerplate)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 ixartz/SaaS-Boilerplate
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 package-lock.json from the default branch of ixartz/SaaS-Boilerplate and checked its 400 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.