grunt-contrib-uglify
Minify JavaScript files with UglifyJS
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): vladikoff is a long-standing, highly trusted npm publisher (837 approved packages). The transition from xhmikosr to vladikoff is consistent with routine maintainer rotation within the gruntjs org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): alexlamsl is a known contributor in the UglifyJS/minification ecosystem. Addition is consistent with legitimate project maintenance, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence is expected for this era of the package and does not indicate risk. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 4 / 5 | |
| 5.2.1 | 4 / 5 | |
| 5.1.0 | 4 / 5 | |
| 5.0.1 | 4 / 5 | |
| 5.0.0 | 4 / 5 | |
| 4.0.1 | 4 / 5 | |
| 4.0.0 | 4 / 5 | |
| 3.4.0 | 4 / 5 | |
| 3.3.0 | 4 / 5 | |
| 3.2.1 | 4 / 5 | |
| 3.1.0 | 4 / 5 | |
| 3.0.1 | 4 / 5 | |
| 3.0.0 | 4 / 5 | |
| 2.3.0 | 5 / 5 | |
| 2.2.1 | 5 / 5 | |
| 2.2.0 | 5 / 5 | |
| 2.1.0 | 5 / 5 | |
| 2.0.0 | 5 / 5 | |
| 1.0.2 | 5 / 5 | |
| 1.0.1 | 5 / 6 | |
| 1.0.0 | 5 / 6 | |
| 0.11.1 | 5 / 6 | |
| 0.11.0 | 5 / 6 | |
| 0.10.1 | 5 / 6 | |
| 0.10.0 | 5 / 6 | |
| 0.9.2 | 5 / 6 | |
| 0.9.1 | 5 / 6 | |
| 0.9.0 | 5 / 6 | |
| 0.8.1 | 5 / 6 | |
| 0.8.0 | 5 / 6 | |
| 0.7.0 | 5 / 5 | |
| 0.6.0 | 5 / 5 | |
| 0.5.1 | 4 / 5 | |
| 0.5.0 | 4 / 5 | |
| 0.4.1 | 3 / 5 | |
| 0.4.0 | 3 / 5 | |
| 0.3.3 | 3 / 5 | |
| 0.3.2 | 3 / 5 | |
| 0.3.1 | 3 / 5 | |
| 0.3.0 | 3 / 5 | |
| 0.2.7 | 2 / 5 | |
| 0.2.6 | 2 / 5 | |
| 0.2.5 | 2 / 5 | |
| 0.2.4 | 2 / 5 | |
| 0.2.3 | 2 / 5 | |
| 0.2.2 | 2 / 5 | |
| 0.2.1 | 2 / 5 | |
| 0.2.0 | 2 / 5 | |
| 0.1.2 | 2 / 5 | |
| 0.1.1 | 2 / 5 | |
| 0.1.0 | 2 / 5 |
v5.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
2 findingsThis version was published by a different npm account than previous versions on 2020-07-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2019-03-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.0.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-04. This could indicate a legitimate maintainer transition or an account compromise.