← Home

grunt-contrib

npm Repository Homepage

The entire grunt-contrib suite.

16
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

tkellencowboyshamavladikoffsindresorhusjmeas

Keywords

gruntplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): Package is over 5000 days old, predating Sigstore provenance. No provenance will ever be backfilled for historical versions; not a meaningful risk signal for this package. ai
semgrep semgrep:new-function-constructor AI (semgrep): new Function() in tasks/jst.js is intentional template compilation — standard pattern for JST task implementations in grunt plugins, not a security risk. ai
phantom-deps phantom-dep:grunt AI (phantom-deps): grunt is used via task configuration rather than direct require(); normal pattern for grunt plugin collections. ai
phantom-deps phantom-dep:express AI (phantom-deps): express is orchestrated as a grunt task dependency, not directly imported; expected pattern for this package. ai
phantom-deps phantom-dep:requirejs AI (phantom-deps): requirejs is orchestrated as a grunt task dependency, not directly imported; expected pattern for this package. ai
provenance publisher-changed AI (provenance): Publisher change from vladikoff to sindresorhus occurred in 2014; sindresorhus is a highly trusted npm publisher. This is a historical, legitimate maintainer transition for the gruntjs org. ai

Versions (showing 16 of 16)

Version Deps Published
0.11.0 1 / 4
0.10.2 1 / 5
0.10.1 1 / 5
0.10.0 1 / 5
0.9.0 1 / 5
0.8.0 1 / 5
0.6.1 26 / 2
0.6.0 25 / 2
0.1.4 14 / 1
0.0.7 9 / 1
0.0.6 8 / 1
0.0.5 8 / 1
0.0.4 7 / 1
0.0.3 7 / 1
0.0.2 9 / 1
0.0.1 9 / 1

v0.11.0

2 findings
HIGH Publisher changed: vladikoff → sindresorhus (on 2014-05-01) provenance

This version was published by a different npm account than previous versions on 2014-05-01. 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.10.2

1 finding
LOW No provenance attestation provenance

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

v0.10.1

1 finding
LOW No provenance attestation provenance

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

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.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 → vladikoff (on 2014-02-11) provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

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
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 2013-03-26) provenance

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

v0.1.4

1 finding
LOW No provenance attestation provenance

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

v0.0.7

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

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.

v0.0.3

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.

v0.0.2

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.

v0.0.1

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.