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.
- Weekly downloads
- 1,038Niche · −30% score
- Versions published
- 15
- First published
- May 2026
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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 4.4.0-self.3 vs 4.4.0-self.2: "node postinstall.mjs"
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 45 · status available -> available, risk high -> high, score 65 -> 45
- new → available · risk high · score 65 · status changed
Evidence
Static findings
3 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 4.4.0-self.3 vs 4.4.0-self.2: "node postinstall.mjs" | 40 |
Show all 4 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 4.4.0-self.3 vs 4.4.0-self.2: "node postinstall.mjs" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="node postinstall.mjs" | 5 |
| low | Large Javascript Payload | package/dist/cli/index.js | 2413904 bytes | 0 |
| low | Large Javascript Payload | package/dist/index.js | 4863893 bytes | 0 |
Manifest
Package metadata
Scripts1
postinstallnode postinstall.mjs
Dependencies17
@ast-grep/cli^0.42.2@ast-grep/napi^0.42.2@clack/prompts^1.4.0@code-yeongyu/comment-checker^0.8.0@modelcontextprotocol/sdk^1.29.0@opencode-ai/plugin^1.15.4@opencode-ai/sdk^1.15.4commander^14.0.3detect-libc^2.1.2diff^9.0.0effect4.0.0-beta.65js-yaml^4.1.1jsonc-parser^3.3.1picocolors^1.1.1picomatch^4.0.4posthog-node^5.34.3vscode-jsonrpc^8.2.1