@prisma-next/driver-postgres
PostgreSQL driver for Prisma Next.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Early-stage monorepo package; no provenance is common and not a disqualifier here. | ai | |
| phantom-deps | phantom-dep:arktype | AI (phantom-deps): arktype is directly imported in source; heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@prisma-next/contract | AI (phantom-deps): Internal monorepo dependency; used via re-exports from framework-components. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-contract | AI (phantom-deps): Internal monorepo dependency; used via re-exports from sql-relational-core. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-operations | AI (phantom-deps): Internal monorepo dependency; used via re-exports from sql-relational-core. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 11 / 9 | |
| 0.11.0 | 11 / 9 | |
| 0.10.0 | 11 / 9 | |
| 0.9.0 | 11 / 9 | |
| 0.8.0 | 11 / 9 | |
| 0.7.0 | 11 / 9 | |
| 0.6.1 | 11 / 9 | |
| 0.5.1 | 11 / 9 | |
| 0.5.0 | 11 / 9 | |
| 0.4.4 | 11 / 9 | |
| 0.4.3 | 11 / 9 | |
| 0.4.2 | 11 / 9 | |
| 0.4.1 | 11 / 9 | |
| 0.3.0 | 11 / 9 | |
| 0.2.0 | 11 / 8 | |
| 0.0.1 | 7 / 7 |
v0.12.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.