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
- 28
- Versions published
- 4
- First published
- Jun 2026
- Publisher
- neomei
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":["@neomei/[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":["@neomei/[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
buildtscdevtsc --watchlinttsc --noEmitprepublishOnlynpm run buildreleasesemantic-releasestartnode dist/cli.jsstart:winchcp 65001 >nul & node dist/cli.js starttypechecktsc --noEmit
Dependencies11
@opencode-ai/sdk^1.0.0@rongcloud/imlib-next5.36.6axios^1.15.0commander^12.0.0fake-indexeddb^6.2.5jsdom^24.0.0pino^9.0.0pino-pretty^11.0.0qrcode^1.5.4ws^8.16.0zod^3.23.0