cssnano-preset-advanced
Advanced optimisations for cssnano; may or may not break your CSS!
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Legitimate migration to GitHub Actions CI/CD publishing with SLSA provenance for cssnano monorepo. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): cssnano monorepo resumed publishing via CI/CD; dormancy reflects normal maintenance cadence. | ai | |
| dependencies | unvetted-dep:postcss-merge-idents | AI (dependencies): postcss-merge-idents is a cssnano monorepo package; unvetted status is a pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:postcss-reduce-idents | AI (dependencies): postcss-reduce-idents is a cssnano monorepo package; unvetted status is a pipeline lag, not a security concern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): cssnano monorepo releases explain all signals: mass-production publisher is expected, inflated semver tracks monorepo versioning, no keywords is common for ecosystem sub-packages. | ai | |
| phantom-deps | phantom-dep:browserslist | AI (phantom-deps): browserslist is legitimately declared for autoprefixer config passthrough; not directly imported by design. | ai | |
| dependencies | unvetted-dep:postcss-discard-unused | AI (dependencies): postcss-discard-unused is a cssnano monorepo package; unvetted status is a pipeline lag, not a security concern. | ai | |
| dependencies | unvetted-dep:postcss-zindex | AI (dependencies): postcss-zindex is a cssnano monorepo package; unvetted status is a pipeline lag, not a security concern. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 8 / 1 | |
| 8.0.0 | 8 / 1 | |
| 7.0.16 | 7 / 1 | |
| 7.0.15 | 7 / 1 | |
| 7.0.14 | 7 / 1 | |
| 7.0.13 | 7 / 1 | |
| 7.0.12 | 7 / 1 | |
| 7.0.11 | 7 / 1 | |
| 7.0.10 | 7 / 1 | |
| 7.0.9 | 7 / 1 | |
| 7.0.8 | 7 / 1 | |
| 7.0.7 | 7 / 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.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.13
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.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.10
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.