Skip to content

chore(threatcrush-scan): pin 0.11.3, and pack 2.0.1 to re-sync consumers #971

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 1 commit into from
Aug 17, 2026
Merged

chore(threatcrush-scan): pin 0.11.3, and pack 2.0.1 to re-sync consumers #971

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions packages/actions/threatcrush-scan/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,8 @@ 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@0.11.2` | 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. |
| `threatcrushIntegrity` | *(sha512 of 0.11.2)* | SRI hash of that tarball. The workflow downloads, hashes and compares before installing, and refuses to install on a mismatch. Bump it with the spec — read it from `npm view <spec> dist.integrity`. Empty skips the check. |
| `threatcrushPackageSpec` | `@profullstack/threatcrush@0.11.3` | 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. |
| `threatcrushIntegrity` | *(sha512 of 0.11.3)* | SRI hash of that tarball. The workflow downloads, hashes and compares before installing, and refuses to install on a mismatch. Bump it with the spec — read it from `npm view <spec> dist.integrity`. Empty skips the check. |
| `failOn` | *(empty)* | Comma-separated severities that fail the job, e.g. `critical,high`. Empty is report-only. |
| `uploadSarif` | `true` | Upload to the Security tab. Emits `security-events: write`. |
| `commentOnPr` | `true` | Post the report as a pull request comment. Emits `pull-requests: write`. |
Expand Down
6 changes: 3 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: 2.0.0
version: 2.0.1
publisher: profullstack
visibility: public
license: MIT
Expand All @@ -32,7 +32,7 @@ inputs:
that fails without a full toolchain.
threatcrushPackageSpec:
type: string
default: '@profullstack/threatcrush@0.11.2'
default: '@profullstack/threatcrush@0.11.3'
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
Expand All @@ -42,7 +42,7 @@ inputs:
version that was checked first.
threatcrushIntegrity:
type: string
default: 'sha512-8N3jqCQixK0Onc+/bvuJaNCSvGZlJYZcSAGsd1nEfRZ4kOu1Ifom7Bd1t2muYJAmAxBTPmz1iseWSay/0gg3Gw=='
default: 'sha512-lxWvTtLDgckiWlRB3wMSoBNfMZ/3ao0CcmwETGyKclc+5NMU5Pl0jXSr0h+QrTtfxh7TNStk4ZgP5h8xbEvIWw=='
description: >-
Subresource-integrity hash of the tarball named by threatcrushPackageSpec,
in npm's own `sha512-<base64>` form. The workflow downloads, hashes and
Expand Down
Loading