@dfds-ui/stylelint-config
Shared stylelint config within DFDS
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:stylelint | AI (phantom-deps): Config-only package; deps are referenced in config files, not imported directly. Stable pattern. | ai | |
| phantom-deps | phantom-dep:stylelint-config-prettier | AI (phantom-deps): Config-only package; deps referenced in config files, not imported directly. | ai | |
| phantom-deps | phantom-dep:stylelint-csstree-validator | AI (phantom-deps): Config-only package; deps referenced in config files, not imported directly. | ai | |
| phantom-deps | phantom-dep:stylelint-config-styled-components | AI (phantom-deps): Config-only package; deps referenced in config files, not imported directly. | ai | |
| phantom-deps | phantom-dep:stylelint-processor-styled-components | AI (phantom-deps): Config-only package; deps referenced in config files, not imported directly. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Intentionally minimal shared config package; tiny payload and no repo URL are expected for this type of internal tooling. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 5 / 0 | |
| 2.0.29 | 5 / 0 | |
| 2.0.28 | 5 / 0 | |
| 2.0.27 | 5 / 0 | |
| 2.0.26 | 5 / 0 | |
| 2.0.25 | 5 / 0 | |
| 2.0.24 | 5 / 0 |
v2.0.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.