PkgRadar

npm · registry.npmjs.org

@crewhaus/egress-matcher-semantic

Suspicious Publish Context: {"package_age_days":4,"publisher":"studiomaxops","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"matcher"},"version_anomaly":false,"new_account":false}

Why PkgRadar flagged 0.1.2

SeveritySignalEvidence
mediumSuspicious Publish Context{"package_age_days":4,"publisher":"studiomaxops","burst_same_day":1,"burst_week":1,"lure":{"kind":"token_affix","target":"matcher"},"version_anomaly":false,"new_account":false}

Scanned versions

VersionVerdictScoreScanned (UTC)
0.1.2Review102026-06-15
0.1.3Review102026-06-15

Block this in CI

PkgRadar gates @crewhaus/egress-matcher-semantic (and every other dependency) before it merges. One line in your pipeline:

pkgradar gate --ecosystem npm @crewhaus/[email protected]
@crewhaus/egress-matcher-semantic — npm security scan | PkgRadar