dependency-audit — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited dependency-audit (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Audit this project's dependencies for risk and staleness, then recommend a safe upgrade path. Detect the ecosystem before running anything.
Identify the package manager(s) from the manifests and lockfiles present, then use that ecosystem's native tooling. Common cases:
npm audit / pnpm audit / yarn npm audit; npm outdated.pip list --outdated, pip-audit; Poetry/uv equivalents.cargo outdated, cargo audit.go list -m -u all, govulncheck.mvn versions:display-dependency-updates, OWASP dependency-check; Gradle equivalents.bundle outdated, bundle-audit.composer outdated, composer audit.If a tool isn't installed, say so and give the exact command to run rather than guessing results. Never invent advisory IDs or version numbers; quote them from real tool output.
Keep findings factual and grounded in tool output; quote versions and advisory IDs exactly.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.