Add the cicd-gha-unpinned-action rule to the catalog - #309
Open
Dyc0de wants to merge 1 commit into
Open
Conversation
Registers the rule emitted by boostsec-scanner-native as cicd-gha-unpinned-action, and rolls the baseline image pin forward to the build that carries it (8f8a409), so the catalog entry and the image that backs it land together. Categorized under supply-chain-missing-artifact-integrity-verification alongside cicd-unpinned-dependencies: an unpinned reference is a download without integrity verification, the same failure mode as a missing lockfile. Note the pin jumps 19 commits from 6b6cf90, not just the one adding this rule. Eighteen of those are the #190 lockfile rework, so this also changes cicd-unpinned-dependencies here: it gains eight ecosystems and resolves a lock file from the repository root, which stops it reporting every member of a cargo or uv workspace. Tracked by boostsecurityio/workspace#296
Dyc0de
marked this pull request as ready for review
August 21, 2026 22:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Registers
cicd-gha-unpinned-actionin the catalog and rolls the baseline imagepin forward to the build that emits it, so the entry and the image that backs it
land together.
The rule itself shipped in
boostsec-scanner-native#96;
this makes it reachable by customers.
The catalog entry
Categorized under
supply-chain-missing-artifact-integrity-verification, matchingcicd-unpinned-dependenciesrather than thesupply-chain-cicd-weak-configurationof its closest analogue
cicd-circleci-unversioned-orb. An unpinneduses:is adownload without integrity verification — the same failure mode as a missing
lockfile — so it groups with the other pinning rule.
recommended: true, matching every siblingcicd-*rule. Worth being explicitabout what that flag does and does not do: its only consumer is
policy-service'srecommendedRulesresolver, which populates the dashboard's "Suggested Rules"button. Rule enablement comes from a policy's own
enabled_rulesand never readsthis flag, so this does not enable the rule for anyone or change finding volume.
The pin bump is bigger than this rule
The pin moves
6b6cf90→8f8a409, which is 19 commits, not one. Eighteen ofthem are the
#190lockfile rework, so this also changescicd-unpinned-dependencieshere: eight more ecosystems, and lock files resolved from the repository root, which
stops it reporting every member of a cargo or uv workspace. Unavoidable — the new
rule exists only in the newer build — but it should be reviewed as part of this
change, not discovered later.
Known gap
ref:points atrules/cicd-gha-unpinned-action.html, which does not exist yet —the docs page is
workspace#274. The link
404s until that ships.
Tracked by https://github.com/boostsecurityio/workspace/issues/296