PkgRadar

npm · registry.npmjs.org

@plurnk/plurnk-schemes-http

Suspicious Publish Context: {"package_age_days":7,"publisher":"possumtechcom","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":false}

Why PkgRadar flagged 0.7.0

SeveritySignalEvidence
mediumSuspicious Publish Context{"package_age_days":7,"publisher":"possumtechcom","burst_same_day":2,"burst_week":2,"lure":null,"version_anomaly":false,"new_account":false}

Scanned versions

VersionVerdictScoreScanned (UTC)
0.13.0Low risk02026-06-20
0.12.0Low risk02026-06-19
0.11.0Low risk02026-06-19
0.8.0Low risk02026-06-19
0.7.0Review102026-06-18
0.3.0Low risk02026-06-18
0.6.0Low risk02026-06-18
0.2.0Low risk02026-06-15
0.1.0Low risk02026-06-15

Block this in CI

PkgRadar gates @plurnk/plurnk-schemes-http (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @plurnk/[email protected]