Back to catalog
Static reviewDevelopment

Skill dossier

verifying-build-provenance-with-slsa-sigstore

Source declaration

Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.

The author's original description, preserved in English. It describes intent, not verified performance.

Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L77]
  • Step 1: Verify a keyless cosign signature on an image [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L79]
  • Step 2: Verify the SLSA provenance attestation on the image [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L90]
  • Step 3: Inspect the provenance predicate [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L102]
  • Step 4: Verify a release binary with slsa-verifier [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L113]
  • Step 5: Verify GitHub artifact attestations / blob bundles [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L129]
  • Step 6: Enforce verification as a gate [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L144]
  • Step 7: Map findings to SLSA Build levels [Source statement; provisional, not tested. Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L160]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L1-L27]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
5
Markdown files
3
scripts
1
references
2
Size
29.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/verifying-build-provenance-with-slsa-sigstore/LICENSEOther11 KB
skills/verifying-build-provenance-with-slsa-sigstore/references/api-reference.mdReference2.4 KB
skills/verifying-build-provenance-with-slsa-sigstore/references/standards.mdReference1.4 KB
skills/verifying-build-provenance-with-slsa-sigstore/scripts/agent.pyScript4.7 KB
skills/verifying-build-provenance-with-slsa-sigstore/SKILL.mdInstruction10.4 KB

SKILL.md frontmatter

{
  "name": "verifying-build-provenance-with-slsa-sigstore",
  "description": "Verifies artifact signatures and SLSA provenance using Sigstore's cosign (verify, verify-attestation, verify-blob-attestation) and slsa-verifier (verify-artifact), enforcing keyless OIDC builder identity and source repo against SLSA Build levels. Use in CI/CD before deploying artifacts, when consuming third-party attestations, establishing a SLSA Build L3 pipeline, or confirming provenance during incident response or admission control.",
  "domain": "cybersecurity",
  "subdomain": "supply-chain-security",
  "tags": [
    "supply-chain",
    "slsa",
    "sigstore",
    "cosign",
    "provenance",
    "attestation",
    "keyless-signing",
    "code-signing"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.DS-01"
  ],
  "mitre_attack": [
    "T1195"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Objectives

    Source-described action candidate under “Objectives”; not verified execution.

  4. 04
    Action

    MITRE ATT&CK Mapping

    Source-described action candidate under “MITRE ATT&CK Mapping”; not verified execution.

  5. 05
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  6. 06
    Action

    Step 1: Verify a keyless cosign signature on an image

    Source-described action candidate under “Step 1: Verify a keyless cosign signature on an image”; not verified execution.

Inspect all extracted workflow candidates (18 candidate steps)
  1. 07
    Action

    Step 2: Verify the SLSA provenance attestation on the image

    Source-described action candidate under “Step 2: Verify the SLSA provenance attestation on the image”; not verified execution.

  2. 08
    Action

    Step 3: Inspect the provenance predicate

    Source-described action candidate under “Step 3: Inspect the provenance predicate”; not verified execution.

  3. 09
    Action

    Step 4: Verify a release binary with slsa-verifier

    Source-described action candidate under “Step 4: Verify a release binary with slsa-verifier”; not verified execution.

  4. 10
    Action

    Step 5: Verify GitHub artifact attestations / blob bundles

    Source-described action candidate under “Step 5: Verify GitHub artifact attestations / blob bundles”; not verified execution.

  5. 11
    Action

    Step 6: Enforce verification as a gate

    Source-described action candidate under “Step 6: Enforce verification as a gate”; not verified execution.

  6. 12
    Action

    Step 7: Map findings to SLSA Build levels

    Source-described action candidate under “Step 7: Map findings to SLSA Build levels”; not verified execution.

  7. 13
    Action

    Build L1 — provenance exists (the build process generates it), but it may be unsigned/forgeable.

    Source-described action candidate under “Step 7: Map findings to SLSA Build levels”; not verified execution.

  8. 14
    Action

    Build L2 — provenance is signed by a hosted build service.

    Source-described action candidate under “Step 7: Map findings to SLSA Build levels”; not verified execution.

  9. 15
    Action

    Build L3 — provenance is non-forgeable: generated on an isolated, hardened builder where secrets are unavailable to user-defined steps (e.g., `slsa-github-generator` reusable workflows). Require L3 for high-trust artifacts.

    Source-described action candidate under “Step 7: Map findings to SLSA Build levels”; not verified execution.

  10. 16
    Action

    Tools and Resources

    Source-described action candidate under “Tools and Resources”; not verified execution.

  11. 17
    Action

    Verification Identity Reference

    Source-described action candidate under “Verification Identity Reference”; not verified execution.

  12. 18
    Action

    Validation Criteria

    Source-described action candidate under “Validation Criteria”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Items warrant review

68 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

39 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 39 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

29 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 29 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 5 collected file(s), 3 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/verifying-build-provenance-with-slsa-sigstore/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/verifying-build-provenance-with-slsa-sigstore
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.