verifying-build-provenance-with-slsa-sigstore SKILL.md skillA
verifying-build-provenance-with-slsa-sigstore from adriannoes/awesome-agentic-ai is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add adriannoes/awesome-agentic-ai/verifying-build-provenance-with-slsa-sigstore@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- adriannoes/awesome-agentic-ai
- Path
cursor-claude-codex/skills/anthropic-cybersecurity-skills/skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Jun 25, 2026
- Size
- 10,328 bytes
- Repository stars
- 69
- License
- MIT
Verify signed artifacts and SLSA build provenance with Sigstore cosign and slsa-verifier, enforce keyless OIDC identity, and apply SLSA Build levels to harden the software supply chain.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verifying Build Provenance with SLSA and Sigstore ## Overview Build-provenance verification answers a question that defeats many supply-chain attacks: *was this artifact actually built from the source I think it was, by the builder I trust, without tampering?* Attackers who compromise a build system, swap a compiled release, or inject a malicious step (as in the SolarWinds and 3CX incidents) produce artifacts that look legitimate but lack verifiable provenance. SLSA (Supply-chain Levels for Software Artifacts, https://slsa.dev) defines Build levels (L1–L3) describing increasing provenance integrity, and Sigstore (https://www.sigstore.dev) provides the signing and transparency infrastructure: **cosign** for signing/verifying artifacts and attestations, **Fulcio** for short-lived keyless certificates bound to an OIDC identity, and **Rekor** as a tamper-evident transparency log. …
Read the whole file at its exact version.
How to install
mdr add adriannoes/awesome-agentic-ai/verifying-build-provenance-with-slsa-sigstore@sha256:f2f8c711b28518e5The line at the top of this page pins the label v1.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5eppkew7buwcteoi)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 25, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10328 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
adriannoes/awesome-agentic-ai · 69 stars · license MIT · pushed 2026-10-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5eppkew7buwcteoi GET https://markdownregistry.com/api/v1/resolve?ref=adriannoes/awesome-agentic-ai/verifying-build-provenance-with-slsa-sigstore GET https://markdownregistry.com/api/v1/blob/f2f8c711b28518e5beb56f167cd40faee104842ebec9ebdf6c59789b62dad263
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.