Dependency Risk Audit
Dependency Risk Audit reads a lockfile or manifest that the user pastes or links (a public raw file address) and checks each pinned package against the OSV.dev vulnerability database. It understands package-lock.json (v1 to v3), yarn.lock, pnpm-lock.yaml, requirements.txt, poetry.lock, Pipfile.lock, go.sum, go.mod, Cargo.lock, Gemfile.lock, composer.lock and Maven pom.xml (direct dependencies with literal versions). Each vulnerability is reported with its identifiers and aliases (CVE, GHSA), severity and CVSS score where the record carries one, affected and fixed versions, and a link to the OSV record. A licence summary from deps.dev and from the lockfile itself flags copyleft licences (GPL, AGPL, LGPL, SSPL and similar) and unknown licences. Files with more than 500 packages are checked in parts with an offset. A project can be saved: the server re-scans it on a schedule (weekly on the free plan, daily on Pro), records an alert for each new vulnerability that affects a saved package, and emails one digest per check round. Vulnerability records come from OSV.dev and the databases it aggregates; each source keeps its own licence (for example the GitHub Advisory Database is CC-BY 4.0). Package metadata comes from deps.dev. Licences are as declared by the package, not legal advice, and results are a screening aid rather than a guarantee that a package is safe.
Details
https://deps.tidybutton.com/mcp · streamable-http
