Package evidence
@bgord/[email protected]
Install-time lifecycle script: preinstall="bunx only-allow bun"
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["@bgord/[email protected]"],"fail_on":"high"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["@bgord/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Install-time lifecycle script: preinstall="bunx only-allow bun"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk high · score 30 · status changed
Related candidates
Linked campaigns and clusters
bgord
8 members · evidence strength 82Install-time lifecycle script — preinstall="bunx only-allow bun"
8 members · evidence strength 88Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Install-time lifecycle script | package.json | preinstall="bunx only-allow bun" | 30 |
Manifest
Package metadata
Scripts4
buildbash scripts/package-build.shpostbuildbash scripts/prepare-css-files.shpreinstallbunx only-allow bunprepublishbash scripts/prepare-css-files.sh