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
- 17
- First published
- May 2026
- Publisher
- hughlv
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":["@supen-ai/[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":["@supen-ai/[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
Scripts3
buildtsc && node scripts/bundle-daemon.mjsprepublishOnlynpm run buildtypechecktsc --noEmit
Dependencies21
@larksuiteoapi/node-sdk^1.59.0@modelcontextprotocol/sdk^1.29.0@supabase/supabase-js^2.47.0axios^1.16.0commander^13.0.0cron-parser^5.5.0dingtalk-stream^2.1.0discord.js^14.25.1https-proxy-agent^7.0.6ink^7.0.0ink-text-input^6.0.0js-yaml^4.1.1pino^9.6.0pino-pretty^13.0.0playwright^1.58.2react^19.2.4rrule^2.8.1undici^7.24.2ws^8.20.1yaml^2.8.3zod^4.3.6