Package evidence
[email protected]
Install-time lifecycle script: postinstall="node scripts/postinstall.js"
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
- 484
- Versions published
- 91Established · −30% score
- First published
- Sep 2025
- Publisher
- wolfejam.dev
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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
Install-time lifecycle script: postinstall="node scripts/postinstall.js"
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (4 events)
- available → available · risk review · score 3 · status available -> available, risk high -> review, score 44 -> 3
- available → available · risk high · score 44 · status available -> available, risk high -> high, score 48 -> 44
- available → available · risk high · score 48 · status available -> available, risk high -> high, score 118 -> 48
- new → available · risk high · score 118 · status changed
Related candidates
Linked campaigns and clusters
wolfejam.dev
4 members · evidence strength 84Evidence
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 | Install-time lifecycle script | package.json | postinstall="node scripts/postinstall.js" | 5 |
Manifest
Package metadata
Scripts19
buildtscdebugnode --inspect-brk=0.0.0.0:9229 -r ts-node/register src/cli.tsdevts-node src/server.tsdev:httpts-node src/cli.ts --transport http-sse --port 3001dev:stdiots-node src/cli.ts --transport stdioformatprettier --write "src/**/*.ts"format:checkprettier --check "src/**/*.ts"linteslint src/**/*.tslint:fixeslint src/**/*.ts --fixpack:mcpbnpm run build && rm -rf .mcpb-staging && mkdir .mcpb-staging && cp -r dist manifest.json package.json package-lock.json assets scripts PRIVACY.md README.md LICENSE CHANGELOG.md skill .faf .mcpb-staging/ 2>/dev/null; cd .mcpb-staging && npm install --omit=dev --ignore-scripts && rm -rf node_modules/@esbuild node_modules/esbuild node_modules/rxjs node_modules/@types node_modules/lodash node_modules/ajv-formats && npx @anthropic-ai/mcpb pack . ../claude-faf-mcp-$(node -p "require('./package.json').version").mcpb && cd .. && rm -rf .mcpb-stagingpostinstallnode scripts/postinstall.jspreparenpm run buildprepublishOnlynpm run buildsync-versionnode scripts/sync-version.jstestjesttest:mcpmcp-inspector stdio ts-node src/cli.tstest:performancejest tests/performance.test.ts --testPathIgnorePatterns=/node_modules/type-checktsc --noEmitversionnpm run sync-version && git add project.faf
Dependencies8
@modelcontextprotocol/sdk^1.27.1@upstash/redis^1.37.0cors^2.8.5esbuild^0.27.3express^4.21.0faf-cli^6.7.1faf-scoring-kernel^2.0.3yaml^2.4.1