Supply Chain Security

Security here is two different questions. Who made this component? That is provenance, covered on this page. What can it do on your machine? That is enforcement — see What Is Enforced.

Key Principles

• No Anonymous Push - Every component must be pushed by an authenticated user
• Responsible Party Tracking - Every component is traceable to its publisher
• Signed by Default - Every workshop supply signs the component; no flag required
• Deny by Default - A component receives only the capabilities it is granted, enforced at composition and runtime configuration — details
• Full Audit Trail - All actions are logged

Component Signing

Signing is not a flag you remember to pass — components are signed by default. workshop supply uses Sigstore keyless signing: your OIDC identity (Google, GitHub, or Microsoft) obtains a short-lived certificate from Fulcio, the component is signed with an ephemeral key, and the signature is recorded in the public Rekor transparency log. There are no long-lived signing keys to manage, rotate, or leak.

Unsigned pushes are refused, with one exception: the public sandbox namespaces (test, public, examples) accept an explicit --skip-signing opt-out for experimentation.