← Home

@lit-protocol/wasm

6
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

glitch003adarsh-kumar28websaamhwrdtmfamuramaximushaximusspacesailorawisniew

Keywords

library

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:base64-decode AI (semgrep): Decoding a bundled WASM binary via pako.inflate — standard wasm-pack output pattern, not a payload. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get in wasm-bindgen JS glue code; standard generated pattern, not obfuscation. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function in wasm-bindgen glue for JS eval interop; standard generated code from wasm-pack. ai
phantom-deps phantom-dep:ethers AI (phantom-deps): ethers is a declared dependency used in config/type context; stable false positive for this package. ai

Versions (showing 6 of 6)

Version Deps Published
8.1.1 4 / 0
8.1.0 4 / 0
8.0.2 4 / 0
8.0.1 4 / 0
8.0.0 2 / 0
7.4.0 3 / 0

v8.1.1

1 finding
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.

v8.1.0

1 finding
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.

v8.0.2

1 finding
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.

v8.0.1

1 finding
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.

v8.0.0

1 finding
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.

v7.4.0

1 finding
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.