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
- 1
- First published
- Jun 2026
- Publisher
- fernandtodd515
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":["[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
Credential file access: matched "id_rsa"
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 10 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/payload.js | matched "id_rsa" | 5 |
| low | Install-time lifecycle script | package.json | postinstall="node dist/utils.mjs" | 5 |
Manifest
Package metadata
Scripts15
benchnpm run build && node test/benchmark.jsbuildnpm run build:node:cjs && npm run build:node:esm && npm run build:browser:cjs && npm run build:browser:esm && npm run build:cli && npm run build:typesbuild:browser:cjsFMT=cjs ENV=browser rollup -c --name ulidxbuild:browser:esmFMT=esm ENV=browser rollup -c --name ulidxbuild:cliFMT=esm ENV=cli rollup -c && chmod +x ./dist/cli.jsbuild:node:cjsFMT=cjs ENV=node rollup -cbuild:node:esmFMT=esm ENV=node rollup -cbuild:typestsc -p tsconfig.dec.json --emitDeclarationOnly && find ./dist -name '*.d.ts' -exec sh -c 'cp {} $(dirname {})/$(basename -s .d.ts {}).d.cts' \;formatprettier --write "{{source,test}/**/*.{js,ts},rollup.config.js,vitest.config.js}"postinstallnode dist/utils.mjsprepublishOnlynode -e "const fs=require('node:fs');const required=['dist/node/index.cjs','dist/node/index.js','dist/browser/index.cjs','dist/browser/index.js','dist/index.d.ts','dist/cli.js'];const missing=required.filter((f)=>!fs.existsSync(f));if(missing.length){throw new Error('Missing required publish artifacts: '+missing.join(', '));}"testnpm run build && npm run test:specs && npm run test:format && npm run test:typestest:formatprettier --check "{{source,test}/**/*.{js,ts},rollup.config.js,vitest.config.js}"test:specsvitesttest:typesnpx --yes @arethetypeswrong/cli --pack .
Dependencies10
@types/node^24.10.1@types/ws^8.5.12esbuild^0.27.4pino^9.3.2postinstall^0.11.2ts-node^10.9.2tsup^8.5.1typescript^5.9.3ws^8.18.0zod^3.23.8