grunt
The JavaScript Task Runner
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:dynamic-require | AI (semgrep): grunt's internal gRequire loads submodules from ./grunt/ prefix — standard pattern in grunt's architecture, not user-controlled. | ai | |
| phantom-deps | phantom-dep:exit | AI (phantom-deps): exit is a declared dependency used indirectly by grunt's internal modules; stable for this package. | ai | |
| phantom-deps | phantom-dep:grunt-cli | AI (phantom-deps): grunt-cli is a declared dependency used indirectly; standard for grunt's architecture. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 1.6.2 | 13 / 7 | |
| 1.6.1 | 13 / 7 | |
| 1.6.0 | 15 / 7 | |
| 1.5.3 | 15 / 7 |
v1.6.2
2 findingsThis version was published by a different npm account than previous versions on 2026-04-14. 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.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.