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
- 38
- First published
- Apr 2026
- Publisher
- kenkaiiii
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":["@kenkaiiii/[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":["@kenkaiiii/[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
Scripts5
buildnode scripts/build-skills.mjs && tsc && node scripts/copy-python.mjsbuild:pythonnode scripts/copy-python.mjsbuild:skillsnode scripts/build-skills.mjschecknode scripts/build-skills.mjs && tsc --noEmittestnode scripts/build-skills.mjs && vitest run
Dependencies8
@kenkaiiii/gg-agent4.8.6@kenkaiiii/gg-ai4.8.6@kenkaiiii/ggcoder4.8.6chalk^5.6.2ink^7.0.2react^19.2.5ws^8.18.0zod^4.4.3