PkgRadar

Package evidence

@danielsimonjr/[email protected]

Install-time lifecycle script: postinstall="node install-fzf.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
28
Versions published
4
First published
Nov 2025
Publisher
danielsimonjr

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":["@danielsimonjr/[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":["@danielsimonjr/[email protected]"],"fail_on":"high"}'
Publisherdanielsimonjr
Artifact bytes1,806,157
Previous version1.0.0
Published2025-11-12T01:33:12.757Z
SHA-256358d68654623f69f337dd4da36b3c7a7d3ce5e8acbc8b466c8ae71d5087541e7

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.1.0 vs 1.0.0: "node install-fzf.js"

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

Availability ledger

available

high
Last checked
highRisk
45Score
1.1.0Version
Status history (1 event)
  1. new → available · risk high · score 45 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.0 vs 1.0.0: "node install-fzf.js"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.0 vs 1.0.0: "node install-fzf.js"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node install-fzf.js"5

Manifest

Package metadata

Scripts2
  • postinstallnode install-fzf.js
  • testecho "Error: no test specified" && exit 1
Dependencies1
  • @modelcontextprotocol/sdk^1.20.2