Package evidence

@followthecode/[email protected]

Install-time lifecycle script: postinstall="node scripts/post-install.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: 670
Versions published: 79Established · −30% score
First published: Jul 2025
Publisher: jheisong

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 promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarball Add to CI gate

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":["@followthecode/[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":["@followthecode/[email protected]"],"fail_on":"review"}'

Publisherjheisong

Artifact bytes238,354,640

Previous version3.1.0

Published2026-04-10T14:07:51.504Z

SHA-256

Why flagged

What the scanner saw

Install-time lifecycle script: postinstall="node scripts/post-install.js"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review

40h agoLast checked

reviewRisk

3Score

3.1.1Version

Status history (2 events)

scan_error → available40h ago · risk review · score 3 · status scan_error -> available, risk none -> review, score none -> 3
new → scan_error9d ago · risk none · score — · refusing to fetch https://registry.npmjs.org/@followthecode/cli/-/cli-3.1.1.tgz: content-length 102858636 exceeds 50000000

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	Install-time lifecycle script	package.json	postinstall="node scripts/post-install.js"	5
low	Oversized Unscanned	manifest	tarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only	0

Manifest

Package metadata

Scripts22

buildnpm run sync-version && npm run build:all && npm run setup
build:allnpm run build:win && npm run build:mac && npm run build:linux
build:linuxdotnet publish ftc.collect.cli.csproj -c Release -r linux-x64 -o ./bin/linux-x64
build:macdotnet publish ftc.collect.cli.csproj -c Release -r osx-x64 -o ./bin/osx-x64
build:windotnet publish ftc.collect.cli.csproj -c Release -r win-x64 -o ./bin/win-x64
cleandotnet clean
copy-confignode scripts/copy-config.js
copy-wrappernode scripts/copy-wrapper
postinstallnode scripts/post-install.js
promotenode scripts/promote.js
publishnode scripts/publish.js
publish:majornode scripts/publish.js --major
publish:minornode scripts/publish.js --minor
publish:patchnode scripts/publish.js --patch
set-permissionsnode scripts/set-permissions.js
setupnpm run copy-config && npm run copy-wrapper && npm run set-permissions
sync-versionnode scripts/sync-version.js
testdotnet test
test:installnpm run test:install:win
test:install:linuxbash scripts/test-installation.sh
test:install:winpowershell -ExecutionPolicy Bypass -File scripts/test-simple.ps1
test:install:wslwsl bash scripts/test-installation.sh

Dependencies1

node-fetch^3.3.0