@tybys/wasm-util
WASI polyfill for browser and some wasm util
19
Versions
MIT
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 — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
toyobayashi
Keywords
wasmwebassemblywasipolyfill
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/cjs/memfs.js | AI (source-diff): This is a bundled/minified copy of the memfs library, consistent with the package's WASI polyfill purpose and its memfs-browser devDependency. Not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:lib/mjs/memfs.mjs | AI (source-diff): ESM variant of the same bundled memfs library. Same rationale as the CJS version — legitimate minified bundle output. | ai | |
| source-diff | net-exec-file:lib/cjs/memfs.js | AI (source-diff): False positive: network and eval patterns come from Node.js polyfills within the bundled memfs library, not from dropper/loader logic. Consistent with browser-targeted WASI polyfill. | ai | |
| source-diff | net-exec-file:lib/mjs/memfs.mjs | AI (source-diff): Same false positive rationale as the CJS variant — bundled Node.js polyfill patterns, not malware. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 0.10.3 | 1 / 15 | |
| 0.10.2 | 1 / 15 | |
| 0.10.1 | 1 / 15 | |
| 0.10.0 | 1 / 15 | |
| 0.9.0 | 1 / 15 | |
| 0.8.3 | 1 / 15 | |
| 0.8.2 | 1 / 15 | |
| 0.8.1 | 1 / 15 | |
| 0.8.0 | 1 / 15 | |
| 0.7.0 | 1 / 15 | |
| 0.6.0 | 1 / 15 | |
| 0.5.3 | 1 / 14 | |
| 0.5.2 | 0 / 14 | |
| 0.5.1 | 0 / 14 | |
| 0.5.0 | 0 / 14 | |
| 0.4.0 | 0 / 14 | |
| 0.3.0 | 1 / 14 | |
| 0.2.0 | 1 / 14 | |
| 0.1.0 | 1 / 14 |
v0.10.3
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.