Skip to content

ci: add a Plumber check on the workflows with its score badge - #2644

Open
Totara-thib wants to merge 1 commit into
pmndrs:nextfrom
Totara-thib:plumber-score
Open

Totara-thib wants to merge 1 commit into
pmndrs:nextfrom
Totara-thib:plumber-score

Conversation

@Totara-thib

Copy link
Copy Markdown
Contributor

Why

Follows up on #2632, merged earlier. That PR fixed three classes of findings in the workflows (floating third-party refs, missing token permissions, tokens left in checkouts). This keeps them fixed: a small workflow runs the Plumber CLI on pushes to next and on pull requests and gates at 85 points, so one small finding never blocks a PR.

What

One workflow file, an overlay that keeps the built-in defaults and trusts the five extra actions this repository uses, and the score badge in the README. Internal tooling only, so no changeset.

Score badge: It works like OpenSSF Scorecard's published results: every run publishes the score, the badge shows next, and a failed publish never fails your CI. No token or secret is needed. The badge reads gray UNKNOWN until the first run on next. If you want the check but not the badge, removing the score-push line is the whole opt-out.

I work on Plumber. If you do not want the tool, no hard feelings, say so and I close this PR, the hardening stands on its own.

Checklist

  • Ready to be merged

A small workflow runs the Plumber CLI on pushes to next and on pull
requests. It checks the GitHub workflows for the classes of findings
the previous commits fixed (floating action refs, missing permissions,
tokens left in checkouts) and fails under 85 points, so one small
finding never blocks a pull request. The overlay keeps the built-in
defaults and trusts the five actions this repository uses on top of
them, all pinned by commit. The README gets the score badge in the
badge block.
@changeset-bot

changeset-bot Bot commented Oct 20, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 76c2e89

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant