cssnano-preset-default
Safe defaults for cssnano which require minimal configuration.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:postcss-minify-gradients | AI (dependencies): postcss-minify-gradients is a first-party cssnano ecosystem package; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): cssnano-preset-default is a legitimate monorepo package from cssnano/cssnano. High version on first registry entry reflects prior publishing history; mass-production flag reflects monorepo structure, not spam. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 29 / 1 | |
| 8.0.0 | 29 / 1 | |
| 7.0.17 | 30 / 1 | |
| 7.0.15 | 30 / 1 | |
| 7.0.12 | 30 / 1 | |
| 7.0.9 | 30 / 1 | |
| 7.0.8 | 30 / 1 | |
| 7.0.7 | 30 / 1 | |
| 5.2.12 | 29 / 1 |
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.0.17
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.12
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.