PkgRadar

Package evidence

@juigorg/[email protected]

no static findings

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
1
First published
May 2024
Publisher
npm
External confirmation
MAL-2025-42596OSV match · pinned to high regardless of other signals

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

See the evidence — freeAdd to CI gate
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":["@juigorg/[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":["@juigorg/[email protected]"],"fail_on":"high"}'
Publishernpm
Artifact bytes412
Previous versionnone
Published2024-05-29T08:10:55.292Z
SHA-256601f1a25632013b747f7f6472c4b760c38e9d543d708d469f3bc8585c784c3bc

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

high
Last checked
highRisk
0Score
0.0.1-security.0Version
Status history (1 event)
  1. new → available · risk high · score 0 · status changed

Evidence

Static findings

No findings stored for this release.