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
- 9
- First published
- May 2026
- Publisher
- gamedaysuits
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":"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":["[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
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 low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts18
auditnode bin/cli.js auditinitnode bin/cli.js initlintnode bin/cli.js lintprepublishOnlynpm testsyncnode bin/cli.js synctestnode --test test/*.test.jstest:contentnode --test test/content.test.jstest:content-syncnode --test test/content-sync.test.jstest:formatnode --test test/format.test.jstest:hugonode --test test/hugo-e2e.test.jstest:init-helpnode --test test/init-help.test.jstest:lintnode --test test/lint.test.jstest:methodsnode --test test/methods.test.jstest:pairsnode --test test/pairs.test.jstest:redteamnode --test test/redteam.test.jstest:sync-pairsnode --test test/sync-pairs.test.jstest:unitnode --test test/sync.test.jswatchnode bin/cli.js watch