data-api-client
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:pg-escape | AI (dependencies): pg-escape is a legitimate, well-known PostgreSQL escaping utility; appropriate dependency for a DB client wrapper. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 1 / 17 | |
| 2.2.0 | 1 / 17 | |
| 2.1.4 | 1 / 17 | |
| 2.1.3 | 1 / 17 | |
| 2.1.0 | 2 / 18 | |
| 2.0.0 | 2 / 13 |
v2.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.