Package evidence
[email protected]
Remote Dependency Spec: devDependencies.@faf/specification="github:Wolfe-Jam/faf"
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
- 10
- First published
- Jan 2026
- Publisher
- wolfejam.dev
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
Remote Dependency Spec: devDependencies.@faf/specification="github:Wolfe-Jam/faf"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (2 events)
- available → available · risk review · score 21 · status available -> available, risk high -> review, score 48 -> 21
- new → available · risk high · score 48 · status changed
Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Dependency Spec | package.json | devDependencies.@faf/specification="github:Wolfe-Jam/faf" | 8 |
| medium | New Remote Dependency Vs Previous | package.json | devDependencies.@faf/specification added in 6.8.0 vs 6.7.1: "github:Wolfe-Jam/faf" | 8 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Dependency Spec | package.json | devDependencies.@faf/specification="github:Wolfe-Jam/faf" | 8 |
| medium | New Remote Dependency Vs Previous | package.json | devDependencies.@faf/specification added in 6.8.0 vs 6.7.1: "github:Wolfe-Jam/faf" | 8 |
| low | Credential file access | package/dist/cli.js | matched ".npmrc" | 5 |
Manifest
Package metadata
Scripts10
buildbun build src/cli.ts --outdir dist --target=node --minify --sourcemap=linked --external faf-scoring-kernel --external open && bun build src/index.ts --outdir dist --target=node --minify --sourcemap=linked --external faf-scoring-kernel --external open && tsc -p tsconfig.build.jsoncheck:no-hardcode! grep -rEln '/(Users|home/runner|private/var)/' dist/ || (echo '❌ Hardcoded build-machine path leaked into dist — see grep output above. Externalize the offending dep in the build script.'; exit 1)compilebun build src/cli.ts --compile --bytecode --minify --outfile fafcompile:allbun build src/cli.ts --compile --bytecode --minify --target=bun-darwin-arm64 --outfile faf-darwin-arm64 && bun build src/cli.ts --compile --bytecode --minify --target=bun-darwin-x64 --outfile faf-darwin-x64 && bun build src/cli.ts --compile --bytecode --minify --target=bun-linux-x64 --outfile faf-linux-x64 && bun build src/cli.ts --compile --bytecode --minify --target=bun-windows-x64 --outfile faf-windows-x64.exedevbun src/cli.tsformatprettier --write 'src/**/*.ts'linteslint src/**/*.tsprepublishOnlybun run build && bun run check:no-hardcodetestbun test --timeout=120000test:watchbun test --watch --timeout=120000
Dependencies4
commander^14.0.1faf-scoring-kernel^2.0.3open^11.0.0yaml^2.4.1
Optional dependencies1
@anthropic-ai/sdk^0.91.1