stylelint-scss
A collection of SCSS-specific rules for Stylelint
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): jeddy3 is a long-standing trusted npm publisher (463 approved pkgs) and known stylelint ecosystem maintainer. Legitimate maintainer transition. | ai |
Versions (showing 51 of 120)
| Version | Deps | Published |
|---|---|---|
| 7.1.1 | 11 / 18 | |
| 7.1.0 | 11 / 18 | |
| 7.0.0 | 8 / 14 | |
| 6.14.0 | 8 / 14 | |
| 6.13.0 | 8 / 14 | |
| 6.12.1 | 8 / 14 | |
| 6.12.0 | 8 / 14 | |
| 6.11.1 | 8 / 14 | |
| 6.11.0 | 8 / 14 | |
| 6.10.1 | 8 / 14 | |
| 6.10.0 | 8 / 14 | |
| 6.9.0 | 8 / 14 | |
| 6.8.1 | 8 / 14 | |
| 6.8.0 | 8 / 14 | |
| 6.7.0 | 7 / 14 | |
| 6.6.0 | 7 / 14 | |
| 6.5.1 | 7 / 13 | |
| 6.5.0 | 7 / 13 | |
| 6.4.1 | 5 / 13 | |
| 6.4.0 | 5 / 13 | |
| 6.3.2 | 5 / 13 | |
| 6.3.1 | 5 / 13 | |
| 6.3.0 | 5 / 13 | |
| 6.2.1 | 5 / 13 | |
| 6.2.0 | 5 / 13 | |
| 6.1.0 | 5 / 13 | |
| 6.0.0 | 5 / 13 | |
| 5.3.2 | 5 / 12 | |
| 5.3.1 | 5 / 12 | |
| 5.3.0 | 5 / 12 | |
| 5.2.1 | 5 / 12 | |
| 5.2.0 | 4 / 12 | |
| 5.1.0 | 4 / 12 | |
| 5.0.1 | 4 / 13 | |
| 5.0.0 | 4 / 13 | |
| 4.7.0 | 4 / 19 | |
| 4.6.0 | 5 / 19 | |
| 4.5.0 | 5 / 20 | |
| 4.4.0 | 5 / 20 | |
| 4.3.0 | 5 / 20 | |
| 4.2.0 | 5 / 20 | |
| 4.1.0 | 5 / 20 | |
| 4.0.1 | 5 / 20 | |
| 4.0.0 | 5 / 20 | |
| 3.21.0 | 5 / 19 | |
| 3.20.1 | 5 / 19 | |
| 3.20.0 | 5 / 19 | |
| 3.19.0 | 5 / 19 | |
| 3.18.0 | 5 / 19 | |
| 3.17.2 | 5 / 19 | |
| 3.17.1 | 5 / 19 |
v7.1.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-11. This could indicate a legitimate maintainer transition or an account compromise.
v7.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2026-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-15. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.