Software supply chain security guides
A release review follows the software from its inputs to the package customers install. Use the guides below to establish which dependencies went into a build, who produced the artifact, and who can publish it.
Where to start
Choosing dependencies
Read a lockfile change alongside the manifest to understand which direct and transitive packages changed.
Dependency Lockfiles Make Changes Reviewable, but They Still Need ReviewConfirming build provenance
Use the attestation to identify the builder and source revision behind a release artifact.
Artifact Attestations: What Build Provenance Can ProvePublishing a package
Review which release workflow can publish to npm and who can change that workflow.
npm Trusted Publishing Changes How a Release Gets PermissionMore software supply chain security guides
- A Leaked Secret Requires Revocation, Not Just a Deleted Commit
- Browser Extensions Belong in the SaaS Access Inventory
- GitHub Actions: The Trust Boundary Between a Pull Request and a Release
- Pinned Container Images Need a Deliberate Update Process
- Private Package Names Need Explicit Registry Rules
- SBOM and VEX: Two Different Records in a Vulnerability Investigation
- Self-Hosted CI Runners Extend the Build’s Access Into Your Network
Guides by Mario Luckeneder, founder of Ceron.