fflate
High performance (de)compression in an 8kB package
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Benign publish-env metadata change on a trusted high-usage package; no malicious behavior. | ai | |
| source-diff | obfuscated-file:umd/index.js | AI (source-diff): Standard UMD minified bundle for browser distribution; matches source in esm/index.js. | ai | |
| source-diff | net-exec-file:esm/index.js | AI (source-diff): ESM module with worker_threads support for non-blocking compression; no actual network calls or malicious execution. | ai | |
| source-diff | net-exec-file:esm/index.mjs | AI (source-diff): Node.js worker_threads usage for non-blocking compression. new Worker with eval:true is the standard pattern for inline worker code. | ai | |
| source-diff | net-exec-file:esm/browser.js | AI (source-diff): fflate uses URL.createObjectURL + Worker for non-blocking compression; not a network call. Standard Web Worker pattern for this library. | ai | |
| semgrep | semgrep:eval-usage | AI (semgrep): Triggered by the standard UMD bundle wrapper pattern in the minified output, not actual eval() on untrusted input. Stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): Used in fflate's inline Web Worker implementation to deserialize worker functions across the worker boundary — a documented, intentional pattern for this library, not a supply-chain risk. | ai |
Versions (showing 51 of 58)
| Version | Deps | Published |
|---|---|---|
| 0.8.3 | 0 / 20 | |
| 0.8.2 | 0 / 20 | |
| 0.8.1 | 0 / 21 | |
| 0.8.0 | 0 / 20 | |
| 0.7.5 | 0 / 20 | |
| 0.7.4 | 0 / 20 | |
| 0.7.3 | 0 / 20 | |
| 0.7.2 | 0 / 20 | |
| 0.7.1 | 0 / 20 | |
| 0.7.0 | 0 / 20 | |
| 0.6.11 | 0 / 20 | |
| 0.6.10 | 0 / 20 | |
| 0.6.9 | 0 / 20 | |
| 0.6.8 | 0 / 20 | |
| 0.6.7 | 0 / 20 | |
| 0.6.6 | 0 / 20 | |
| 0.6.5 | 0 / 20 | |
| 0.6.4 | 0 / 20 | |
| 0.6.3 | 0 / 20 | |
| 0.6.2 | 0 / 20 | |
| 0.6.1 | 0 / 20 | |
| 0.6.0 | 0 / 20 | |
| 0.5.4 | 0 / 20 | |
| 0.5.3 | 0 / 20 | |
| 0.5.2 | 0 / 20 | |
| 0.5.1 | 1 / 20 | |
| 0.5.0 | 1 / 21 | |
| 0.4.9 | 0 / 21 | |
| 0.4.8 | 0 / 21 | |
| 0.4.7 | 0 / 21 | |
| 0.4.6 | 0 / 21 | |
| 0.4.5 | 0 / 21 | |
| 0.4.4 | 0 / 21 | |
| 0.4.3 | 0 / 21 | |
| 0.4.2 | 0 / 21 | |
| 0.4.1 | 0 / 21 | |
| 0.4.0 | 0 / 21 | |
| 0.3.11 | 0 / 21 | |
| 0.3.10 | 0 / 21 | |
| 0.3.9 | 0 / 21 | |
| 0.3.8 | 0 / 21 | |
| 0.3.7 | 0 / 21 | |
| 0.3.6 | 0 / 20 | |
| 0.3.5 | 0 / 17 | |
| 0.3.4 | 0 / 17 | |
| 0.3.3 | 0 / 10 | |
| 0.3.2 | 0 / 10 | |
| 0.3.1 | 0 / 10 | |
| 0.3.0 | 0 / 10 | |
| 0.2.3 | 0 / 9 | |
| 0.2.2 | 0 / 9 |
v0.7.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 101arrowz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 101arrowz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 101arrowz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: 101arrowz.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.