PkgRadar

Package evidence

@strvmarv/[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
1,301Niche · −30% score
Versions published
95
First published
Apr 2026
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (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.

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":["@strvmarv/[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":["@strvmarv/[email protected]"],"fail_on":"review"}'
Artifact bytes370,191,113
Previous version3.3.0
Published2026-06-15T22:39:58.359Z
SHA-256

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

review
Last checked
reviewRisk
1Score
3.3.1Version
Status history (2 events)
  1. scan_erroravailable · risk review · score 1 · status scan_error -> available, risk none -> review, score none -> 1
  2. newscan_error · risk none · score · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@strvmarv/total-recall/-/total-recall-3.3.1.tgz)

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)
SeverityKindPathDetailPoints
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node scripts/postinstall.js"5
lowOversized Unscannedmanifesttarball exceeds the 50MB fetch cap; scanned registry metadata (install scripts + dependencies) only0

Manifest

Package metadata

Scripts4
  • postinstallnode scripts/postinstall.js
  • preparegit config core.hooksPath git-hooks || true
  • prepublishOnlynode scripts/verify-binaries.js
  • test:shimnode --test bin/shim/ scripts/fetch-binary.test.js