← Home

grunt-contrib-clean

npm Repository Homepage

Clean files and folders

14
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

cowboyjmeastkellenvladikoffshamasindresorhus

Keywords

gruntplugincleancleanupremovedeletedelrmrmrfrimraf

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The cowboy→shama transition occurred in April 2013 and is a well-known historical maintainer handoff within the official grunt-contrib ecosystem. Shama is a recognized Grunt core contributor with a strong track record. ai

Versions (showing 14 of 14)

Version Deps Published
2.0.1 2 / 5
2.0.0 2 / 5
1.1.0 2 / 5
1.0.0 2 / 6
0.7.0 1 / 5
0.6.0 1 / 4
0.5.0 1 / 4
0.4.1 0 / 4
0.4.0 0 / 4
0.3.2 2 / 1
0.3.1 2 / 1
0.3.0 2 / 0
0.2.0 2 / 0
0.1.0 2 / 0

v2.0.1

1 finding
LOW No provenance attestation provenance

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

v2.0.0

1 finding
LOW No provenance attestation provenance

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

v1.1.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: shama → vladikoff (on 2017-04-13) provenance

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

v1.0.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: vladikoff → shama (on 2016-02-15) provenance

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

v0.4.1

2 findings
HIGH Publisher changed: cowboy → shama (on 2013-04-16) provenance

This version was published by a different npm account than previous versions on 2013-04-16. 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.