Package evidence
@mercuryworkshop/[email protected]
Install-time lifecycle script: preinstall="npx only-allow pnpm"
Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Versions published
- 11Established · −30% score
- First published
- Jun 2024
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["@mercuryworkshop/[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":["@mercuryworkshop/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: preinstall added in 1.1.0 vs 1.0.2: "npx only-allow pnpm"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (3 events)
- available → available · risk high · score 45 · status available -> available, risk high -> high, score 51 -> 45
- available → available · risk high · score 51 · status available -> available, risk high -> high, score 100 -> 51
- new → available · risk high · score 100 · status changed
Related candidates
Linked campaigns and clusters
Install-time lifecycle script — preinstall="npx only-allow pnpm"
21 members · evidence strength 90Evidence
Static findings
1 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 1.1.0 vs 1.0.2: "npx only-allow pnpm" | 40 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | preinstall added in 1.1.0 vs 1.0.2: "npx only-allow pnpm" | 40 |
| low | Install-time lifecycle script | package.json | preinstall="npx only-allow pnpm" | 5 |
Manifest
Package metadata
Scripts20
buildrspack build --mode productionbuild:allnpm run build && npm run build:typesbuild:typesrslib build && rm -rf dist/tempdevnode server.jsdev:debugDEBUG=1 node server.jsdocstypedocdocs:devtypedoc --options typedoc.dev-facing.jsondocs:servenpx serve _docs; typedoc --watchformatprettier --write .format:docsremark "docs/**/*.{md,mdx}" --outputlinteslint ./src/lint:allnpm run lint && npm run lint:workflowslint:fixeslint ./src/ --fixlint:workflowsactionlint .github/workflows/*.ymlpreinstallnpx only-allow pnpmpubnpm publish --no-git-checks --access publicrewriter:buildcd rewriter/wasm/ && bash build.sh && cd ../../testnpm run test:package && npm run test:integrationtest:integrationnpx playwright testtest:packageava tests/ci/packageValidation.js
Dependencies8
@mercuryworkshop/bare-mux^2.1.9dom-serializer^2.0.0domhandler^5.0.3domutils^3.2.2htmlparser210.0.0idb^8.0.3parse-domain^8.2.2set-cookie-parser^2.7.1