← Home

grunt-lib-contrib

npm Repository Homepage

Common functionality shared across grunt-contrib tasks.

10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

cowboytkellenshamasindresorhus

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from shama to tkellen occurred in 2013; tkellen is a core Grunt contributor with 683 approved packages. This is a stable historical transition, not a compromise signal. ai

Versions (showing 10 of 10)

Version Deps Published
0.7.1 2 / 3
0.7.0 2 / 3
0.6.1 1 / 3
0.6.0 1 / 3
0.5.3 1 / 3
0.5.2 1 / 3
0.5.1 1 / 3
0.4.0 0 / 1
0.3.1 0 / 1
0.3.0 0 / 1

v0.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tkellen → sindresorhus (on 2014-02-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2014-02-28. This could indicate a legitimate maintainer transition or an account compromise.

v0.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

2 findings
HIGH Publisher changed: shama → tkellen (on 2013-03-14) provenance

This version was published by a different npm account than previous versions on 2013-03-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.3

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cowboy → shama (on 2013-02-23) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2013-02-23. This could indicate a legitimate maintainer transition or an account compromise.

v0.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: tkellen → cowboy (on 2013-01-10) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2013-01-10. This could indicate a legitimate maintainer transition or an account compromise.

v0.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.3.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: cowboy → tkellen (on 2012-10-29) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2012-10-29. This could indicate a legitimate maintainer transition or an account compromise.

v0.3.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.