← Home

grunt-contrib-sass

Compile Sass to CSS

25
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

cowboyjmeasshamasindresorhustkellenvladikoff

Keywords

gruntpluginscsssasscsscompilepreprocessorstyle

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): The shama→sindresorhus transition occurred in 2013 and is a well-known legitimate maintainer handoff within the Grunt ecosystem. sindresorhus is a highly trusted publisher with thousands of approved packages. ai

Versions (showing 25 of 25)

Version Deps Published
2.0.0 5 / 5
1.0.0 5 / 6
0.9.2 5 / 6
0.9.1 5 / 6
0.9.0 5 / 6
0.8.1 5 / 5
0.8.0 5 / 5
0.7.4 5 / 5
0.7.3 5 / 5
0.7.2 5 / 5
0.7.1 4 / 5
0.7.0 4 / 5
0.6.0 2 / 5
0.5.1 2 / 5
0.5.0 1 / 5
0.4.1 1 / 5
0.4.0 1 / 5
0.3.0 1 / 5
0.2.2 1 / 5
0.2.1 1 / 6
0.2.0 1 / 5
0.1.3 1 / 2
0.1.2 1 / 2
0.1.1 1 / 2
0.1.0 1 / 2

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.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: sindresorhus → vladikoff (on 2016-03-04) provenance

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

v0.5.0

2 findings
HIGH Publisher changed: shama → sindresorhus (on 2013-08-21) provenance

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