managing-dependencies — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited managing-dependencies (Agent Skill) and scored it 92/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 2 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 2 flagged
The text {match} tells the agent to skip the normal "ask the user first" gate. Used adversarially it removes the human-in-the-loop check before destructive or sensitive actions, turning a normally-gated agent into a fire-and-forget executor.
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.
Every dependency is code you now own the risk of. Add and update them with intent.
dependency (and its transitive tree, supply-chain risk, and upgrade burden). Prefer the standard library where it's reasonable.
licensed, and from the real source (watch for typosquats). Prefer well-known packages over obscure ones for sensitive work.
constraint; commit the lockfile. Don't rely on "latest" implicitly.
a time, and run the full test suite after. Treat a major-version bump as a real change, not a rubber stamp.
when an advisory hits a dependency you use.
don't introduce a second package manager or dependency style.
Red flag: adding a heavy dependency for a one-liner, or bumping a major version without reading what changed or running tests.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.