libpg-query
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): WASM is this package's core parser artifact; expected every version. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 18.1.2 | 1 / 0 | |
| 18.1.1 | 1 / 0 | |
| 18.1.0 | 1 / 0 | |
| 18.0.2 | 1 / 0 | |
| 18.0.1 | 1 / 0 | |
| 18.0.0 | 1 / 0 | |
| 17.7.4 | 1 / 0 | |
| 17.7.3 | 1 / 0 | |
| 17.7.2 | 1 / 0 | |
| 17.7.1 | 1 / 0 | |
| 17.6.0 | 1 / 0 | |
| 17.5.6 | 1 / 0 | |
| 17.5.5 | 1 / 0 | |
| 17.5.3 | 1 / 0 | |
| 17.5.2 | 1 / 0 | |
| 17.5.1 | 1 / 0 | |
| 17.5.0 | 1 / 0 | |
| 17.4.1 | 1 / 0 | |
| 17.4.0 | 1 / 0 | |
| 16.7.3 | 1 / 0 | |
| 16.7.2 | 1 / 0 | |
| 16.7.1 | 1 / 0 | |
| 16.5.6 | 1 / 0 | |
| 15.6.3 | 1 / 0 | |
| 15.6.2 | 1 / 0 | |
| 15.6.1 | 1 / 0 | |
| 15.4.9 | 1 / 0 | |
| 14.4.3 | 1 / 0 | |
| 14.4.2 | 1 / 0 | |
| 14.4.1 | 1 / 0 | |
| 14.2.6 | 1 / 0 | |
| 13.7.3 | 1 / 0 | |
| 13.7.2 | 1 / 0 | |
| 13.7.1 | 1 / 0 | |
| 13.5.8 | 1 / 0 |
v18.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v18.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v17.7.4
2 findingsPackage contains compiled binaries that could be backdoors: • wasm/libpg-query.wasm
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.