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
- 61Mature · −50% score
- First published
- Mar 2024
- Publisher
- holons
Effective trust discount applied: −50% (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":["[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":["[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
Known Indicator Filename: package/registry-shim.js
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 22 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Known Indicator Filename | package/registry-shim.js | package/registry-shim.js | 45 |
Manifest
Package metadata
Scripts9
buildnpm run build:browserbuild:browsernode build.jsbuild:bundlenode build.jspreparenpm run buildprepublish:skip-testsnpm run buildprepublishOnlynpm run buildpublish:cdnnpm publish && echo 'Package published to npm and will be available on CDNs within minutes'publish:forcenpm publish --force && echo 'Package force published to npm and will be available on CDNs within minutes'testnode --experimental-vm-modules node_modules/jest/bin/jest.js
Dependencies6
@noble/curves^1.8.0@noble/hashes^1.8.0@scure/base^1.2.0ajv^8.12.0gun^0.2020.1240h3-js^4.1.0