StackPrism

steven-tey/precedent dependency check

View on GitHub (opens in a new tab)

steven-tey/precedent: 3 critical findings, fixed by upgrading next to 15.5.24, @clerk/nextjs to 5.7.6 and next to 16.4.2. Plus 10 warnings.

Last checked against GitHub, OSV.dev, deps.dev, CISA KEV, FIRST EPSS, npm and endoflife.date.

13 things your coding agent doesn’t know about this repo

steven-tey/precedent on GitHub (opens in a new tab)

3 critical10 warnings19 low priority

One task with every fix, most urgent first, the file to change and why. Paste it into Claude Code, Cursor or Codex.

Checked 35 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.

StackPrism dependency check badge for steven-tey/precedent
[![StackPrism](https://stackprism.ai/badge/github/steven-tey/precedent.svg)](https://stackprism.ai/check/github/steven-tey/precedent)

What next

Get alerts when this changesConnect GitHub (free) and StackPrism re-checks this repo every day, with an in-app alert when a new critical finding turns up.Connect GitHubSee the whole stack as a diagramMap the repo into an architecture diagram with health on every part, then hand your coding agent a brief to build from.Map this repo

Want your agent to check before it adds a package? Connect Claude Code, Cursor or Codex to StackPrism. Setup steps

Ask Prism Agent about steven-tey/precedent

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.

Ask Prism AgentCheck another repo

How this report works

StackPrism read package.json and pnpm-lock.yaml from the default branch of steven-tey/precedent and checked its 35 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.