moai-ref-supply-chain

Provides defensive reference patterns for SBOM generation, SLSA provenance, and Sigstore artifact verification.

1.2k|222|Updated Sep 16, 2025
One-click install
npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-supply-chain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: moai-ref-supply-chain
Source: https://github.com/modu-ai/moai-adk/tree/main/internal/template/templates/.claude/skills/moai-ref-supply-chain
Command: npx skills add https://github.com/modu-ai/moai-adk --skill moai-ref-supply-chain

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about moai-ref-supply-chain

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate an SBOM for my software project?

Generate an SBOM at build time using syft, which emits both SPDX and CycloneDX formats from an artifact or source tree. Include the NTIA minimum elements such as supplier, version, and dependency relationships, and attach it as a signed attestation.

What is the difference between SPDX and CycloneDX SBOM formats?

SPDX is a Linux Foundation ISO standard focused on license compliance with broad regulatory acceptance. CycloneDX is an OWASP format focused on security with native vulnerability and dependency-relationship modeling.

How do I defend against dependency confusion attacks?

Defend against dependency confusion by reserving your namespace on public registries, pinning internal names to resolve only from the internal registry, and hash-pinning every dependency in the lockfile. A registry proxy that refuses public fallback for internal names adds another layer.

What SLSA level should production deployments require?

Production environments typically require SLSA Build L2 or higher, meaning signed provenance from a hosted build platform. High-assurance environments require L3, where the build runs in an isolated, ephemeral environment with non-forgeable provenance.

How do I verify a signed artifact with cosign?

Verify artifacts at install or admission time using cosign verify with the expected certificate identity and OIDC issuer. Verification fails closed, so unsigned or wrong-identity artifacts are rejected before acceptance.

When should I not use this supply-chain reference?

This reference does not cover offensive techniques, LLM-specific security such as model provenance, or web-application OWASP Top 10 issues. Use moai-ref-llm-security or moai-ref-owasp-checklist for those domains.