agentleFS
Sign inStart free
mihaimurra001mihaimurra001/preConfigProject/.agents/skills/dependency-vulnerability-audit/SKILL.md

dependency-vulnerability-audit

Skill1 starsChanged 2 months agoMITView on GitHub

Audit project dependencies and lockfiles for known CVEs, malicious packages, and supply chain security vulnerabilities.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Lockfile Verification: Always commit and enforce lockfiles (package-lock.json, pnpm-lock.yaml, poetry.lock, Cargo.lock) to guarantee …

    line 11
  2. Very specific:

    Automated Scanning: Run npm audit, pip-audit, or cargo audit as a mandatory pre-flight gate.

    line 12
  3. Distinctive:

    Typosquatting & Malicious Packages: Verify package author and download volume before introducing new dependencies.

    line 14
  4. Distinctive:

    If no patch exists: Assess whether the vulnerable function is actually reachable in your code path.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Dependency Security & Supply Chain Audit (Trail of Bits Standard)

Third-party dependencies represent the largest attack surface in modern applications:

1. Audit Strategy

  • Lockfile Verification: Always commit and enforce lockfiles (package-lock.json, pnpm-lock.yaml, poetry.lock, Cargo.lock) to guarantee deterministic reproducible builds.
  • Automated Scanning: Run npm audit, pip-audit, or cargo audit as a mandatory pre-flight gate.
  • Direct vs Transitive Dependencies: Pin exact versions or tightly constrained ranges; periodically audit transitive dependency trees.
  • Typosquatting & Malicious Packages: Verify package author and download volume before introducing new dependencies.

2. Remediation Guidelines

  • For Critical or High CVEs: Update to patched versions immediately.
  • If no patch exists: Assess whether the vulnerable function is actually reachable in your code path; wrap with safe validation or replace the package with native platform features (Ponytail principle).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free