Dependency Health
Audit dependency health, upgrade risk, security alerts, and maintenance load from the manifests, lock files, advisory reports, and release history the user supplies.
Sample result
How it works
What Dependency Health does
Separates direct from transitive and runtime from build or dev exposure, classifies the version gap by semver jump, checks each advisory against the resolved version and its fix path, rates maintenance signals (active, slow, stale, abandoned), applies hard gates before a points score, batches upgrades by risk, estimates ongoing maintenance load, and recommends patch now, schedule, pin, replace, remove, or accept with an expiry.
Use it when
Someone asks for a dependency audit, whether packages are outdated or abandoned, how risky an upgrade is, what to do about a pile of security alerts, or how much upkeep dependencies cost.
Use something else for
Turning findings into a ranked backlog, a cloud infrastructure review, or vetting an imported skill's source.
Inputs and results
What goes in, what comes back
- You give
A short brief describing what you need
Add a specialist method to the work.
- You get
Dependency health report, upgrade plan, advisory review and maintenance load estimate
The method guides the work with your files and context.
- You check
The sources and open questions
Review the output against your brief.
Questions and answers
Questions about Dependency Health
Updated Oct 20, 2026.
What does Dependency Health do?
Audit dependency health, upgrade risk, security alerts, and maintenance load from the manifests, lock files, advisory reports, and release history the user supplies. Separates direct from transitive and runtime from build or dev exposure, classifies the version gap by semver jump, checks each advisory against the resolved version and its fix path, rates maintenance signals (active, slow, stale, abandoned), applies hard gates before a points score, batches upgrades by risk, estimates ongoing maintenance load, and recommends patch now, schedule, pin, replace, remove, or accept with an expiry. Use when someone asks for a dependency audit, whether packages are outdated or abandoned, how risky an upgrade is, what to do about a pile of security alerts, or how much upkeep dependencies cost. Do not use for turning findings into a ranked backlog (use maintenance-backlog), a cloud infrastructure review (use audit-cloud-infrastructure), or vetting an imported skill's source (use import-provenance-checker).
Who is Dependency Health for?
It is designed for engineering leads, application developers, platform teams and security reviewers.
What do I need to use it?
Nothing extra is needed. Sign in to Relay to run it with your own files and context.
What does Dependency Health produce?
Dependency health report, upgrade plan, advisory review and maintenance load estimate. Results come back with their sources and any open questions for you to check before anything is used.
How much does Dependency Health cost?
It is free to use. Paid model usage, if any, is shown before a run.
Can an AI agent use it?
Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.
Details
Trust, access and technical details
Trust and access
- Visibility
- Public: anyone can view
- Status
- Published and maintained
- Pricing
- Free
- cmvgt7i7m0039…
- Oct 20, 2026
- 0 signals
- Commit pinned
Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.
Use it from code or an agent
Read the public definition, then check cost and inputs with a preflight before a run.
Open definitionPOST /api/v1/runs/preflight
How agents connect to Relay →Tags and source
- Repo
- rose-digital/relay
- License
- MIT
Connections
Where Dependency Health fits
Have a task this would help with?
Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.