@newhighsco/stylelint-config
New High Score shareable config 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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stylelint-order | AI (phantom-deps): Stylelint config packages reference plugins via config files, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-prettier | AI (phantom-deps): Stylelint config packages reference plugins via config files, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-config-css-modules | AI (phantom-deps): Stylelint config packages reference plugins via config files, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-config-standard-scss | AI (phantom-deps): Stylelint config packages reference plugins via config files, not direct imports; stable pattern for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 4.0.44 | 4 / 2 | |
| 4.0.43 | 4 / 2 | |
| 4.0.42 | 4 / 2 | |
| 4.0.41 | 4 / 2 | |
| 4.0.40 | 4 / 2 | |
| 4.0.39 | 4 / 2 | |
| 4.0.38 | 4 / 2 | |
| 4.0.37 | 4 / 2 | |
| 4.0.36 | 4 / 2 | |
| 4.0.35 | 4 / 2 | |
| 4.0.34 | 4 / 2 | |
| 4.0.33 | 4 / 2 | |
| 4.0.32 | 4 / 2 | |
| 4.0.31 | 4 / 2 | |
| 4.0.30 | 4 / 2 | |
| 4.0.29 | 4 / 2 | |
| 4.0.28 | 4 / 2 | |
| 4.0.27 | 4 / 2 | |
| 4.0.26 | 5 / 2 | |
| 4.0.25 | 5 / 2 | |
| 4.0.24 | 5 / 2 | |
| 4.0.23 | 5 / 2 | |
| 4.0.22 | 5 / 2 | |
| 4.0.21 | 5 / 2 | |
| 4.0.20 | 5 / 2 | |
| 4.0.19 | 5 / 2 | |
| 4.0.18 | 5 / 2 | |
| 4.0.17 | 5 / 2 | |
| 4.0.16 | 5 / 2 | |
| 4.0.15 | 5 / 2 | |
| 4.0.14 | 5 / 2 | |
| 4.0.13 | 5 / 2 |
v4.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.36
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.