PkgRadar

Package evidence

@hpp-io/[email protected]

Install Lifecycle Suppresses Failure: postinstall="patch-package || true"

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
7
Versions published
2
First published
May 2026
Publisher
hpp-io

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":["@hpp-io/[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":["@hpp-io/[email protected]"],"fail_on":"high"}'
Publisherhpp-io
Artifact bytes91,289
Previous version0.0.1
Published2026-06-09T07:59:56.612Z
SHA-256183e51f4faa69d1e542b2dfb73cdd7d73f88a6d607631a83b1435f45dbaadec0

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.0.2 vs 0.0.1: "patch-package || true"

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

Availability ledger

available

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

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.0.2 vs 0.0.1: "patch-package || true"40
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="patch-package || true"20
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 33 day(s) ago, 2 total version(s), has lifecycle hook10
Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.0.2 vs 0.0.1: "patch-package || true"40
highInstall Lifecycle Suppresses Failurepackage.jsonpostinstall="patch-package || true"20
mediumNew Account With Lifecycle Hookpackage.jsonpackage first published 33 day(s) ago, 2 total version(s), has lifecycle hook10
lowInstall-time lifecycle scriptpackage.jsonpostinstall="patch-package || true"5

Manifest

Package metadata

Scripts5
  • buildtsc
  • devtsx src/index.ts
  • postinstallpatch-package || true
  • prepublishOnlynpm run typecheck && npm run build
  • typechecktsc --noEmit
Dependencies7
  • @modelcontextprotocol/sdk^1.0.0
  • @napi-rs/keyring^1.3.0
  • @x402/core^2.13.0
  • @x402/evm^2.13.0
  • @x402/mcp^2.13.0
  • viem^2.21.54
  • zod^3.23.8