Individual skill

supply-chain-security

Vet dependencies before they enter the build: typosquats, dependency confusion, malicious packages, known vulnerabilities, unlocked resolution, risky install and build hooks, EOL embedded runtimes, and the authenticity and freshness of your own release channel. Use when adding or upgrading a dependency, reviewing package manifests or lockfiles, configuring package sources or internal namespaces, or publishing a package or application update.

skills/supply-chain-security/SKILL.md

Read pinned source

Source commit eaba88102d91df65a9aa6397e8507c315c018f5e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.

Repository context

Repository stars (not skill ratings): 23
Repository last updated: Aug 14, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-skills Repository topic
llm Repository topic
security Repository topic
skills Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 7,793 bytes
SKILL.mdcore · 7,793 bytes
SKILL.mdcore · 7,793 bytes
SKILL.mdcore · 7,793 bytes
references/ecosystem-controls.mddoc · 4,450 bytes
references/verifying-findings.mddoc · 8,569 bytes
rules/dependency_confusion.jsonasset · 5,133 bytes
rules/known_malicious.jsonasset · 925 bytes
rules/typosquat_patterns.jsonasset · 8,763 bytes
tests/corpus.jsonasset · 5,486 bytes

Read excerpt


# Supply Chain Security

## Rules (for AI agents)

### ALWAYS
- Verify the identity of a new dependency before adding it: registry metadata,
  repository URL, maintainer set, and provenance checked against the signer you
  *expect*. Name-similarity screening opens the question; it never answers it.
- Query the bundled malicious-package data before adding any dependency —
  `check_dependency`, `check_typosquat` and `lookup_vulnerability` read it, this file
  cannot. Match on ecosystem, normalized name **and affected version range**; an
  active match on the resolved version blocks.
- Treat package age, download volume, maintainer count and activity as risk signals,
  never as proof of trust. Defaults: a verified maintainer signal within 90 days of a