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 updateStatic 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"}'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
Status history (1 event)
- new → available · risk high · score 45 · status changed
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.3.36 vs 0.3.32: "bun run generate" | 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.3.36 vs 0.3.32: "bun run generate" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="bun run generate" | 5 |
Manifest
Package metadata
Scripts9
buildNODE_ENV=production next build --turbopackcheckbun run lint && bun run typecheckdb:pushprisma db pushdevnext dev --turbopackgeneraterm -rf src/server/generated && zenstack generate --output ./src/server/generated/.zenstack --no-compile --schema ./prisma/schema.zmodellinteslint .postinstallbun run generatestartnext starttypechecktsc --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.1antd^6.3.1next^16.2.4next-auth^4.24.11react^19.1.0react-dom^19.1.0server-only^0.0.1superjson^2.2.1zenstack2.22.1zod^3.23.3zod-validation-error^3.4.0