release/trusted-publishing/maven
Packages are published with trusted publishing
Implements release/trusted-publishing for the maven artifact: it runs when the release publishes one (see artifacts).
| Severity | warning |
| Tiers | 1 |
| Artifact | maven |
| Scope | root |
| Kind | expr |
| Source | library v0.5.0 |
| Selected by | fleetlint-recommended@v0.5.0 |
Requirement
Maven Central has no trusted publishing (OIDC) yet; its publishing token stays a CI secret.
Why
A registry token in CI secrets is valid for months and publishes from anywhere once leaked; an OIDC token is minted per run, scoped to this repository and workflow, and expires in minutes.
Capability applies when
repo.artifacts.size() > 0Applies when
falseCheck
trueFix
Register the repository and workflow as a trusted publisher on the registry, grant id-token: write to the release job and delete the token secret.
Agent instruction: Grant id-token: write on the publishing job, remove the registry token from env/with (pypa/gh-action-pypi-publish without password, npm publish with npm 11.5.1 or newer, rust-lang/crates-io-auth-action for cargo, rubygems/release-gem for gems, NuGet/login for nuget.org, dart-lang/setup-dart for pub.dev; on GitLab add id_tokens: with the registry’s audience), and tell the user to register the trusted publisher and delete the secret.
Sources
- https://docs.github.com/en/actions/security-for-github-actions/security-hardening-your-deployments/about-security-hardening-with-openid-connect (guidance)
- https://docs.gitlab.com/ci/secrets/id_token_authentication/ (spec, id_tokens)
- https://fleetlint.org/baseline/#releases (convention)
- https://fleetlint.org/baseline/#security
Generated by fleetlint docs from catalog v0.5.0.