nbbaier/npm-supply-chain-security
skills/npm-supply-chain-security/SKILL.md
Audit and harden Node.js projects against npm supply chain attacks — compromised maintainer accounts, malicious package versions, and install-script payloads. Use when reviewing or setting up package.json, lockfiles, .npmrc, Dockerfile, or CI workflows for security; when the user mentions npm security, supply chain attacks, `npm audit`, lockfile policy, install scripts, or min-release-age; also when the user wants to check whether their dependencies are safe, or recover from a suspected compromise.
$ install --global
skillsauthnpx skillsauth add nbbaier/agent-skills npm-supply-chain-securityInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 13, 2026, 6:54 AM141.9s3 files scanned
SKILL.md
- name:
- npm-supply-chain-security
- description:
- Audit and harden Node.js projects against npm supply chain attacks — compromised maintainer accounts, malicious package versions, and install-script payloads. Use when reviewing or setting up package.json, lockfiles, .npmrc, Dockerfile, or CI workflows for security; when the user mentions npm security, supply chain attacks, `npm audit`, lockfile policy, install scripts, or min-release-age; also when the user wants to check whether their dependencies are safe, or recover from a suspected compromise.
npm Supply Chain Security
Adapted from NPM Security Best Practices for Supply Chain Attacks by Localcan.
Defends against three concrete attack patterns: zero-day malicious publishes (a compromised maintainer pushes a backdoored version), install-script payloads (lifecycle scripts run arbitrary code on install), and resolution drift (npm install picks up a newer-than-locked version). Controls operate at three layers — resolution (versions entering the lockfile), installation (lifecycle scripts), and execution environment (what the build can reach).
npm-primary; pnpm and bun equivalents are noted inline. Full per-PM detail in REFERENCE.md.
Quick start
Apply the 30-minute baseline:
-
Commit the lockfile (
package-lock.json/pnpm-lock.yaml/bun.lock). -
Add an install cooldown —
min-release-age=1in.npmrc(npm 11+), orminimumReleaseAge: 1inpnpm-workspace.yaml(pnpm 10.16+). Bun has no native equivalent — this is a real gap, sincebun installre-resolves locally and bypasses any PR-layer cooldown. Configure Dependabot or Renovate cooldown as a partial mitigation for the update-PR path. -
In CI/Dockerfile, install with frozen lockfile and
--ignore-scripts:npm ci --ignore-scriptspnpm install --frozen-lockfile --ignore-scriptsbun install --frozen-lockfile --ignore-scripts
Allow-list required native modules with a follow-up
npm rebuild <pkg>(e.g.sharp,better-sqlite3). -
Digest-pin base images:
FROM node:24-alpine@sha256:..., notFROM node:24-alpine. -
Add an audit step to CI:
npm audit --audit-level=high(orpnpm audit/bun audit). -
Put
package.json, the lockfile,.npmrc, andDockerfileunder CODEOWNERS with required review.
Workflows
Audit an existing project
Run the audit script (lives at scripts/audit.sh in this skill directory) from the target project's root:
bash <path-to-this-skill>/scripts/audit.sh
It detects the package manager, checks each baseline item, and prints PASS/FAIL/WARN. Treat each FAIL as a TODO; WARN items need human judgment.
Harden a project from scratch
Walk the user through the 30-minute checklist in order. Two recurring gotchas:
--ignore-scriptsbelongs in CI commands, not project-level.npmrc. Local dev often needs install scripts to compile native modules.- Electron apps and projects with many native modules may need a per-package allow-list rather than a blanket block. Ask before applying
--ignore-scriptsglobally.
Respond to a suspected compromise
If a malicious version may have been installed:
- Enumerate reachable credentials. For every affected machine or runner, list every credential that was loaded — env vars, dotfiles, keychains, agent forwards, cloud metadata. Assume each one is exfiltrated.
- Rotate everything reachable. Don't try to assess which were actually stolen. Rotate npm tokens, GitHub PATs, SSH keys, cloud credentials, CI secrets, SaaS API keys.
- Pin to last-known-good. Find the commit predating the bad version, revert the lockfile,
npm cifrom there. - Trace the blast radius.
npm ls <bad-pkg>shows every dependency path. For multi-repo orgs, search across all lockfiles. - Rebuild artifacts. Any image, deploy, or published package produced while the bad version was installed should be considered tainted. Rebuild from clean inputs.
What this does NOT prevent
- Malicious commits directly to the lockfile (the cooldown only filters registry metadata; CODEOWNERS + required review is the answer).
- Attacks that evade detection beyond the cooldown window.
- Projects where install scripts are an architectural requirement (mitigate with allow-listing, not blocking).
Out of scope: publishing-side hardening
This skill covers the install side — protecting your project from compromised upstream packages. If the user is also publishing packages to npm, point them at the publishing-side controls (separate concern, not audited here):
- 2FA enforced on the npm account and on any maintainer accounts.
- Scoped, short-lived automation tokens — never long-lived publish tokens checked into CI secrets.
- OIDC-based trusted publishing (GitHub Actions → npm) instead of static tokens where possible.
- Provenance attestations (
npm publish --provenance) so consumers can verify the build origin.
See REFERENCE.md for per-control rationale, per-PM syntax, and incident background.
Related Skills
nbbaier/tufte-viz
development
VerifiedTrustedCommunity
Ideate and critique data visualizations using Edward Tufte's principles from "The Visual Display of Quantitative Information." Use this skill when: (1) Designing new data visualizations or charts (2) Critiquing or improving existing visualizations (3) Reviewing dashboards or reports for graphical integrity (4) Deciding between visualization approaches (5) Reducing chartjunk or improving data-ink ratio (6) Planning small multiples or high-density displays Applies principles: data-ink ratio, chartjunk elimination, graphical integrity, lie factor, small multiples, and data density.
9SKILL.mdUpdated May 24, 2026
nbbaier/val-town-cli
tools
VerifiedTrustedCommunity
Manage Val Town projects using the vt CLI. Use when working with Vals (Val Town serverless functions), syncing code to Val Town, creating HTTP endpoints, streaming logs, or managing Val Town branches. Triggers on tasks involving Val Town development, val creation/editing, or when user mentions "vt", "val town", or "vals".
9SKILL.mdUpdated May 13, 2026
nbbaier/react-effect-patterns
development
VerifiedTrustedCommunity
Guidelines for proper React useEffect usage and avoiding unnecessary Effects. Use when writing, reviewing, or refactoring React components that use useEffect, useState, or handle side effects. Triggers on tasks involving React Effects, derived state, event handlers, data fetching, or component synchronization.
9SKILL.mdUpdated May 13, 2026
nbbaier/logging-best-practices
tools
VerifiedTrustedCommunity
Use before implementing logs in a medium to large scale production system.
9SKILL.mdUpdated May 13, 2026