← Home

@supabase/pg-parser

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

etienne_supakiwicoppleange1icoawaliasgregnrphamhieu1998inianstdimziinc_supabasemandarinichase.cresgyceeteelamkevin-supabasemattrossman

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): WASM build artifacts from documented libpg_query build pipeline, not opaque binaries. ai
maintainer-change maintainer-added AI (maintainer-change): Supabase team roster change, consistent with org-owned package. ai
maintainer-change maintainer-removed AI (maintainer-change): Supabase team roster change, consistent with org-owned package. ai

Versions (showing 8 of 8)

Version Deps Published
0.1.7 0 / 16
0.1.6 0 / 16
0.1.5 0 / 16
0.1.4 0 / 16
0.1.3 1 / 15
0.1.2 1 / 15
0.1.1 1 / 15
0.1.0 1 / 15

v0.1.5

3 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/17/pg-parser.min.wasm • wasm/15/pg-parser.wasm • wasm/16/pg-parser.wasm • wasm/17/pg-parser.wasm

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gregnr.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.4

3 findings
HIGH Bundled binary files (4) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/17/pg-parser.min.wasm • wasm/15/pg-parser.wasm • wasm/16/pg-parser.wasm • wasm/17/pg-parser.wasm

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: gregnr.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.0

2 findings
HIGH Bundled binary files (3) npm-metadata

Package contains compiled binaries that could be backdoors: • wasm/15/pg-parser.wasm • wasm/16/pg-parser.wasm • wasm/17/pg-parser.wasm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.