Package evidence
@prisma-next/[email protected]
Suspicious Publish Context: {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"prisma"},"version_anomaly":false,"new_account":false}
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
- 38
- First published
- Jun 2026
- 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
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@prisma-next/[email protected]"],"fail_on":"review"}'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":["@prisma-next/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"prisma"},"version_anomaly":false,"new_account":false}
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 review · score 10 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"prisma"},"version_anomaly":false,"new_account":false} | 10 |
Manifest
Package metadata
Scripts9
buildtsdownbuild:contract-spaceprisma-next contract emitcleanrm -rf dist dist-tsc dist-tsc-prod coverage .tmp-outputlintbiome check . --error-on-warningslint:fixbiome check --write .lint:fix:unsafebiome check --write --unsafe .testvitest runtest:coveragevitest run --coveragetypechecktsc --project tsconfig.json --noEmit
Dependencies22
@prisma-next/adapter-postgres0.13.0-dev.28@prisma-next/contract0.13.0-dev.28@prisma-next/contract-authoring0.13.0-dev.28@prisma-next/driver-postgres0.13.0-dev.28@prisma-next/family-sql0.13.0-dev.28@prisma-next/framework-components0.13.0-dev.28@prisma-next/migration-tools0.13.0-dev.28@prisma-next/postgres0.13.0-dev.28@prisma-next/sql-builder0.13.0-dev.28@prisma-next/sql-contract0.13.0-dev.28@prisma-next/sql-contract-ts0.13.0-dev.28@prisma-next/sql-operations0.13.0-dev.28@prisma-next/sql-orm-client0.13.0-dev.28@prisma-next/sql-relational-core0.13.0-dev.28@prisma-next/sql-runtime0.13.0-dev.28@prisma-next/sql-schema-ir0.13.0-dev.28@prisma-next/target-postgres0.13.0-dev.28@prisma-next/utils0.13.0-dev.28@standard-schema/spec^1.1.0arktype^2.2.0jose^5pg8.21.0