Package Provenance and SLSA
What you'll learn: How to use the SLSA framework to verify where your software packages really came from and ensure they haven't been tampered with.
What Is Package Provenance?
Package provenance is the documented history of how a software package was built—who built it, from what source code, using which tools, and when. Think of it like a chain of custody for evidence in a court case: you need proof that the package in front of you is exactly what the original developer intended, without unauthorized modifications along the way.
Without provenance, you can't be certain that the package you downloaded wasn't secretly compiled from modified source code or replaced during transit.
What Is SLSA?
SLSA (Supply-chain Levels for Software Artifacts, pronounced "salsa") is a security framework that defines graduated levels of supply chain integrity. It establishes how trustworthy your build and distribution process is:
- SLSA Level 0: No guarantees—anyone could have built this package anywhere
- SLSA Level 1: Build process is documented and provenance exists
- SLSA Level 2: Builds use version control and are signed with cryptographic attestations
- SLSA Level 3: Source and build platforms are hardened against tampering
- SLSA Level 4: Highest assurance with two-person review and hermetic builds
How SLSA Protects Your Supply Chain
Each SLSA level adds requirements that make it harder for attackers to inject malicious code. At Level 2+, you get signed attestations—cryptographic proofs stating exactly what source code was used, what build commands ran, and what artifacts were produced. You can verify these attestations before using a package.
This builds directly on the package signing and reproducible builds concepts you've learned: SLSA provides the framework to tie them all together into a verifiable supply chain.
Key Takeaway: SLSA provides graduated security levels for verifying software provenance, ensuring packages are built from trusted source code through secure, auditable processes.