@prisma-next/extension-paradedb
ParadeDB full-text search extension pack 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 | slsa-provenance | AI (provenance): Package consistently published via CI with SLSA attestation; stable signal for this package. | ai | |
| phantom-deps | phantom-dep:@prisma-next/sql-operations | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used indirectly. Stable false positive. | ai | |
| phantom-deps | phantom-dep:@prisma-next/contract-authoring | AI (phantom-deps): Same-org monorepo dep; likely re-exported or used indirectly. Stable false positive. | ai | |
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI/CD publishing with SLSA attestation; consistent with official prisma org automation. | ai | |
| phantom-deps | phantom-dep:@prisma-next/contract | AI (phantom-deps): Same org scope (@prisma-next); likely re-exported or used indirectly via contract-authoring peer. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.12.0 | 10 / 11 | |
| 0.11.0 | 10 / 11 | |
| 0.10.0 | 10 / 11 | |
| 0.9.0 | 10 / 11 | |
| 0.8.0 | 10 / 11 | |
| 0.6.1 | 10 / 11 | |
| 0.5.1 | 10 / 11 | |
| 0.5.0 | 9 / 9 | |
| 0.4.4 | 2 / 5 | |
| 0.4.3 | 2 / 5 | |
| 0.4.2 | 2 / 5 | |
| 0.4.1 | 2 / 5 | |
| 0.3.0 | 2 / 5 | |
| 0.0.1 | 2 / 5 |
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.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
2 findingsThis version was published by a different npm account than previous versions on 2026-04-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-16. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.