Skills deps
Use when hardening npm supply chain, pinning dependency versions, adding .npmrc security flags, or setting up Renovate and audit workflows. Locks down install-time scripts, registries, version ranges, and CI checks.
install
source · Clone the upstream repo
git clone https://github.com/tartinerlabs/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/tartinerlabs/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/deps" ~/.claude/skills/tartinerlabs-skills-deps && rm -rf "$T"
manifest:
skills/deps/SKILL.mdsource content
You harden npm supply chain security for JS/TS projects. Auto-detect what's already configured and only apply missing hardening measures.
1. Detect Package Manager
Check for lockfiles in this order:
→ pnpmpnpm-lock.yaml
/bun.lock
→ bunbun.lockb
→ yarnyarn.lock
→ npmpackage-lock.json- No lockfile → ask the user
Use the detected package manager for all commands. Replace
<pm> in rule files with the detected manager.
2. Detect Existing Config
Before applying any hardening, scan for existing configurations:
/.npmrc
/.yarnrc.yml
→ package manager config already present (check individual flags)bunfig.toml
/renovate.json
/.renovaterc
/.renovaterc.json
key inrenovate
→ Renovate already configuredpackage.json
containing.github/workflows/*.yml
→ audit workflow existsaudit
containing.github/workflows/*.yml
→ dependency review existsdependency-review
containing.github/workflows/*.yml
→ lockfile integrity check existslockfile
dependency versions withoutpackage.json
or^
prefixes → already pinned~
Skip rules whose checks already pass. Report what was skipped at the end.
3. Apply Rules
Read each rule file for detailed instructions and config templates.
| Rule | Impact | File |
|---|---|---|
| .npmrc security flags | HIGH | |
| Release quarantine | MEDIUM | |
| Version pinning | HIGH | |
| Renovate | MEDIUM | |
| Audit workflow | HIGH | |
| Dependency review | HIGH | |
| Lockfile integrity | MEDIUM | |
4. Output Summary
After all rules are processed, display a summary:
## Supply Chain Hardening Complete ### Applied - [list of rules applied with brief description] ### Skipped (already configured) - [list of rules skipped with reason] ### Manual Steps Required - [any post-setup steps, e.g. "Run `pnpm exec husky` to reinitialise git hooks"]
Assumptions
- Project has a
(JS/TS project)package.json - Project is hosted on GitHub (for CI workflows)
- GitHub CLI (
) is available for looking up action commit SHAsgh - Git is initialised in the project