See which dependencies put your product at risk
Agents map every open-source package your software runs on and flag open advisories, single maintainer accounts and stale releases. No new data infrastructure or data science team required.
What runs behind the example
The monitor is the part you see. Behind it is a managed data pipeline that agents built.
Sources
Public records of packages, advisories and releases.
- deps.dev
- OSV advisories
- npm registry
- Your lockfiles and SBOMs
Ingest and catalog
Agents load the resolved dependency graph and the record of every package in it.
- 436 packages
- 821 dependency links
Score the risk
Agents work out how many packages need each one, then flag advisories, single maintainer accounts and stale releases.
- 11 open advisories
- 4 risk signals
Live application
The monitor reads from the scored tables, and every number traces back to its source.
- Risk monitor
- Audit trail
Every figure shows the day the data was read. When a new advisory or release is published, each stage can be run again.
Using your own data
The example runs on public data. Here is what changes when you bring your own.
- Software
- In this exampleOne open-source application
- With your dataYour products, services and build pipelines
- Dependencies
- In this exampleThe resolved tree from deps.dev
- With your dataYour lockfiles and SBOMs
- Signals
- In this exampleAdvisories, maintainers and releases
- With your dataYour scanners, licenses and policies
- Priority
- In this exampleHow many packages need each one
- With your dataWhat each package touches in your product
- Decisions
- In this exampleWhich dependencies to look at first
- With your dataWhat to patch, replace or sponsor
Your data stays private to your organization. Nothing is public unless you publish it.
Why you can trust the monitor
A risk list is only useful if it is specific. This one names the package, the version and the public record behind every flag.
7 of 436
Packages with an open advisory
11 advisories in all, 6 of them rated high, each linked to its OSV record.
Packages flagged, by signal
- One npm maintainer account224
- No release in two years124
- Open advisory7
Advisories apply to the versions resolved when the data was read; a fresh install may pick up fixed versions. A maintainer account is not a count of people.
- Specific to the version
- Every flag names the exact package version it applies to, not the package in general.
- Every number is traceable
- Each figure links to its source and the calculation behind it.
- Facts, not verdicts
- The monitor reports what the public record shows and leaves the judgment to your team.
Build a dependency risk engine for your business
Start with your software and the question you need answered.
Connect your data
Upload your lockfiles or SBOMs, or connect your repositories. Agents add the public records.
Ask your question
Describe the risks you care about. Agents build a first version you can use right away.
Review and share
Check the numbers, comment and approve the monitor before your team relies on it.