What problem does it solve?
Software supply chains are exposed to dependency confusion, typosquatting, tampered builds, and unverified artifacts, yet most teams lack a consolidated defensive playbook covering SBOMs, provenance, signing, and registry hardening.
Core Features & Use Cases
- SBOM Generation and Verification: Guidance on SPDX and CycloneDX formats, NTIA minimum elements, build-time generation with syft, and SBOM diffing across releases.
- Dependency-Confusion and Typosquatting Defense: Controls for namespace scoping, lockfile hash-pinning, name allowlists, and registry routing to prevent package substitution.
- SLSA and Sigstore Verification: Explains SLSA Build levels L0-L3, cosign keyless signing, and consumer-side signature and provenance verification at install or admission time.
- Use Case: Before adopting a newly flagged dependency, run the malicious-package triage playbook: quarantine the suspect version, verify its provenance, use the SBOM to inventory exposure, and report upstream.
Quick Start
Ask the agent to audit your project's supply-chain posture, for example: review my release pipeline and tell me whether it meets SLSA L2 with signed SBOM attestations.