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

release/trusted-publishing/cpp

Packages are published with trusted publishing

Implements release/trusted-publishing for cpp.

Severitywarning
Tiers1
Stackscpp
Scoperoot
Kindexpr
Sourcelibrary v0.2.0
Selected byfleetlint-recommended@v0.2.0

Requirement

C and C++ packages are not uploaded to a registry with trusted publishing (vcpkg and Conan Center take ports by pull request).

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.

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; on GitLab add id_tokens: with the registry’s audience), and tell the user to register the trusted publisher and delete the secret.

See: https://fleetlint.org/baseline/#releases, https://fleetlint.org/baseline/#security, https://fleetlint.org/stacks/#cc


Generated by fleetlint docs from catalog v0.2.0.