Package evidence
@momidala/[email protected]
Install-time lifecycle script: postinstall="node ./build/cli.js install-command"
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
- 4
- First published
- May 2026
- Publisher
- lbarchett
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@momidala/[email protected]"],"fail_on":"review"}'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":["@momidala/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Install-time lifecycle script: postinstall="node ./build/cli.js install-command"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (4 events)
- available → available · risk review · score 5 · status available -> available, risk high -> review, score 47 -> 5
- available → available · risk high · score 47 · status available -> available, risk high -> high, score 59 -> 47
- available → available · risk high · score 59 · status available -> available, risk high -> high, score 84 -> 59
- new → available · risk high · score 84 · status changed
Related candidates
Linked campaigns and clusters
lbarchett
2 members · evidence strength 60Install-time lifecycle script — postinstall="node ./build/cli.js install-command"
2 members · evidence strength 66Install Lifecycle Remote Or Exec — postinstall="node ./build/cli.js install-command"
2 members · evidence strength 66Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Install-time lifecycle script | package.json | postinstall="node ./build/cli.js install-command" | 5 |
Manifest
Package metadata
Scripts4
buildtsc && chmod 755 build/index.js build/cli.jspostinstallnode ./build/cli.js install-commandpreuninstallnode ./build/cli.js uninstall-commandtesttsc && node --test build/parts.test.js build/cli.test.js build/auth.test.js build/diff-patch.test.js build/session-command.test.js build/autostart.test.js build/registry.test.js build/sessions.test.js build/index.test.js
Dependencies5
@modelcontextprotocol/sdk1.29.0@opencode-ai/sdk1.14.25diff^9.0.0proper-lockfile^4.1.2zod4.3.6