PkgRadar

Package evidence

[email protected]

Remote Payload: matched "curl "

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
5
First published
Jun 2026
Publisher
tunderules

Recommended action

Review before promoting

Mixed 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":["[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"}'
Publishertunderules
Artifact bytes47,840
Previous version0.2.0
Published2026-06-05T18:42:27.994Z
SHA-256824c5862d3936587b9df16051df90bd6c6a4eb143355aa0b764c3854232b28bc

Why flagged

What the scanner saw

Remote Payload: matched "curl "

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
17Score
0.2.1Version
Status history (1 event)
  1. newavailable · risk review · score 17 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumRemote Payloadpackage/tools/local-first-run-test.shmatched "curl "12
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
mediumRemote Payloadpackage/tools/local-first-run-test.shmatched "curl "12
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node bin/postinstall.js"5

Manifest

Package metadata

Scripts3
  • pack:checknpm pack --dry-run
  • postinstallnode bin/postinstall.js
  • testif [ -f tests/validate-package.sh ]; then bash tests/validate-package.sh; fi && node bin/ucp-shopper-skill.js doctor --json