PkgRadar

Package evidence

@wzyjs/[email protected]

Install-time lifecycle script: postinstall="bun run generate"

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
16
Versions published
106Mature · −50% score
First published
Dec 2022
Publisher
wzy1993

Effective trust discount applied: 50% (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.

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":["@wzyjs/[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":["@wzyjs/[email protected]"],"fail_on":"high"}'
Publisherwzy1993
Artifact bytes39,474
Previous version0.3.32
Published2026-06-12T05:46:52.776Z
SHA-256d218538c8d048d918c4d727206cde90e9c6ec0ba7991db46c9611277ac03a4e6

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.3.36 vs 0.3.32: "bun run generate"

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

Availability ledger

available

high
Last checked
highRisk
45Score
0.3.36Version
Status history (1 event)
  1. newavailable · 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 0.3.36 vs 0.3.32: "bun run generate"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.3.36 vs 0.3.32: "bun run generate"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="bun run generate"5

Manifest

Package metadata

Scripts9
  • buildNODE_ENV=production next build --turbopack
  • checkbun run lint && bun run typecheck
  • db:pushprisma db push
  • devnext dev --turbopack
  • generaterm -rf src/server/generated && zenstack generate --output ./src/server/generated/.zenstack --no-compile --schema ./prisma/schema.zmodel
  • linteslint .
  • postinstallbun run generate
  • startnext start
  • typechecktsc --noEmit
Dependencies24
  • @prisma/client^6.14.0
  • @t3-oss/env-nextjs^0.10.1
  • @tanstack/react-query^5.50.0
  • @trpc/client^11.7.0
  • @trpc/next^11.7.0
  • @trpc/react-query^11.7.0
  • @trpc/server^11.7.0
  • @wzyjs/hooksworkspace:*
  • @wzyjs/middle-sdkworkspace:*
  • @wzyjs/nextworkspace:*
  • @wzyjs/uisworkspace:*
  • @wzyjs/utilsworkspace:*
  • @zenstackhq/runtime2.22.1
  • @zenstackhq/trpc2.22.1
  • antd^6.3.1
  • next^16.2.4
  • next-auth^4.24.11
  • react^19.1.0
  • react-dom^19.1.0
  • server-only^0.0.1
  • superjson^2.2.1
  • zenstack2.22.1
  • zod^3.23.3
  • zod-validation-error^3.4.0