grunt-legacy-util
Some old grunt utils provided for backwards compatibility.
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): Legitimate transfer from cowboy (Ben Alman) to shama (Kyle Robinson Young), both core Grunt team members in the gruntjs GitHub org. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): shama and vladikoff are known Grunt team members; legitimate maintainer addition within the gruntjs organization. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): grunt-legacy-util is a build tool utility; child_process.spawn is core to its documented purpose of running tasks. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 2.0.1 | 7 / 6 | |
| 2.0.0 | 7 / 6 | |
| 1.1.1 | 7 / 6 | |
| 1.1.0 | 7 / 6 | |
| 1.0.0 | 7 / 6 | |
| 0.2.0 | 7 / 5 | |
| 0.1.2 | 7 / 4 | |
| 0.1.1 | 7 / 4 | |
| 0.1.0 | 8 / 4 |
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
2 findingsThis version was published by a different npm account than previous versions on 2018-05-20. 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.
v1.0.0
2 findingsThis version was published by a different npm account than previous versions on 2016-04-03. 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.