@wordpress/stylelint-config
stylelint config for WordPress development.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@wordpress/theme | AI (phantom-deps): Config package; dependencies referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@stylistic/stylelint-plugin | AI (phantom-deps): Config package; dependencies referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:stylelint-config-recommended | AI (phantom-deps): Config package; dependencies referenced in config files, not direct imports. | ai | |
| phantom-deps | phantom-dep:stylelint-config-recommended-scss | AI (phantom-deps): Config package; dependencies referenced in config files, not direct imports. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 23.40.0 | 4 / 2 | |
| 23.39.0 | 4 / 2 | |
| 23.38.0 | 4 / 2 | |
| 23.37.0 | 4 / 2 | |
| 23.36.0 | 4 / 2 | |
| 23.35.0 | 4 / 2 | |
| 23.34.0 | 4 / 2 | |
| 23.33.0 | 4 / 2 | |
| 23.32.0 | 4 / 2 | |
| 23.31.0 | 4 / 2 | |
| 23.30.0 | 4 / 2 | |
| 23.29.0 | 3 / 0 | |
| 23.28.0 | 3 / 0 | |
| 23.27.0 | 3 / 0 | |
| 23.26.0 | 3 / 0 | |
| 23.25.1 | 3 / 0 | |
| 23.25.0 | 3 / 0 | |
| 23.24.0 | 3 / 0 | |
| 23.23.0 | 3 / 0 | |
| 23.22.0 | 3 / 0 | |
| 23.21.0 | 3 / 0 | |
| 23.20.0 | 3 / 0 | |
| 23.19.0 | 3 / 0 | |
| 23.18.0 | 3 / 0 | |
| 23.17.0 | 3 / 0 | |
| 23.16.0 | 3 / 0 | |
| 23.15.0 | 3 / 0 |
v23.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v23.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.34.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.25.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.