PkgRadar

Package evidence

@super-repo/[email protected]

no 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
48
First published
May 2026
Publisher
interc0der

Recommended action

Looks clean — keep monitoring

No 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":["@super-repo/[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":["@super-repo/[email protected]"],"fail_on":"review"}'
Publisherinterc0der
Artifact bytes70,512
Previous version0.4.1-b.2
Published2026-05-29T23:02:52.986Z
SHA-256c6d64b41f3ac9ac1ecffc1fb01851d2526957464db77a3020f8eafa1d53f5b38

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

low
Last checked
lowRisk
0Score
0.4.1-b.3Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Dependencies6
  • @super-repo/cli0.4.1-b.3
  • @super-repo/czar0.4.1-b.3
  • ink^5.0.1
  • ink-text-input^6.0.0
  • meow^13.2.0
  • react^18.3.1