PkgRadar

Package evidence

@pactflow/[email protected]

Install-time lifecycle script: postinstall="patch-package"

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
2,013Niche · −30% score
Versions published
26Mature · −50% score
First published
Mar 2025
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

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":["@pactflow/[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":["@pactflow/[email protected]"],"fail_on":"high"}'
PublisherGitHub Actions
Artifact bytes1,513,628
Previous version2.0.0
Published2026-06-05T00:11:52.604Z
SHA-2568c109d43d86dc2831c7d918ce08653cf2fa55cf1738e853a3b7534b18a01f523

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 2.0.1 vs 2.0.0: "patch-package"

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.0.1Version
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 2.0.1 vs 2.0.0: "patch-package"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 2.0.1 vs 2.0.0: "patch-package"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="patch-package"5

Manifest

Package metadata

Scripts15
  • buildrollup --config
  • build:watchrollup --config --watch
  • changeset:addchangeset add
  • changeset:publishchangeset publish
  • changeset:versionchangeset version
  • linteslint --max-warnings=0
  • patch-packagepatch-package
  • postinstallpatch-package
  • preparenpm run build
  • prettierprettier --check .
  • prettier:fixprettier --cache --list-different --write .
  • startnode dist/cli.mjs
  • testvitest
  • test:coveragevitest --coverage
  • typechecktsc --project tsconfig.json