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.
- Weekly downloads
- 3,025Niche · −30% score
- Versions published
- 375
- First published
- Dec 2025
- Publisher
- skrillex12242018
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@skrillex1224/[email protected]"],"fail_on":"review"}'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":["@skrillex1224/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched ".npmrc"
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 review · score 2 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/package.json | matched ".npmrc" | 3 |
Manifest
Package metadata
Scripts4
buildnode build.jsprepublishOnlynpm run buildreleasenpm run build && npm version patch && npm publish --registry https://registry.npmjs.org --access public --userconfig ../.npmrctestecho "Error: no test specified" && exit 1
Dependencies11
delay^4.4.1express^4.18.2fingerprint-generator2.1.80fingerprint-injector2.1.80generative-bayesian-network2.1.80got-scraping^4.1.3header-generator2.1.80jimp^1.6.1picomatch^4.0.3serialize-error^12.0.0uuid^13.0.0