@morev/stylelint-plugin
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss | AI (phantom-deps): Runtime dependency for stylelint plugin; used indirectly through postcss-selector-parser. | ai | |
| phantom-deps | phantom-dep:postcss-selector-parser | AI (phantom-deps): Runtime dependency for BEM/SCSS rule implementation; stable across versions. | ai | |
| phantom-deps | phantom-dep:valibot | AI (phantom-deps): Runtime dependency for validation; used indirectly in plugin logic. | ai | |
| phantom-deps | phantom-dep:@morev/utils | AI (phantom-deps): Same-org scoped dependency; stable pattern for this publisher. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 0.5.0 | 4 / 23 | |
| 0.4.0 | 4 / 23 | |
| 0.3.1 | 4 / 23 | |
| 0.3.0 | 4 / 21 | |
| 0.2.0 | 4 / 21 | |
| 0.1.2 | 4 / 21 | |
| 0.1.1 | 4 / 21 | |
| 0.1.0 | 4 / 21 |
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.