← Home

parquet-wasm

npm Repository Homepage
3
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kylebarron

Keywords

parquetwebassemblyarrow

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): The .wasm binary is this package's stated core deliverable; expected across all versions. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Standard wasm-bindgen glue code; __wbg_get_* shims are generated by wasm-bindgen toolchain, not malicious. ai
semgrep semgrep:new-function-constructor AI (semgrep): wasm-bindgen __wbg_newnoargs_* shim; generated pattern for JS Function constructor bridging from WASM. ai

Versions (showing 3 of 3)

Version Deps Published
0.7.2 0 / 0
0.7.1 0 / 0
0.1.0 0 / 0

v0.7.2

1 finding
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 (1) npm-metadata

Package contains compiled binaries that could be backdoors: • parquet_wasm_bg.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.