@open-keystone/adapter-prisma
KeystoneJS Prisma Database Adapter
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:env-spread | AI (semgrep): Spreads process.env to pass DATABASE_URL to prisma CLI — standard adapter pattern, not exfiltration. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execSync used only to invoke prisma CLI binary; no user-controlled input in the command. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads generated Prisma client from a known, adapter-controlled path; not arbitrary module loading. | ai | |
| phantom-deps | phantom-dep:prisma | AI (phantom-deps): prisma is a CLI tool invoked via execSync, not imported directly; phantom-dep is a false positive here. | ai | |
| phantom-deps | phantom-dep:@prisma/client | AI (phantom-deps): Loaded dynamically via require(this.clientPath) after generation; phantom-dep is a false positive. | ai | |
| phantom-deps | phantom-dep:@prisma/internals | AI (phantom-deps): Used in config/schema generation logic; phantom-dep heuristic misses indirect usage patterns. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 4.0.41 | 7 / 0 | |
| 4.0.40 | 7 / 0 | |
| 4.0.39 | 7 / 0 | |
| 4.0.38 | 7 / 0 | |
| 4.0.37 | 7 / 0 | |
| 4.0.36 | 7 / 0 | |
| 4.0.35 | 7 / 0 | |
| 4.0.34 | 7 / 0 | |
| 4.0.33 | 7 / 0 | |
| 4.0.32 | 7 / 0 | |
| 4.0.31 | 7 / 0 | |
| 4.0.30 | 7 / 0 | |
| 4.0.17 | 7 / 0 | |
| 4.0.16 | 7 / 0 | |
| 4.0.15 | 7 / 0 | |
| 4.0.14 | 7 / 0 | |
| 4.0.13 | 7 / 0 | |
| 4.0.12 | 7 / 0 | |
| 4.0.11 | 7 / 0 | |
| 4.0.10 | 7 / 0 | |
| 4.0.9 | 7 / 0 | |
| 4.0.8 | 7 / 0 | |
| 4.0.7 | 7 / 0 | |
| 4.0.6 | 7 / 0 | |
| 4.0.5 | 7 / 0 | |
| 4.0.4 | 7 / 0 | |
| 4.0.3 | 7 / 0 | |
| 4.0.2 | 7 / 0 | |
| 4.0.1 | 7 / 0 | |
| 4.0.0 | 7 / 0 |
v4.0.41
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.40
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.39
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.38
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.37
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.36
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.35
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.34
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.33
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.