PkgRadar

npm · registry.npmjs.org

@lpm-registry/cli

Install-time lifecycle script: postinstall="node scripts/install-binary.js"

Why PkgRadar flagged 0.59.1

SeveritySignalEvidence
highNew Lifecycle Script Vs Previouspostinstall added in 0.59.1 vs 0.59.0: "node scripts/install-binary.js" · package.json

Scanned versions

VersionVerdictScoreScanned (UTC)
0.60.0Review12026-06-13
0.59.1High risk452026-06-10
0.59.0Low risk02026-06-10
0.58.0Review162026-06-09
0.57.0Review162026-06-07
0.56.0Review162026-06-06
0.55.0Review162026-06-05
0.54.0Review162026-06-04
0.53.0Review162026-06-03
0.52.0Review162026-06-02
0.51.0Review162026-06-01
0.50.0Review162026-05-30
0.49.0Review162026-05-29
0.48.2Review252026-05-28
0.47.0Review252026-05-26
0.46.0Review972026-05-24
0.45.0Review972026-05-24

Campaign attribution

Part of the asteroiddao npm campaign campaign.

Block this in CI

PkgRadar gates @lpm-registry/cli (and every other dependency) before it merges. One line in your pipeline:

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