@prisma-next/family-sql
SQL family descriptor 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/cli | AI (phantom-deps): Same-org monorepo sibling; declared as dep but re-exported transitively — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/emitter | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/operations | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-contract-ts | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in this monorepo package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/runtime-executor | AI (phantom-deps): Same-org sibling dep; likely re-exported rather than directly imported in this monorepo package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 14 / 10 | |
| 0.11.0 | 14 / 10 | |
| 0.10.0 | 14 / 10 | |
| 0.9.0 | 14 / 10 | |
| 0.8.0 | 14 / 10 | |
| 0.7.0 | 14 / 10 | |
| 0.6.1 | 14 / 10 | |
| 0.5.1 | 14 / 10 | |
| 0.5.0 | 14 / 10 | |
| 0.4.4 | 14 / 10 | |
| 0.4.3 | 14 / 10 | |
| 0.4.2 | 15 / 9 | |
| 0.4.1 | 15 / 9 | |
| 0.3.0 | 14 / 9 | |
| 0.2.0 | 15 / 7 | |
| 0.0.1 | 11 / 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.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.