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
- 41
- Versions published
- 6
- First published
- Nov 2025
- Publisher
- vangelishhhh
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":["[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":["[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 (2 events)
- new → available · risk low · score 0 · status changed
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts1
testecho "Error: no test specified" && exit 1
Dependencies16
@larksuiteoapi/node-sdk^1.55.0@sqlite.org/sqlite-wasm^3.51.2-build6ansi-regex^6.2.2boxen^7.1.1chalk^5.5.0cli-table3^0.6.5commander^14.0.0inquirer^12.9.4mysql2^3.15.1node-fetch^3.3.2process^0.11.10properties-reader^2.3.0proxy-agent^6.4.0string-width^7.2.0strip-ansi^7.1.2ws^8.18.3