PkgRadar

npm · registry.npmjs.org

@github/computer-use-mcp

Install-time lifecycle script: install="node package.js install"

Why PkgRadar flagged 0.1.29

SeveritySignalEvidence
highNew Lifecycle Script Vs Previousinstall added in 0.1.29 vs 0.1.28: "node package.js install" · package.json

Scanned versions

VersionVerdictScoreScanned (UTC)
0.1.29High risk452026-06-10
0.1.44Low risk02026-06-10
0.1.42Low risk02026-06-08
0.1.41Low risk02026-06-08
0.1.40Low risk02026-06-07
0.1.39Low risk02026-06-07
0.1.38Low risk02026-06-07
0.1.37Low risk02026-06-07
0.1.35Low risk02026-06-05
0.1.34Low risk02026-06-05
0.1.33Low risk02026-06-05
0.1.32Low risk02026-06-05
0.1.31Low risk02026-06-03
0.1.30Low risk02026-06-02
0.1.28Low risk02026-06-02

Campaign attribution

Part of the asteroiddao npm campaign campaign.

Block this in CI

PkgRadar gates @github/computer-use-mcp (and every other dependency) before it merges. One line in your pipeline:

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