@prisma-next/adapter-postgres
PostgreSQL adapter 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@prisma-next/sql-schema-ir | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/cli | AI (phantom-deps): Same-org monorepo dep; declared for peer/tooling use, not a direct import. | ai | |
| phantom-deps | phantom-dep:@prisma-next/contract | AI (phantom-deps): Same-org monorepo dep; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:arktype | AI (phantom-deps): Used in config/type definitions; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/contract-authoring | AI (phantom-deps): Same-org package; stable FP for this monorepo. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-operations | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-contract-ts | AI (phantom-deps): Same-org monorepo sibling; declared as peer/type dep, not directly imported. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-contract-psl | AI (phantom-deps): Same-org monorepo sibling; declared as peer/type dep, not directly imported. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 16 / 10 | |
| 0.11.0 | 16 / 10 | |
| 0.10.0 | 15 / 11 | |
| 0.9.0 | 15 / 11 | |
| 0.8.0 | 15 / 11 | |
| 0.7.0 | 15 / 11 | |
| 0.6.1 | 15 / 11 | |
| 0.5.1 | 15 / 11 | |
| 0.5.0 | 15 / 12 | |
| 0.4.4 | 15 / 11 | |
| 0.4.3 | 15 / 11 | |
| 0.4.2 | 16 / 11 | |
| 0.4.1 | 15 / 6 | |
| 0.3.0 | 15 / 6 | |
| 0.2.0 | 12 / 5 | |
| 0.0.1 | 9 / 4 |
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.2
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.