Add SLSA build provenance attestation#277
Merged
Merged
Conversation
The framework signs action files and inventories dependencies (SBOM) but could not attest what was produced by which build. Add an in-toto v1 statement carrying a SLSA v1 provenance predicate over file sha256 digests, plus a verifier that re-hashes the artifacts. Pure stdlib and fully offline. Wired through the facade, AC_build_provenance/ AC_verify_provenance executor commands, MCP tools and the Script Builder.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 31 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The framework can sign action files (HMAC) and inventory dependencies (SBOM), but it could not attest what was produced by which build — the SLSA provenance attestation binding artifact digests to build metadata. This adds it.
subject_for(path)/subject_for_bytes(name, data)— in-toto subjects (sha256).build_provenance(subjects, *, build_type, builder_id, external_parameters, metadata)— in-toto v1 Statement + SLSA v1 provenance predicate (buildDefinition+runDetails).write_provenance(stmt, path)/verify_provenance(stmt, files)— persist / re-hash and report mismatches.Pure stdlib (
hashlib+json), fully offline. Complementsaction_signingandsbom. DSSE signing left as an optional later layer.Five-layer wiring
je_auto_control/utils/provenance/__init__.py+__all__AC_build_provenance,AC_verify_provenanceac_build_provenance,ac_verify_provenanceTests & docs
test/unit_test/headless/test_provenance_batch.py(8 tests: digest, statement structure, verify clean/tamper, write round-trip)Lint clean: ruff / pylint / bandit / radon.