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
- Jun 2026
- Publisher
- rcortex
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":["@redsocs/[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":["@redsocs/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":2,"publisher":"rcortex","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}
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 10 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":2,"publisher":"rcortex","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true} | 10 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":2,"publisher":"rcortex","burst_same_day":1,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true} | 10 |
| low | Large Javascript Payload | package/dist/spamwarden.min.js | 6477780 bytes | 0 |
Manifest
Package metadata
Scripts8
buildnode build.jsdev:buildif [ -z "$MODEL_DECRYPTION_KEY" ]; then echo "Error: MODEL_DECRYPTION_KEY environment variable is required"; exit 1; fi && openssl enc -d -pbkdf2 -in model.json.enc -out model.json -k "$MODEL_DECRYPTION_KEY" && (npm run build; status=$?; openssl enc -e -pbkdf2 -in model.json -out model.json.enc -k "$MODEL_DECRYPTION_KEY"; rm -f model.json; exit $status) && echo "✅ Build and re-encryption complete."dev:lazyif [ -z "$MODEL_DECRYPTION_KEY" ]; then echo "Error: MODEL_DECRYPTION_KEY environment variable is required"; exit 1; fi && openssl enc -d -pbkdf2 -in model.json.enc -out model.json -k "$MODEL_DECRYPTION_KEY" && (npm run lazy && npm run build; status=$?; openssl enc -e -pbkdf2 -in model.json -out model.json.enc -k "$MODEL_DECRYPTION_KEY"; rm -f model.json; exit $status) && echo "✅ Lazy import, build, and re-encryption complete."dev:testif [ -z "$MODEL_DECRYPTION_KEY" ]; then echo "Error: MODEL_DECRYPTION_KEY environment variable is required"; exit 1; fi && openssl enc -d -pbkdf2 -in model.json.enc -out model.json -k "$MODEL_DECRYPTION_KEY" && (npm run build; build_status=$?; rm -f model.json; if [ $build_status -ne 0 ]; then exit $build_status; fi; npm test)lazynode lazy.jstestnode tests/test.jstest-servernode tests/simulate/server.jsversionnode -e "console.log(require('./dist/spamwarden.min.js').version)"