timlrx/tailwind-nextjs-starter-blog dependency check
timlrx/tailwind-nextjs-starter-blog: 4 critical findings, each with a fixed version. Plus 1 warning.
Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date.
5 things your coding agent doesn’t know about this repo
timlrx/tailwind-nextjs-starter-blog on GitHub (opens in a new tab)
4 critical1 warning19 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
28 known vulnerabilities in next 15.5.12
EPSS: top 19%13 rated high or critical. Most serious: CVE-2026-75604, Next.js: Unauthenticated Remote Code Execution on windows-hosted servers. Upgrading to 15.5.27 fixes all of them.
- CriticalVulnerabilitypackage.json
4 known vulnerabilities in postcss 8.5.6
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
2 known vulnerabilities in image-size 2.0.2
EPSS: top 65%2 rated high or critical. Most serious: CVE-2025-71329, image-size: JXL and HEIF parsers allow denial of service through infinite loops. Upgrading to 2.0.3 fixes all of them.
- 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 6 days
Support ends 2026-10-21. Plan an upgrade to Next.js 16 LTS.
Checked 51 packages from package.json and yarn.lock 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/timlrx/tailwind-nextjs-starter-blog)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 timlrx/tailwind-nextjs-starter-blog
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 yarn.lock from the default branch of timlrx/tailwind-nextjs-starter-blog and checked its 51 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.