Skip to content

fix(threatcrush-scan): pin the CLI install spec instead of @latest #952

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 2 commits into from
Aug 11, 2026
+10 −4
Merged

fix(threatcrush-scan): pin the CLI install spec instead of @latest #952

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
071d818
fix(threatcrush-scan): pin the CLI install spec instead of @latest
ralyodio Aug 11, 2026
87a29cb
docs(threatcrush-scan): document the pinned install spec
ralyodio Aug 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/actions/threatcrush-scan/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ sh1pt actions install threatcrush-scan --repo owner/name --pr
| --- | --- | --- |
| `scanPath` | `.` | Path to scan, relative to the repository root. |
| `nodeVersion` | `20` | See *Node 20, deliberately*, below. |
| `threatcrushPackageSpec` | `@profullstack/threatcrush@latest` | npm spec used to install the CLI. |
| `threatcrushPackageSpec` | `@profullstack/threatcrush@0.11.0` | npm spec used to install the CLI. Pinned rather than `@latest` so one bad publish cannot break every consumer at once; bump it in a pack release. |
| `failOn` | *(empty)* | Comma-separated severities that fail the job, e.g. `critical,high`. Empty is report-only. |
| `uploadSarif` | `true` | Upload to the Security tab. |

Expand Down
12 changes: 9 additions & 3 deletions packages/actions/threatcrush-scan/sh1pt.actionpack.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ description: >-
Scans pull requests for hardcoded credentials, injection, SSRF, unsafe
deserialisation and dependency tampering, and uploads SARIF to the Security
tab.
version: 1.1.0
version: 1.2.0
publisher: profullstack
visibility: public
license: MIT
Expand All @@ -32,8 +32,14 @@ inputs:
that fails without a full toolchain.
threatcrushPackageSpec:
type: string
default: '@profullstack/threatcrush@latest'
description: npm spec used to install the CLI.
default: '@profullstack/threatcrush@0.11.0'
description: >-
npm spec used to install the CLI. Pinned, not `@latest`: a scanner that
runs on every pull request is a dependency, and `@latest` means one bad
publish breaks CI in every repo that installed this pack at once — which
is exactly what a `workspace:` protocol slip in 0.7.0/0.7.1 did. Bump this
deliberately, in a pack release, so the fleet re-syncs consumers to a
version that was checked first.
failOn:
type: string
default: ''
Expand Down
Loading