@fedimint/fedimint-client-wasm-web
Wasm-pack output (target web) for fedimint-client-wasm
1
Versions
MIT
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
wbobeirnejustinmoonalexlwnelsirionokjodom
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): wasm-bindgen generated glue code; Reflect.get is standard JS/Wasm interop boilerplate across all versions. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): wasm-bindgen emits new Function() for Wasm string interop; stable pattern across all versions of this package. | ai |
Versions (showing 1 of 1)
| Version | Deps | Published |
|---|---|---|
| 0.1.1 | 0 / 0 |
v0.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.