release/signing/nuget
Release artifacts are signed
Implements release/signing for the nuget artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | nuget |
| Scope | root |
| Kind | outcome |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
NuGet packages are signed (dotnet nuget sign) or the binaries inside carry an Authenticode signature (signtool, Azure Trusted Signing) in the workflow that pushes them. nuget.org adds its own repository signature on upload; that proves the registry, not the author.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Sign packages with dotnet nuget sign (or binaries with signtool / Azure Trusted Signing) before dotnet nuget push.
Agent instruction: Use the artifact’s own signing format when it has one. Otherwise add sigstore/cosign-installer and a signing step after the artifacts are built. Files: cosign sign-blob --yes --bundle checksums.txt.sigstore.json checksums.txt and upload the bundle. Container image: cosign sign --yes <image>@<digest> using the digest output of the build step, with id-token: write on the job.
See: https://fleetlint.org/baseline/#releases, https://learn.microsoft.com/nuget/create-packages/sign-a-package
Generated by fleetlint docs from catalog v0.3.1.