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
- 18
- Versions published
- 6
- First published
- Apr 2026
- Publisher
- imenam
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@imenam/[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":["@imenam/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts8
buildtsc && npm run build:guibuild:guicd public && npx vite builddevconcurrently -n server,gui -c blue,green "npm run dev:server" "npm run dev:gui"dev:guicd public && npx vitedev:servertsx src/index.tsprepublishOnlynpm run buildreleasenpm version patch && npm run build && npm publish --access public && git push origin master --follow-tagsstartnode dist/index.js
Dependencies7
@imenam/mcp-gui-interface^1.0.5@modelcontextprotocol/sdk^1.28.0body-parser^2.2.2dotenv^17.3.1express^5.2.1puppeteer^24.40.0zod^4.3.6