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
- 5
- First published
- Jun 2026
- Publisher
- yjjeong
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":["@yjjeong/[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":["@yjjeong/[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
Scripts11
buildtsc && node scripts/copy-assets.mjsdevtsc --watchformatprettier --write "src/**/*.{ts,tsx}" "test/**/*.{ts,tsx}"format:checkprettier --check "src/**/*.{ts,tsx}" "test/**/*.{ts,tsx}"linteslint .prepublishOnlynpm run typecheck && npm run build && npm run test:publishstartnode dist/cli.jstestvitest runtest:publishvitest run --exclude '**/e2e/chat.test.ts'test:watchvitesttypechecktsc --noEmit
Dependencies8
commander^12.1.0cross-spawn^7.0.6ink^6.8.0ink-text-input^6.0.0lowlight^3.3.0react^19.0.0string-width^7.2.0yaml^2.6.0