fleetlint Policy for a fleet of repositories
v0.7
Getting started

release/trusted-publishing/helm-chart

Packages are published with trusted publishing

Implements release/trusted-publishing for the helm-chart artifact: it runs when the release publishes one (see artifacts).

Severitywarning
Tiers1
Artifacthelm-chart
Scoperoot
Kindexpr
Sourcelibrary v0.4.0
Selected byfleetlint-recommended@v0.4.0

Requirement

Chart registries have no trusted publishing; the forge’s own registry takes the job token, and signing (release/signing/helm-chart) is what identifies the publisher.

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() > 0

Applies when

false

Check

true

Fix

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


Generated by fleetlint docs from catalog v0.4.0.