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
- 12
- Versions published
- 8
- First published
- Mar 2026
- Publisher
- frankie_li
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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
Credential file access: matched ".npmrc"
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 review · score 5 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/cli.mjs | matched ".npmrc" | 5 |
Manifest
Package metadata
Scripts12
action:buildtsdown --filter actionaction:releasetsx scripts/release.tslintrun-s lint:eslint lint:prettier typechecklint:eslinteslint . --cache --fixlint:prettierprettier . --cache --write --log-level silentnpm:buildtsdown --filter npmnpm:clinode bin/cli.jsnpm:devtsdown --filter npm --watchpublintpublinttestvitest runtest:coveragevitest run --coveragetypechecktsc --noEmit
Dependencies8
@actions/core^3.0.0@actions/github^9.1.0@inquirer/prompts^8.4.1commander^14.0.3execa^9.6.1fast-glob^3.3.3semver^7.7.2yaml^2.8.3