brotli
A port of the Brotli compression algorithm as used in WOFF2
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | net-exec-file:build/encode.js | AI (source-diff): Emscripten runtime boilerplate; XHR loads .mem files in browser, eval is module bootstrap. | ai | |
| source-diff | net-exec-file:build/all.js | AI (source-diff): XMLHttpRequest + eval are Emscripten runtime boilerplate for .mem file loading and module init, not malware. | ai | |
| source-diff | net-exec-file:build/decode.js | AI (source-diff): Emscripten runtime boilerplate; XHR loads .mem files in browser, eval is module bootstrap. | ai | |
| source-diff | obfuscated-file:build/all.js | AI (source-diff): Emscripten-compiled C brotli library output; standard minified wasm/asm.js build artifact, not obfuscation. | ai | |
| source-diff | obfuscated-file:build/decode.js | AI (source-diff): Emscripten-compiled C brotli decoder output; standard minified build artifact. | ai | |
| source-diff | obfuscated-file:build/encode.js | AI (source-diff): Emscripten-compiled C brotli encoder output; standard minified build artifact. | ai | |
| source-diff | obfuscated-file:dec/dictionary.bin.js | AI (source-diff): Base64-encoded Brotli dictionary binary data, not obfuscated code. Required for the decompression algorithm to function. | ai | |
| source-diff | obfuscated-file:build/mem.js | AI (source-diff): Base64-encoded Brotli memory initialization data, not obfuscated code. Standard for pure-JS compression libraries shipping binary dictionaries. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.3.3 | 1 / 1 | |
| 1.3.2 | 1 / 1 | |
| 1.3.1 | 1 / 1 | |
| 1.3.0 | 1 / 1 | |
| 1.2.0 | 3 / 1 | |
| 1.1.0 | 3 / 1 | |
| 1.0.2 | 0 / 0 | |
| 1.0.1 | 0 / 0 | |
| 1.0.0 | 0 / 0 |
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
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 source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
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.
v1.1.0
7 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.
Newly 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.
Newly 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.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.