uglify-js
JavaScript parser, mangler/compressor and beautifier toolkit
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 |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode in lib/minify.js is used to decode inline source maps — a documented, legitimate feature of uglify-js. Not a malicious payload vector. | ai | |
| phantom-deps | phantom-dep:commander | AI (phantom-deps): commander is a declared runtime dep used by the CLI binary (bin/uglifyjs); not imported in the library entry point but legitimately used. Stable false positive for this package. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is an intentional, documented pattern in uglify-js for dynamically constructing AST node class constructors. Not malicious; stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): async is a declared runtime dependency used in build/config context; phantom-dep finding is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:uglify-to-browserify | AI (phantom-deps): uglify-to-browserify is a declared dependency used as a browserify transform in package.json config; phantom-dep finding is a false positive for this package. | ai |
Versions (showing 100 of 249)
| Version | Deps | Published |
|---|---|---|
| 3.19.3 | 0 / 2 | |
| 3.19.2 | 0 / 2 | |
| 3.19.1 | 0 / 2 | |
| 3.19.0 | 0 / 2 | |
| 3.18.0 | 0 / 2 | |
| 3.17.4 | 0 / 2 | |
| 3.17.3 | 0 / 2 | |
| 3.17.2 | 0 / 2 | |
| 3.17.1 | 0 / 2 | |
| 3.17.0 | 0 / 2 | |
| 3.16.3 | 0 / 2 | |
| 3.16.2 | 0 / 2 | |
| 3.16.1 | 0 / 2 | |
| 3.16.0 | 0 / 2 | |
| 3.15.5 | 0 / 2 | |
| 3.15.4 | 0 / 2 | |
| 3.15.3 | 0 / 2 | |
| 3.15.2 | 0 / 2 | |
| 3.15.1 | 0 / 2 | |
| 3.15.0 | 0 / 2 | |
| 3.14.5 | 0 / 2 | |
| 3.14.4 | 0 / 2 | |
| 3.14.3 | 0 / 2 | |
| 3.14.2 | 0 / 2 | |
| 3.14.1 | 0 / 2 | |
| 3.14.0 | 0 / 2 | |
| 3.13.10 | 0 / 2 | |
| 3.13.9 | 0 / 2 | |
| 3.13.8 | 0 / 2 | |
| 3.13.7 | 0 / 2 | |
| 3.13.6 | 0 / 2 | |
| 3.13.5 | 0 / 2 | |
| 3.13.4 | 0 / 2 | |
| 3.13.3 | 0 / 2 | |
| 3.13.2 | 0 / 2 | |
| 3.13.1 | 0 / 2 | |
| 3.13.0 | 0 / 2 | |
| 3.12.8 | 0 / 2 | |
| 3.12.7 | 0 / 2 | |
| 3.12.6 | 0 / 2 | |
| 3.12.5 | 0 / 2 | |
| 3.12.4 | 0 / 2 | |
| 3.12.3 | 0 / 2 | |
| 3.12.2 | 0 / 2 | |
| 3.12.1 | 0 / 2 | |
| 3.12.0 | 0 / 2 | |
| 3.11.6 | 0 / 2 | |
| 3.11.5 | 0 / 2 | |
| 3.11.4 | 0 / 2 | |
| 3.11.3 | 0 / 2 | |
| 3.11.2 | 0 / 2 | |
| 3.11.1 | 0 / 2 | |
| 3.11.0 | 0 / 2 | |
| 3.10.4 | 0 / 2 | |
| 3.10.3 | 0 / 2 | |
| 3.10.2 | 0 / 2 | |
| 3.10.1 | 0 / 2 | |
| 3.10.0 | 0 / 2 | |
| 3.9.4 | 1 / 2 | |
| 3.9.3 | 1 / 2 | |
| 3.9.2 | 1 / 2 | |
| 3.9.1 | 1 / 2 | |
| 3.9.0 | 1 / 2 | |
| 3.8.1 | 2 / 2 | |
| 3.8.0 | 2 / 2 | |
| 3.7.7 | 2 / 2 | |
| 3.7.6 | 2 / 2 | |
| 3.7.5 | 2 / 2 | |
| 3.7.4 | 2 / 2 | |
| 3.7.3 | 2 / 2 | |
| 3.7.2 | 2 / 2 | |
| 3.7.1 | 2 / 2 | |
| 3.7.0 | 2 / 2 | |
| 3.6.9 | 2 / 2 | |
| 3.6.8 | 2 / 2 | |
| 3.6.7 | 2 / 2 | |
| 3.6.6 | 2 / 2 | |
| 3.6.5 | 2 / 2 | |
| 3.6.4 | 2 / 2 | |
| 3.6.3 | 2 / 2 | |
| 3.6.2 | 2 / 2 | |
| 3.6.1 | 2 / 2 | |
| 3.6.0 | 2 / 2 | |
| 3.5.15 | 2 / 2 | |
| 3.5.14 | 2 / 2 | |
| 3.5.13 | 2 / 2 | |
| 3.5.12 | 2 / 2 | |
| 3.5.11 | 2 / 2 | |
| 3.5.10 | 2 / 2 | |
| 3.5.9 | 2 / 2 | |
| 3.5.8 | 2 / 2 | |
| 3.5.7 | 2 / 2 | |
| 3.5.6 | 2 / 2 | |
| 3.5.5 | 2 / 2 | |
| 3.5.4 | 2 / 2 | |
| 3.5.3 | 2 / 2 | |
| 3.5.2 | 2 / 2 | |
| 3.5.1 | 2 / 2 | |
| 3.5.0 | 2 / 2 | |
| 3.4.10 | 2 / 2 |
v3.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.