postcss-reduce-initial
Reduce initial definitions to the actual initial value, where possible.
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 to GitHub Actions CI/CD publishing with SLSA attestation; expected for cssnano monorepo. | ai | |
| bogus-package | bogus-package | AI (bogus-package): cssnano is a monorepo with many similarly-named plugins; inflated semver and mass-production signals are false positives for this well-known CSS tooling ecosystem package. | ai | |
| dependencies | unvetted-dep:caniuse-api | AI (dependencies): caniuse-api is a standard, widely-used dependency in the CSS tooling ecosystem; no material risk for this package. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 8.0.0 | 2 / 3 | |
| 7.0.9 | 2 / 3 | |
| 7.0.8 | 2 / 3 | |
| 7.0.7 | 2 / 3 | |
| 7.0.6 | 2 / 3 | |
| 7.0.5 | 2 / 3 | |
| 7.0.4 | 2 / 3 | |
| 7.0.3 | 2 / 3 |
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.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.7
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
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.5
2 findingsThis version was published by a different npm account than previous versions on 2025-10-29. 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.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.