Package evidence
[email protected]
Install Lifecycle Remote Or Exec: postinstall="node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\""
Trust signals
Why this verdict
PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.
- Versions published
- 51
- First published
- Mar 2026
- Publisher
- thatsrajan
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
Block this release in CIcurl · GitHub Actions
Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer $PKGRADAR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"high"}'GitHub Actions step:
- name: PkgRadar gate
run: |
curl -fsS https://pkgradar.com/gate/npm \
-H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
-H "Content-Type: application/json" \
-d '{"specs":["[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 1.3.0-beta.0 vs 1.2.9: "node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\""
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (2 events)
- available → available · risk high · score 75 · status available -> available, risk high -> high, score 45 -> 75
- new → available · risk high · score 45 · status changed
Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.0-beta.0 vs 1.2.9: "node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\"" | 40 |
| high | Install Lifecycle Remote Or Exec | package.json | postinstall="node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\"" | 30 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.3.0-beta.0 vs 1.2.9: "node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\"" | 40 |
| high | Install Lifecycle Remote Or Exec | package.json | postinstall="node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\"" | 30 |
| low | Install-time lifecycle script | package.json | postinstall="node -e \"console.log('\\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\\n')\"" | 5 |
Manifest
Package metadata
Scripts12
buildtsc -p tsconfig.jsondevtsx src/cli.tsdoctornpm run build --silent && node dist/cli.js doctorpostinstallnode -e "console.log('\nVidLens MCP installed. From a checkout run: npm run setup. For the global command run: npm install -g .\n')"release:publishnpm test && npm publish --access publicrelease:verifynpm test && npm pack --dry-runsetupnpm run build --silent && node dist/cli.js setupsmokenode dist/scripts/smoke.jssmoke:drynode dist/scripts/smoke.js --dry-runstartnode dist/cli.jstestnpm run build && node --test dist/test/*.test.jsupdate-depsnpm run build --silent && node dist/cli.js update-deps
Dependencies3
@google/genai^1.45.0@modelcontextprotocol/sdk^1.17.4execa^9.6.0