@taiga-ui/stylelint-config
Taiga UI stylelint config
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:stylelint-plugin-use-baseline | AI (dependencies): Stylelint plugin used as a config dependency; no malicious indicators, stable pattern for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established Taiga UI toolkit package; provenance not yet enabled but no other risk signals present. | ai | |
| phantom-deps | phantom-dep:postcss-less | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-order | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-rem-over-px | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-use-logical | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-config-standard | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:@stylistic/stylelint-plugin | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-plugin-logical-css | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-plugin-use-baseline | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-no-unsupported-browser-features | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:@stylistic/stylelint-config | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Config-only package; deps referenced in config files, not JS imports. Expected pattern. | ai | |
| provenance | publisher-changed | AI (provenance): splincode is a named contributor in package.json and has a clean track record; transition appears legitimate for this package. | ai |
Versions (showing 94 of 594)
| Version | Deps | Published |
|---|---|---|
| 0.125.0 | 0 / 0 | |
| 0.124.0 | 0 / 0 | |
| 0.123.0 | 0 / 0 | |
| 0.122.3 | 0 / 0 | |
| 0.122.2 | 0 / 0 | |
| 0.122.1 | 0 / 0 | |
| 0.122.0 | 0 / 0 | |
| 0.121.1 | 0 / 0 | |
| 0.121.0 | 0 / 0 | |
| 0.120.1 | 0 / 0 | |
| 0.120.0 | 0 / 0 | |
| 0.119.0 | 0 / 0 | |
| 0.118.2 | 0 / 0 | |
| 0.118.1 | 0 / 0 | |
| 0.118.0 | 0 / 0 | |
| 0.117.0 | 0 / 0 | |
| 0.116.0 | 0 / 0 | |
| 0.115.4 | 0 / 0 | |
| 0.115.3 | 0 / 0 | |
| 0.115.2 | 0 / 0 | |
| 0.115.1 | 0 / 0 | |
| 0.115.0 | 0 / 0 | |
| 0.114.2 | 0 / 0 | |
| 0.114.1 | 0 / 0 | |
| 0.114.0 | 0 / 0 | |
| 0.113.10 | 0 / 0 | |
| 0.113.9 | 0 / 0 | |
| 0.113.8 | 0 / 0 | |
| 0.113.7 | 0 / 0 | |
| 0.113.6 | 0 / 0 | |
| 0.113.5 | 0 / 0 | |
| 0.113.4 | 0 / 0 | |
| 0.113.3 | 0 / 0 | |
| 0.113.2 | 0 / 0 | |
| 0.113.1 | 0 / 0 | |
| 0.113.0 | 0 / 0 | |
| 0.112.0 | 0 / 0 | |
| 0.111.0 | 0 / 0 | |
| 0.110.0 | 0 / 0 | |
| 0.109.2 | 0 / 0 | |
| 0.109.1 | 0 / 0 | |
| 0.109.0 | 0 / 0 | |
| 0.108.1 | 0 / 0 | |
| 0.108.0 | 0 / 0 | |
| 0.107.0 | 0 / 0 | |
| 0.106.0 | 0 / 0 | |
| 0.105.0 | 0 / 0 | |
| 0.104.0 | 0 / 0 | |
| 0.103.1 | 0 / 0 | |
| 0.103.0 | 0 / 0 | |
| 0.102.0 | 0 / 0 | |
| 0.101.0 | 0 / 0 | |
| 0.100.0 | 0 / 0 | |
| 0.99.0 | 0 / 0 | |
| 0.98.1 | 0 / 0 | |
| 0.98.0 | 0 / 0 | |
| 0.97.0 | 0 / 0 | |
| 0.96.0 | 0 / 0 | |
| 0.95.2 | 0 / 0 | |
| 0.95.1 | 0 / 0 | |
| 0.95.0 | 0 / 0 | |
| 0.94.1 | 0 / 0 | |
| 0.94.0 | 0 / 0 | |
| 0.92.0 | 0 / 0 | |
| 0.90.0 | 0 / 0 | |
| 0.22.3 | 0 / 0 | |
| 0.22.2 | 0 / 0 | |
| 0.22.1 | 0 / 0 | |
| 0.22.0 | 0 / 0 | |
| 0.21.0 | 0 / 0 | |
| 0.20.6 | 0 / 0 | |
| 0.20.5 | 0 / 0 | |
| 0.20.4 | 0 / 0 | |
| 0.20.3 | 0 / 0 | |
| 0.20.2 | 0 / 0 | |
| 0.20.1 | 0 / 0 | |
| 0.20.0 | 0 / 0 | |
| 0.19.0 | 5 / 0 | |
| 0.18.0 | 5 / 0 | |
| 0.17.0 | 5 / 0 | |
| 0.16.0 | 5 / 0 | |
| 0.15.0 | 5 / 0 | |
| 0.14.0 | 5 / 0 | |
| 0.13.6 | 5 / 0 | |
| 0.13.5 | 5 / 0 | |
| 0.13.4 | 5 / 0 | |
| 0.13.3 | 5 / 0 | |
| 0.13.2 | 5 / 0 | |
| 0.13.1 | 5 / 0 | |
| 0.13.0 | 5 / 0 | |
| 0.12.5 | 5 / 0 | |
| 0.12.4 | 5 / 0 | |
| 0.12.3 | 5 / 0 | |
| 0.12.2 | 5 / 0 |
v0.125.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.124.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.123.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.122.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.121.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.121.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.120.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.120.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.119.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.118.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.118.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.118.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.117.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.116.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.115.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.115.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.115.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.115.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.115.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.114.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.114.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.114.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.113.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.112.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.111.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.110.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.109.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.109.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.109.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.108.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.108.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.107.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.106.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.105.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.104.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.103.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.103.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.102.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.101.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.100.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.99.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.98.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.97.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.96.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.95.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.94.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.92.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.90.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.