postcss-minify-selectors
Minify selectors with PostCSS.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from human publisher to GitHub Actions CI/CD with SLSA provenance; expected for cssnano monorepo modernization. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy explained by release pipeline migration to GitHub Actions; SLSA provenance confirms legitimate CI/CD origin. | ai | |
| dependencies | unvetted-dep:caniuse-api | AI (dependencies): caniuse-api is a well-established CSS tooling dependency used by autoprefixer, stylelint, and others; not a risk for this package. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 4 / 3 | |
| 8.0.0 | 4 / 3 | |
| 7.1.2 | 4 / 3 | |
| 7.1.1 | 4 / 3 | |
| 7.1.0 | 4 / 3 | |
| 7.0.6 | 2 / 2 | |
| 7.0.5 | 2 / 2 |
v8.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v8.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.6
2 findingsThis version was published by a different npm account than previous versions on 2026-03-06. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.