PkgRadar

npm · registry.npmjs.org

next-fetch-panel

Suspicious Publish Context: {"package_age_days":3,"publisher":"lukazovic","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"next"},"version_anomaly":false,"new_account":true}

Why PkgRadar flagged 0.4.2

SeveritySignalEvidence
mediumSuspicious Publish Context{"package_age_days":3,"publisher":"lukazovic","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"next"},"version_anomaly":false,"new_account":true}

Scanned versions

VersionVerdictScoreScanned (UTC)
0.4.2Review102026-06-12
0.4.1Review102026-06-12
0.4.0Low risk02026-06-11
0.3.0Low risk02026-06-10
0.2.0Low risk02026-06-10
0.1.1Low risk02026-06-10
0.1.0Low risk02026-06-09

Block this in CI

PkgRadar gates next-fetch-panel (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm [email protected]
Start free — 25 scans / moView full evidence