Skip to content
ceron
Book a Call
ceron
CLIENT

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 Review

Confirming build provenance

Use the attestation to identify the builder and source revision behind a release artifact.

Artifact Attestations: What Build Provenance Can Prove

Publishing a package

Review which release workflow can publish to npm and who can change that workflow.

npm Trusted Publishing Changes How a Release Gets Permission

Guides by , founder of Ceron.