@prisma/sdk
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
jolg42janpiopirix-ghprismabot
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:replace-string | AI (dependencies): Small, well-known string utility; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@timsuchanek/copy | AI (dependencies): Internal Prisma utility authored by the package author; stable for this package. | ai | |
| dependencies | unvetted-dep:checkpoint-client | AI (dependencies): Prisma telemetry client; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:@prisma/engine-core | AI (dependencies): First-party Prisma package; stable dependency for this package. | ai | |
| dependencies | unvetted-dep:new-github-issue-url | AI (dependencies): Small, well-known utility by sindresorhus; stable for this package. | ai |
v4.0.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.15.2
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.