Choose the artifact
Identify the exact file or version you will record.
Loading...
For developers
Associate a signed record with the version of code or a release artifact you want to share.
For developers
A recorded fingerprint can help someone compare an artifact with the version that was signed. The identity and context of the issuer remain important to interpreting that proof.
A record does not independently establish copyright ownership or guarantee that the code is safe.
For developers
Identify the exact file or version you will record.
Use a supported issuing workflow to sign the relevant information.
Provide verification information alongside the artifact.
Details and limitations
Decide whether you are recording a release archive, a source snapshot or a build output. Keep the exact bytes that were signed or fingerprinted, and publish verification information alongside the artifact. A developer automating this process should configure its business integration in Console; personal Verify remains appropriate for personal records.
Check the original artifact and a modified test copy. Record the identity that issued the evidence and review whether it had authority to represent the project. Cryptographic integrity does not show that code is safe, establish its license or settle ownership. Retain source review, build provenance and any other evidence your recipients need.