Package evidence

@develop-plugins/[email protected]

Install-time lifecycle script: postinstall="node ./check-node-version.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.

Versions published: 8
First published: May 2026
Publisher: xiong_xiong

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":["@develop-plugins/[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":["@develop-plugins/[email protected]"],"fail_on":"high"}'

Publisherxiong_xiong

Artifact bytes9,133

Previous version0.6.0

Published2026-06-04T05:23:54.375Z

SHA-256c4d31f156d084877657250d2f767418db61e5862d1e32a8f78cf02020f227ec3

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.7.0 vs 0.6.0: "node ./check-node-version.js"

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

Availability ledger

available

high

42h agoLast checked

highRisk

45Score

0.7.0Version

Status history (3 events)

scan_error → available42h ago · risk high · score 45 · status scan_error -> available, risk none -> high, score none -> 45
new → scan_error42h ago · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@develop-plugins/vite-plugin-git-tag/-/vite-plugin-git-tag-0.7.0.tgz)
new → scan_error42h ago · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@develop-plugins/vite-plugin-git-tag/-/vite-plugin-git-tag-0.7.0.tgz)

Evidence

Static findings

1 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 0.7.0 vs 0.6.0: "node ./check-node-version.js"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.7.0 vs 0.6.0: "node ./check-node-version.js"	40
low	Install-time lifecycle script	package.json	postinstall="node ./check-node-version.js"	5

Manifest

Package metadata

Scripts3

buildvite build
postinstallnode ./check-node-version.js
runnode ./index.js

Dependencies2

@clack/prompts^1.4.0
picocolors^1.1.1