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

release/trusted-publishing/node

Packages are published with trusted publishing

Implements release/trusted-publishing for node.

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

Requirement

A tag-triggered GitHub or GitLab workflow that publishes to npm (npm|pnpm|yarn npm|bun publish, JS-DevTools/npm-publish) uses trusted publishing: id-token: write (npm 11.5.1 or newer) and no NPM_TOKEN/NODE_AUTH_TOKEN or --token from secrets; on GitLab id_tokens:.

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

tagged_workflows().filter(w, ci_kind(w) in ["github", "gitlab"] && steps(w).exists(s,
  s.uses.startsWith("JS-DevTools/npm-publish")
  || s.run.matches("\\b(npm publish|pnpm publish|yarn npm publish|bun publish)\\b"))).size() > 0

Check

For each item in:

tagged_workflows().filter(w, ci_kind(w) in ["github", "gitlab"] && steps(w).exists(s,
  s.uses.startsWith("JS-DevTools/npm-publish")
  || s.run.matches("\\b(npm publish|pnpm publish|yarn npm publish|bun publish)\\b")))
ci_kind(item) == "gitlab"
  ? text(item).matches("(?m)^\\s*id_tokens:")
  : text(item).matches("id-token:\\s*write")
    && !grep(item, r'^\s*-?\s*(?:NODE_AUTH_TOKEN|NPM_TOKEN)\s*:\s*["\x27]?\$\{\{\s*secrets\.(\w+)').exists(m, m.match.upperAscii() != "GITHUB_TOKEN")
    && !grep(item, r'--token[\s=]+["\x27]?\$\{\{\s*secrets\.(\w+)').exists(m, m.match.upperAscii() != "GITHUB_TOKEN")

Fix

Register the workflow as a trusted publisher on npmjs.com, publish with npm 11.5.1+ from a job with id-token: write, and delete the NPM_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/#nodejs--typescript


Generated by fleetlint docs from catalog v0.2.0.