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
- 46
- Versions published
- 11
- First published
- Mar 2026
- Publisher
- frankie_li
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":["@tofrankie/[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":["@tofrankie/[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
Scripts10
buildrun-s build:tsconfig build:cli json:lintbuild:clitsdownbuild:tsconfignode ./scripts/build-tsconfig.tsdev:clitsdown --watchjson:formatprettier ./**/*.json --write --log-level silentjson:lintrun-s json:sort json:sort json:sort json:formatjson:sorteslint --fix --config ./eslint.config.js >/dev/null 2>&1 || truepublintpublinttestvitest runtypechecktsc --noEmit
Dependencies5
@clack/prompts^1.5.0ansis^4.3.1commander^15.0.0execa^9.6.0tsconfck^3.1.6