supply-chain-and-sbom-sentinel
Skill4 starsChanged 31 days agoMITView on GitHub
Review new dependencies, lockfiles, install hooks, build attestations, SBOMs, and container base images. Use when package identity, artifact integrity, registry trust, or a change in release ownership needs verification.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- anti-slop-engineeringSkill
- anti-slop-engineeringSkill
- api-ergonomics-and-contract-governorSkill
- apple-craft-and-frame-budgetSkill
- apple-craft-and-interaction-physicsSkill
- asset-provenance-guardSkill
- backprop-guardSkill
- chaos-and-degradation-choreographerSkill
- chromatic-drift-guardSkill
- cognitive-load-and-attention-governorSkill
- comment-budget-guardSkill
- context-window-and-token-economics-architectSkill
- cryptographic-agility-and-secret-lifecycle-gateSkill
- decision-guardSkill
- demock-guardSkill
- design-system-drift-guardSkill
- deterministic-simulation-and-property-testingSkill
- distributed-consensus-and-concurrency-gateSkill
- finops-and-unit-economics-governorSkill
- future-scale-gateSkill
- grumpy-senior-staff-engineerSkill
- honeypot-trap-guardSkill
- house-tell-guardSkill
- install-anti-slopSkill
- llm-eval-and-prompt-injection-fortressSkill
- mandela-guardSkill
- mechanical-sympathy-and-perf-gateSkill
- mechanical-sympathy-profilerSkill
- motion-runtime-guardSkill
- observability-and-slo-architectSkill
- observability-and-slo-gateSkill
- paranoid-principal-architectSkill
- pr-boundary-guardSkill
- privacy-and-data-lineage-gateSkill
- re0-handoff-guardSkill
- reduction-guardSkill
- repo-memory-and-invariant-stewardSkill
- root-fix-gateSkill
- safe-evolution-and-rollout-choreographerSkill
- scientific-fault-isolationSkill
- styleseed-guardSkill
- tagore-guardSkill
- type-level-and-ast-slop-gateSkill
- ui-and-copy-disciplineSkill
- verification-oracle-architectSkill
- zero-downtime-migration-gateSkill
The file
Files
Supply Chain and SBOM Sentinel
Review order
- Read the import or build requirement, package manifest, and lockfile diff. Record the intended package coordinate, exact version, effective registry or source commit, artifact integrity value, and the reason for the change. Show additions, changes in source or ownership, and new lifecycle hooks separately from lockfile reordering.
- Start from a trusted upstream source, such as the project's verified documentation or repository, then match its documented coordinate with the registry record and lockfile. For a private package, inspect scoped registry configuration and resolver fallback rules. Remove credentials from evidence. A similar name, first-seen publisher, unsigned release, or low download count alone cannot establish malicious intent.
- Inspect the exact package artifact as data, without executing install or build code. Do not extract untrusted tar paths into the workspace. Read manifests, lifecycle commands, and files those commands invoke. Trace network access, credential reads, writes outside the package, and subprocesses. Native build hooks can be legitimate. Record their need and the controls before permitting them.
- Verify available integrity evidence with the ecosystem's existing tooling. A digest match binds bytes to an expected digest. Provenance verification also checks the signature or attestation and compares the source revision, builder or workflow identity, and subject digest to independent policy. Registry guidance and attestations are optional sources when offline.
- If supplied, compare the SBOM's generated artifact identity, version, target platform, dependency relationships, and hashes with the reviewed lockfile and built image. Distinguish build-time, optional, and runtime dependencies. For OCI images, identify whether the pin is for an index or a platform manifest before comparing digests. A matching SBOM or digest does not establish absence of vulnerabilities.
- Report each check with its evidence and a trust decision. Before adding an install step, request missing evidence or propose a safe replacement. Record remediation at the authoritative resolver, build, or release boundary.
| Decision | Evidence |
| Verified | Canonical identity and registry match, approved digest or independently verified signed provenance matches the artifact, and relevant scripts were reviewed. State precisely which checks ran. |
| Suspicious | A concrete mismatch or prohibited behavior, such as an approved digest mismatch, registry substitution, a package coordinate that differs from trusted documentation, or a lifecycle hook that reads unrelated secrets. Record evidence and hold installation. |
| Unknown | Available evidence cannot establish identity, bytes, or script behavior. For an offline uncached release, request the approved metadata or artifact. Never infer approval from a clean grep or missing alerts. |
Catalog: CI-01, CI-04, CI-07.
Evidence exercise
Run offline review cases with Python 3.9+. The fixtures represent already inspected evidence, not a package verifier. They assert the distinction among a package name mismatch, a prohibited hook, a matching approved artifact, unavailable offline evidence, and a mismatched container digest. No fixture downloads, extracts, builds, or runs third-party code.
Sources: npm package provenance, npm audit signatures, Docker image digest pinning, SLSA artifact verification, CycloneDX specification.
Does 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.

