PkgRadar

Package evidence

@naster17/[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
11
First published
May 2026
Publisher
naster17

Recommended action

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

Inspect tarballAdd 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":["@naster17/[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":["@naster17/[email protected]"],"fail_on":"review"}'
Publishernaster17
Artifact bytes7,440
Previous version1.14.58-PRO
Published2026-06-01T19:34:37.747Z
SHA-256bc653286754ed78c2e485e3809db87538943f810dece36f88c4cf8328e2f9c55

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
1.14.59-PROVersion
Status history (2 events)
  1. new → available · risk low · score 0 · status changed
  2. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts2
  • buildtsc
  • typechecktsgo --noEmit
Dependencies3
  • @opencode-ai/sdk1.14.59-PRO
  • effect4.0.0-beta.59
  • zod4.1.8