@nice-move/stylelint-config
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:settingz | AI (dependencies): Long-standing dep in this package; stable across many approved versions. | ai | |
| dependencies | unvetted-dep:stylelint-suitcss | AI (dependencies): Long-standing dep in this package; stable across many approved versions. | ai | |
| phantom-deps | phantom-dep:stylelint-require-units | AI (phantom-deps): Config package references deps via config strings, not direct imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-suitcss | AI (phantom-deps): Config package references plugins by name in config objects, not via import; stable false positive. | ai | |
| phantom-deps | phantom-dep:stylelint-no-unresolved-module | AI (phantom-deps): Config package; deps declared for peer resolution, not direct import. Stable pattern. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-declaration-block-no-ignored-properties | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:postcss-html | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:postcss-less | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:stylelint-scss | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai | |
| phantom-deps | phantom-dep:postcss-markdown | AI (phantom-deps): Stylelint config package; deps are referenced as config values, not direct imports. Stable FP for this package. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 0.10.28 | 9 / 0 | |
| 0.10.27 | 9 / 0 | |
| 0.10.26 | 9 / 0 | |
| 0.10.25 | 10 / 0 | |
| 0.10.24 | 10 / 0 | |
| 0.10.23 | 10 / 0 | |
| 0.10.22 | 11 / 0 | |
| 0.10.20 | 11 / 0 | |
| 0.10.19 | 11 / 0 | |
| 0.10.18 | 11 / 0 | |
| 0.10.17 | 11 / 0 | |
| 0.10.16 | 11 / 0 | |
| 0.10.15 | 12 / 0 |
v0.10.28
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.27
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.26
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.25
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.