What is npm-supply-chain-audit?

A security audit for npm-compatible JavaScript package dependencies and the tools that install them.

Use it to identify the repository's package manager, check its lockfile and security settings, and add protections for npm, pnpm, Yarn, Bun, or Aube projects.

It finds missing protections against risky packages, unsafe install scripts, and untrusted dependencies. It reports the findings before applying fixes, so changes require confirmation.

npm-supply-chain-audit — Skill for Claude Code by NitorCreations

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add NitorCreations/nitor-agent-skills --skill npm-supply-chain-audit

Clone the repo

git clone --depth 1 https://github.com/NitorCreations/nitor-agent-skills

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit/github.svg)](https://agentmods.dev/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit)

Your own site

<a href="https://agentmods.dev/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,548 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00099	$0.03548
Opus 5.5	$0.00040	$0.01419
Sonnet 5.5	$0.00020	$0.00710
Haiku 4.5	$0.00010	$0.00355

Measured 1mo ago against content hash 9683e839cc7d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

npm-supply-chain-audit scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/npm-supply-chain-audit/SKILL.md · 281 lines

How it starts

The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.

npm supply-chain security audit

Audit the current repo for npm supply-chain security issues, present findings to the user, and apply fixes only after confirmation.

Step 1 – Detect the package manager

Check which package manager(s) are in use:

package-lock.json -> npm
aube-lock.yaml -> Aube
pnpm-lock.yaml -> pnpm
yarn.lock + .yarnrc.yml -> Yarn Berry; yarn.lock without .yarnrc.yml -> Yarn Classic
bun.lockb or bun.lock -> Bun
packageManager field in package.json confirms the PM and version

Use the packageManager field to determine the version. If not present, run the PM's --version command. The version is needed for checks that depend on minimum PM versions (e.g. pnpm 10+, pnpm 11+, npm 11.10+, npm 12+, Yarn Berry 4.10+, Bun 1.3+).

pnpm 11 ships several supply-chain protections on by default (minimumReleaseAge: 1440, blockExoticSubdeps: true, strictDepBuilds: true) and only reads pnpm-specific settings from pnpm-workspace.yaml (or ~/.config/pnpm/config.yaml), not from .npmrc. Many checks below differ between pnpm 10 and pnpm 11+.

npm 12 similarly ships protections on by default: dependency lifecycle scripts are blocked unless approved via the allowScripts field in package.json, and git and remote-URL dependencies are blocked (allow-git and allow-remote default to none). Several checks below differ between npm 11 and npm 12+.

If no lockfile exists, default to npm.

Step 2 – Audit

Work through the checks below. For each one, check the current state and record whether it passes or needs a fix. Do NOT make any changes yet.

2.1 Lockfile committed

If no lockfile exists (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lockb, bun.lock, aube-lock.yaml), warn the user they should run their package manager's install command and commit the lockfile. Do NOT run install yourself.

2.2 Block lifecycle scripts

npm 12+ – blocks dependency lifecycle scripts (preinstall, install, postinstall, and prepare for git/file/link dependencies) by default; only packages approved in the allowScripts field of package.json may run them. Check that .npmrc does not loosen this with a broad allow-scripts setting, and review existing allowScripts entries – flag any untrusted packages approved there.

Read the full file on GitHub · 281 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago Changed · -1 lines 9683e839cc7d
2mo ago First seen · 282 lines · 99 tokens per session scan A b222954a1708

Subscribe to this mod's changes

npm-supply-chain-audit is a skill published in the GitHub repository NitorCreations/nitor-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 3,548 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Languages Security TypeScript

npm-supply-chain-audit next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
npm-supply-chain-auditNitorCreations/nitor-agent-skills	Skill	2	1mo ago	MIT	A	99	Claude Code
no-bare-castsprisma/orm	Skill	48k	today	Apache-2.0	A	52	Claude Code, Codex
aws-sst-developmentsickn33/agentic-awesome-skills	Skill	49k	today	MIT	A	26	Claude Code
league-akari-shard-developmentLeagueAkari/LeagueAkari	Skill	4.7k	5d ago	MIT	A	58	Claude Code, Codex
dd-code-generationDataDog/pup	Skill	1.0k	today	Apache-2.0	A	16	Claude Code
fast-typescript-checkinternet-development/www-sacred	Skill	1.6k	3d ago	MIT	A	84	Claude Code, Codex
typescript-magicianmcollina/skills	Skill	2.0k	10d ago	MIT	A	108	Claude Code, Codex