Package evidence

@jpmvtv/[email protected]

New Account With Lifecycle Hook: package first published 12 day(s) ago, 8 total version(s), has lifecycle hook

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,153Niche · −30% score
Versions published: 8
First published: May 2026
Publisher: jpmvtv

Effective trust discount applied: −30% (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 tarball Add 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":["@jpmvtv/[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":["@jpmvtv/[email protected]"],"fail_on":"high"}'

Publisherjpmvtv

Artifact bytes26,854

Previous version1.1.2

Published2026-05-31T00:54:13.649Z

SHA-2565d013d319d42f5c7416d10f2afb86b85f5e6eb724db74ad385c7948087246e19

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.2.0 vs 1.1.2: "echo 'Run npm run setup:a2u-payments to configure @jpmvtv/a2u-payments for your database schema'"

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

Availability ledger

available

high

3d agoLast checked

highRisk

45Score

1.2.0Version

Status history (1 event)

new → available13d ago · risk high · score 45 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.2.0 vs 1.1.2: "echo 'Run npm run setup:a2u-payments to configure @jpmvtv/a2u-payments for your database schema'"	40
medium	New Account With Lifecycle Hook	package.json	package first published 12 day(s) ago, 8 total version(s), has lifecycle hook	10

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 1.2.0 vs 1.1.2: "echo 'Run npm run setup:a2u-payments to configure @jpmvtv/a2u-payments for your database schema'"	40
medium	New Account With Lifecycle Hook	package.json	package first published 12 day(s) ago, 8 total version(s), has lifecycle hook	10
low	Install-time lifecycle script	package.json	postinstall="echo 'Run npm run setup:a2u-payments to configure @jpmvtv/a2u-payments for your database schema'"	5

Manifest

Package metadata

Scripts7

buildtsc
devtsc --watch
postinstallecho 'Run npm run setup:a2u-payments to configure @jpmvtv/a2u-payments for your database schema'
prepublishOnlynpm run build
setup:a2u-paymentsnode scripts/setup-wizard.js
testjest
test:watchjest --watch

Dependencies4

inquirer^8.2.0
pg^8.11.3
pi-backend^0.1.3
react^18.0.0 || ^19.0.0