@gradio/wasm
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/webworker/webworker.js | AI (source-diff): Bundled/minified build output (vite), not true obfuscation; consistent with pyodide worker loader. | ai | |
| source-diff | net-exec-file:dist/webworker/webworker.js | AI (source-diff): Webworker fetching/executing pyodide WASM is the package's stated function. | ai | |
| phantom-deps | phantom-dep:@types/path-browserify | AI (phantom-deps): Types package, not directly imported by convention. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.18.1 | 3 / 0 | |
| 0.14.1 | 3 / 0 | |
| 0.13.1 | 3 / 0 | |
| 0.13.0 | 2 / 1 | |
| 0.12.0 | 2 / 1 |
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.