Quickstart
Run radius on your project in under a minute.
You need Node.js 22.12 or later and a JavaScript or TypeScript project.
Run it in your project
cd your-project
npx dep-radiusradius checks every dependency that has an update. The first run downloads what it needs. Later runs use the cache and are fast.
Read the answers
- Quiet packages are listed on one line. You can merge them.
- Review and blocked packages each get a short block: the release notes that affect your code, and your lines. The most important ones come first.
Look at one package, or one exact version
npx dep-radius zod # only this package
npx dep-radius zod@4.6.0 # this exact target
npx dep-radius --latest # the newest version, even across majorsAlready upgraded? Ask what changed
Ran npm update, or merged a bot's pull request? Compare with a commit:
npx dep-radius --since HEAD # changes not committed yet
npx dep-radius --since main # everything this branch changed--since doesn't need anything installed. It reads the lockfile at that commit.
Something broke after some upgrades? See which upgrade broke this?
Install it for good (optional)
npx is enough. If you run it often:
npm install --save-dev dep-radiusThen use radius (or dep-radius, same thing) in your scripts.
Give it a GitHub token (recommended)
Release notes mostly come from GitHub. Without a token, GitHub allows 60 requests an hour. With one,
5000. radius finds GITHUB_TOKEN, GH_TOKEN, or your gh login by itself.
gh auth login # once, and radius finds itUse the exit code
| Code | Verdict |
|---|---|
0 | quiet: nothing your code uses changed |
1 | review: at least one package needs a look |
2 | blocked: an export you use was removed |
3 | radius itself failed (bad option, no git history for --since) |
The exit code is the worst answer across all packages. So npx dep-radius zod && npm run deploy only
deploys when zod is quiet.