PkgRadar

Package evidence

@napps/[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
13Established · −30% score
First published
Nov 2025
Publisher
tonysilva16

Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["@napps/[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":["@napps/[email protected]"],"fail_on":"review"}'
Publishertonysilva16
Artifact bytes28,247
Previous version0.0.9
Published2026-02-04T15:44:45.738Z
SHA-256c9d3715cee721268a7742fd5da23f293f5bd8bc3c27ec11e5edab7176e5371cd

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.0.10Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts5
  • buildtsc --noEmit && tsdown --env-file=.env.prod
  • build-devtsc --noEmit && tsdown --env-file=.env.prod
  • build-stagingtsc --noEmit && tsdown --env-file=.env.staging
  • prepublishOnlynpm run build
  • type-checktsc --noEmit
Dependencies9
  • @types/ws^8.18.1
  • better-sse^0.15.1
  • bufferutil^4.0.9
  • chalk^5.6.2
  • chokidar^5.0.0
  • commander^14.0.2
  • qrcode^1.5.4
  • ts-error^1.0.6
  • ws^8.18.3