agentleFS
seancabalseseancabalse/agentic-playbook/skills/vet-dependency/SKILL.md

vet-dependency

Skill0 starsChanged 15 days agoMITView on GitHub

Vet a package before you add or upgrade it: advisories, release age, adoption, licence and fit. Use for each new dependency.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Vet a dependency

Playbook files named here: when the project has its own copy at .playbook/local/<same path>, use that copy instead.

Package: $ARGUMENTS

Principles: ${CLAUDE_PLUGIN_ROOT}/principles/07-dependencies-supply-chain.md.

  1. Need: can the platform, the standard library or an existing dependency do this in a few lines? Say so if yes, and stop.
  2. Candidates: the package plus one or two alternatives. For each, check from live sources (the registry, the advisory DB, the repo), not memory:

    • Latest version and release date; weekly downloads and dependents; maintainers; open issues and PR response; archived or not.
    • Advisories for the version you'd install (GitHub Advisories, OSV, and the ecosystem's audit after a dry install in a scratch dir), and whether they affect the code path you'd use.
    • Release age: a version published in the last two weeks waits, unless it fixes an advisory that affects you. Check that it came from the usual maintainer and matches a tag in the repo.
    • Fit: the supported framework or runtime versions, types, size, native or compiled parts, and the module format.
    • Licence; post-install scripts; network or file access it shouldn't need.
    EcosystemLook upAuditFit to check
    npmnpm view <pkg> time versions maintainers dist.attestationsnpm audit, npm audit signaturesNode LTS range (engines), React or framework major, TypeScript types, bundle size, native addons (node-gyp, prebuilt binaries), ESM/CJS
    Otherthe registry's page and APIthe ecosystem's audit tool, or OSVthe same questions
  3. Recommend the widely used, current, clean option, with a one-paragraph why. If none is clean, say what the risk is and ask the owner.
  4. Install the ecosystem's way (nx add, the package manager the lockfile belongs to, or the installer the stack file names). Pin an exact version for packages whose output you depend on.
  5. Check: the ecosystem's audit (npm audit, …) shows no new findings compared with before (say exactly what's pre-existing). The lockfile diff contains no surprising transitive packages.
  6. Record: the PR "Packages" section (name@version, adoption, advisories, native or compiled parts); a Decision Log entry for anything notable (pinning, an accepted advisory with a revisit trigger, a choice between alternatives).

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.