grunt-contrib-coffee
Compile CoffeeScript files to JavaScript
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): tkellen→shama transition is a documented Grunt team maintainer handoff in Jan 2014; both are legitimate gruntjs org contributors. Stable for this package. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): vladikoff and jmeas are known Grunt ecosystem contributors added as part of the official gruntjs org maintainer expansion. No compromise indicators. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): chalk and lodash are well-established, widely-used utility packages with no malicious history. Their addition is benign for a CoffeeScript compilation plugin. | ai | |
| dependencies | unvetted-dep:grunt-contrib-lib | AI (dependencies): grunt-contrib-lib is a legitimate grunt ecosystem support library from the gruntjs GitHub org; its use here is expected and benign for this package. | ai | |
| dependencies | unvetted-dep:coffeescript | AI (dependencies): coffeescript is the canonical CoffeeScript compiler package; its use here is expected and legitimate for a CoffeeScript Grunt plugin. | ai | |
| dependencies | unvetted-dep:uri-path | AI (dependencies): uri-path is a small, legitimate utility used for path handling; no malicious signals and appropriate for this package's use case. | ai | |
| provenance | no-provenance | AI (provenance): Package is 4970 days old from the official gruntjs org; lack of Sigstore provenance is expected for packages predating that tooling. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 2.1.0 | 4 / 5 | |
| 2.0.0 | 4 / 5 | |
| 1.0.0 | 4 / 6 | |
| 0.13.0 | 4 / 6 | |
| 0.12.0 | 4 / 5 | |
| 0.11.1 | 3 / 5 | |
| 0.11.0 | 3 / 5 | |
| 0.10.1 | 3 / 5 | |
| 0.10.0 | 3 / 5 | |
| 0.9.0 | 3 / 5 | |
| 0.8.2 | 2 / 5 | |
| 0.8.0 | 1 / 5 | |
| 0.7.0 | 1 / 5 | |
| 0.6.7 | 1 / 5 | |
| 0.6.6 | 1 / 5 | |
| 0.6.5 | 1 / 5 | |
| 0.6.4 | 1 / 5 | |
| 0.6.3 | 1 / 5 | |
| 0.6.2 | 1 / 5 | |
| 0.6.1 | 1 / 5 | |
| 0.6.0 | 1 / 5 | |
| 0.5.0 | 1 / 5 | |
| 0.4.0 | 1 / 5 | |
| 0.3.2 | 2 / 2 | |
| 0.3.1 | 2 / 2 | |
| 0.3.0 | 2 / 2 | |
| 0.2.0 | 2 / 2 |
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
2 findingsThis version was published by a different npm account than previous versions on 2015-02-20. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
2 findingsThis version was published by a different npm account than previous versions on 2014-10-04. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
2 findingsThis version was published by a different npm account than previous versions on 2014-08-15. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
2 findingsThis version was published by a different npm account than previous versions on 2014-08-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
2 findingsThis version was published by a different npm account than previous versions on 2014-02-17. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
2 findingsThis version was published by a different npm account than previous versions on 2014-02-07. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version was published by a different npm account than previous versions on 2014-01-29. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
2 findingsThis version was published by a different npm account than previous versions on 2013-02-18. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.