shadow-supplychain
Skill1 starsChanged yesterdayMITView on GitHub
Dependency, Build & Artifact Supply-Chain Integrity. Use when generating or verifying CycloneDX/SPDX SBOMs against resolved lockfiles, detecting typosquatting/dependency confusion, auditing transitive dependency reachability, enforcing pinned CI/container digests, checking license policies, or validating SLSA provenance attestations. Do NOT use for general AppSec STRIDE/SAST (shadow-sec), server operations (shadow-ops), or SemVer changelogs (shadow-release).
In this repository51 other files it gives its agents.
- antislop-codeSkill
- antislop-copywritingSkill
- antislop-humanSkill
- antislop-layoutmobileSkill
- antislopSkill
- antislop-uiSkill
- context7Skill
- handoffSkill
- shadow-accessibilitySkill
- shadow-apiSkill
- shadow-architectSkill
- shadow-authSkill
- shadow-bootstrapSkill
- shadow-browserSkill
- shadow-cacheSkill
- shadow-compatSkill
- shadow-concurrencySkill
- shadow-dataSkill
- shadow-dbSkill
- shadow-debugSkill
- shadow-designSkill
- shadow-discoverySkill
- shadow-docSkill
- shadow-domainSkill
- shadow-eaSkill
- shadow-evalSkill
- shadow-finopsSkill
- shadow-gitSkill
- shadow-grcSkill
- shadow-handoverSkill
- shadow-integrateSkill
- shadow-maintainSkill
- shadow-mobileSkill
- shadow-modernizeSkill
- shadow-monarchSkill
- shadow-observeSkill
- shadow-opsSkill
- shadow-perfSkill
- shadow-planSkill
- shadow-pmoSkill
- shadow-presalesSkill
- shadow-privacySkill
- shadow-qualitySkill
- shadow-realtimeSkill
- shadow-refactorSkill
- shadow-releaseSkill
- shadow-resilienceSkill
- shadow-searchSkill
- shadow-secSkill
- shadow-testSkill
- shadow-uatSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Read methodologies/SBOM-SLSA-PROVENANCE-AND-LOCKFILE-INTEGRITY.md and playbooks/SBOM-RISK-REGISTER-AND-ATTESTATION.md:
- Very specific: line 17
Inventory Build Chain & Lockfiles: Verify package-lock.json, pnpm-lock.yaml, poetry.lock, go.sum, Cargo.lock, CI workflows, and base …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
/shadow-supplychain — Dependency, Build & Artifact Integrity
- Owner: SBOM vs lockfile integrity, transitive reachability, dependency confusion/typosquatting defense, pinned build inputs, SLSA provenance, license policy, and time-bounded security waivers.
- Boundaries: AppSec STRIDE/SAST/ASVS (
shadow-sec), server/K8s operations (shadow-ops), SemVer rollout/rollback (shadow-release).
1. Preconditions, Isolation & Failure Rules
- Offline/Restricted Environments: Explicitly declare when vulnerability databases or external signature registries are unreachable (
UNVERIFIED/NOT_RUN), never fabricating provenance trust. - Zero Unverifiable Trust: Reject artifacts with unverifiable signer identity, floating mutable image/action tags (
:latest,@main), or SBOMs diverging from resolved lockfiles.
2. 6-Step Supply-Chain Integrity Playbook
Read methodologies/SBOM-SLSA-PROVENANCE-AND-LOCKFILE-INTEGRITY.md and playbooks/SBOM-RISK-REGISTER-AND-ATTESTATION.md:
- Inventory Build Chain & Lockfiles: Verify
package-lock.json,pnpm-lock.yaml,poetry.lock,go.sum,Cargo.lock, CI workflows, and base container images. - Validate Origin & Anti-Confusion Controls: Detect lookalike typosquatted packages, scoped private registry mismatches, and unpinned GitHub Actions (
uses: org/action@v1-> must pin 40-char SHA). - Generate & Reconcile SBOM (CycloneDX / SPDX): Cross-check emitted SBOM components 1:1 against resolved lockfile dependencies (
0phantom/missing packages). - Prioritize by Reachability & Fix Availability: Triage CVEs by production runtime reachability rather than noisy dev-only alerts; enforce expiry dates on waivers.
- Enforce Isolated Reproducible Build & Provenance: Build in isolated CI runners without leaking secrets; sign artifacts and emit SLSA provenance attestations where supported.
- Verify Before Release Handoff: Hand verified SBOM + provenance digest to
/shadow-releaseand/shadow-handover.
python "shadow-supplychain/scripts/supplychain_sbom_gate.py" --self-test
python "shadow-supplychain/scripts/supplychain_sbom_gate.py" --verify path/to/supplychain_manifest.jsonDoes 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
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.

