PkgRadar

Package evidence

@agentfare/[email protected]

Install Lifecycle Suppresses Failure: preinstall="node dist/preinstall-stop-proxy.js || exit 0"

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.

Versions published
29
First published
May 2026
Publisher
whatcanyouoffer

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.

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":["@agentfare/[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":["@agentfare/[email protected]"],"fail_on":"high"}'
Artifact bytes16,132
Previous version0.1.26
Published2026-06-04T10:22:20.864Z
SHA-2565d93924f05e6972aa13410eb6bdcd26e1133f856ecfa7f1abd126110277569de

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.27 vs 0.1.26: "node dist/postinstall-start-proxy.js || exit 0"

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

Availability ledger

available

high
Last checked
highRisk
90Score
0.1.27Version
Status history (1 event)
  1. newavailable · risk high · score 90 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.27 vs 0.1.26: "node dist/postinstall-start-proxy.js || exit 0"40
highInstall Lifecycle Suppresses Failurepackage.jsonpreinstall="node dist/preinstall-stop-proxy.js || exit 0"20
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="node dist/postinstall-start-proxy.js || exit 0"20
Show all 5 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.1.27 vs 0.1.26: "node dist/postinstall-start-proxy.js || exit 0"40
highInstall Lifecycle Suppresses Failurepackage.jsonpreinstall="node dist/preinstall-stop-proxy.js || exit 0"20
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="node dist/postinstall-start-proxy.js || exit 0"20
lowInstall-time lifecycle scriptpackage.jsonpreinstall="node dist/preinstall-stop-proxy.js || exit 0"5
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node dist/postinstall-start-proxy.js || exit 0"5

Manifest

Package metadata

Scripts5
  • buildtsc
  • postinstallnode dist/postinstall-start-proxy.js || exit 0
  • preinstallnode dist/preinstall-stop-proxy.js || exit 0
  • testvitest run
  • test:watchvitest
Dependencies7
  • @agentfare/core0.1.10
  • @agentfare/hook0.1.12
  • @agentfare/loader0.1.12
  • @agentfare/models0.1.10
  • @agentfare/proxy0.1.13
  • @agentfare/setup0.1.13
  • commander^13.0.0