release/signing/maven
Release artifacts are signed
Implements release/signing for the maven artifact: it runs when the release publishes one (see artifacts).
| Severity | error |
| Tiers | 1 |
| Artifact | maven |
| Scope | root |
| Kind | outcome |
| Source | library v0.8.0 |
| Selected by | fleetlint-recommended@v0.8.0 |
Requirement
Artifacts for Maven Central are signed with PGP (Maven’s gpg or sign plugin, Gradle’s signing plugin or signAllPublications(), JReleaser), or JARs are signed with jarsigner in the release workflow.
Why
Checksums prove integrity; only a signature proves who built it.
Capability applies when
release.exists || repo.artifacts.size() > 0Fix
Maven: add maven-gpg-plugin (or sign-maven-plugin) to the release profile; Gradle: apply the signing plugin to the Maven publication. The key comes from CI secrets.
Agent instruction (from release/signing): 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.
A finding that names no file points at the first existing file of pom.xml, build.gradle.kts or build.gradle, else pom.xml.
Sources
- https://csrc.nist.gov/pubs/sp/800/218/final (standard, PS.2.1: Make software integrity verification information available to software acquirers)
- https://github.com/ossf/scorecard/blob/main/docs/checks.md (standard, Signed-Releases)
- https://fleetlint.org/baseline/#releases
- https://central.sonatype.org/publish/requirements/gpg/ (spec)
Generated by fleetlint docs from catalog v0.8.0.