PkgRadar

Package evidence

@miaskiewicz/[email protected]

Oversized Unscanned: tarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only

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
16
First published
Jun 2026
Publisher
miaskiewicz

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["@miaskiewicz/[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":["@miaskiewicz/[email protected]"],"fail_on":"review"}'
Publishermiaskiewicz
Artifact bytes243,281,257
Previous version0.2.12
Published2026-06-13T21:51:37.551Z
SHA-256

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":5,"publisher":"miaskiewicz","burst_same_day":7,"burst_week":7,"lure":{"kind":"token_affix","target":"turbo"},"version_anomaly":false,"new_account":false}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
0.2.13Version
Status history (2 events)
  1. scan_error → available · risk review · score 10 · status scan_error -> available, risk none -> review, score none -> 10
  2. new → scan_error · risk none · score — · refusing to fetch https://registry.npmjs.org/@miaskiewicz/turbo-test/-/turbo-test-0.2.13.tgz: content-length 79731997 exceeds 50000000

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":5,"publisher":"miaskiewicz","burst_same_day":7,"burst_week":7,"lure":{"kind":"token_affix","target":"turbo"},"version_anomaly":false,"new_account":false}10
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":5,"publisher":"miaskiewicz","burst_same_day":7,"burst_week":7,"lure":{"kind":"token_affix","target":"turbo"},"version_anomaly":false,"new_account":false}10
lowOversized Unscannedmanifesttarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only0

Manifest

Package metadata

Scripts3
  • buildbash scripts/npm-build.sh
  • prepublishOnlybash scripts/npm-build.sh
  • testnode --test 'test/*.mjs'
Dependencies2
  • @miaskiewicz/turbo-dom^0.2.0
  • esbuild^0.21.0