PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: postinstall="npm run install-python-deps"

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
1,598Niche · −30% score
Versions published
15
First published
May 2026
Publisher
frontterrain

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

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Inspect tarballAdd 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":["[email protected]"],"fail_on":"high"}'

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":"high"}'
Publisherfrontterrain
Artifact bytes9,858
Previous version2.1.0
Published2026-05-26T17:38:50.320Z
SHA-2560aa66e0fbe9b74bf8670086e9b17932f548fdf0a1b91b710fbe2da120757be38

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 2.1.1 vs 2.1.0: "npm run install-python-deps"

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

Availability ledger

available

high
Last checked
highRisk
45Score
2.1.1Version
Status history (2 events)
  1. available → available · risk high · score 45 · status available -> available, risk high -> high, score 75 -> 45
  2. new → available · risk high · score 75 · status changed

Evidence

Static findings

1 static · 1 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 2.1.1 vs 2.1.0: "npm run install-python-deps"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 2.1.1 vs 2.1.0: "npm run install-python-deps"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="npm run install-python-deps"5

Manifest

Package metadata

Scripts8
  • deploy-cloudnpm publish && npm run notify-cloud-ready
  • install-python-depspython -m pip install --only-binary :all: -q -r backend/requirements-minimal.txt 2>/dev/null || echo 'Python dependencies optional - install manually if needed'
  • notify-cloud-readyecho 'ft-sovx v2.0.3 published with Cloud Functions support!'
  • postinstallnpm run install-python-deps
  • setup-envecho 'export FT_DEPLOYMENT_MODE=cloud' >> ~/.bashrc && echo 'export GCP_PROJECT_ID=ft-sovereign-prod' >> ~/.bashrc
  • testnode bin/index.js --help
  • test:cloudFT_DEPLOYMENT_MODE=cloud ft-sovx status
  • test:localFT_DEPLOYMENT_MODE=local ft-sovx status
Dependencies3
  • axios^1.6.0
  • chalk^5.3.0
  • commander^11.0.0