cssnano
A modular minifier, built on top of the PostCSS ecosystem.
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): cssnano moved to GitHub Actions CI/CD publishing with SLSA provenance; this is a security improvement, not a takeover. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy is relative to last vetted version (v4); cssnano has been actively publishing v5-v7 in the interim. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): lilconfig replaces cosmiconfig — a well-known lightweight config loader swap in the ecosystem. | ai | |
| bogus-package | bogus-package | AI (bogus-package): cssnano is a mature, well-known CSS minifier. Inflated semver and short README signals are false positives — v7.1.7 reflects the package's actual version history, not inflation. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is cssnano's documented preset-loading mechanism, allowing users to specify custom presets by name. This is a core feature, not a security risk. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 8.0.1 | 2 / 4 | |
| 8.0.0 | 2 / 4 | |
| 7.1.9 | 2 / 4 | |
| 7.1.8 | 2 / 4 | |
| 7.1.7 | 2 / 4 | |
| 7.1.6 | 2 / 4 | |
| 7.1.5 | 2 / 4 | |
| 7.1.4 | 2 / 4 | |
| 7.1.3 | 2 / 4 | |
| 7.1.2 | 2 / 4 | |
| 7.1.1 | 2 / 4 | |
| 7.1.0 | 2 / 4 | |
| 7.0.7 | 2 / 4 | |
| 7.0.6 | 2 / 4 | |
| 7.0.5 | 2 / 4 | |
| 7.0.4 | 2 / 4 | |
| 7.0.3 | 2 / 4 | |
| 7.0.2 | 2 / 4 | |
| 7.0.1 | 2 / 4 | |
| 7.0.0 | 2 / 4 | |
| 6.1.2 | 2 / 4 | |
| 6.1.1 | 2 / 4 | |
| 6.1.0 | 2 / 4 | |
| 6.0.5 | 2 / 4 | |
| 6.0.4 | 2 / 4 | |
| 6.0.3 | 2 / 4 | |
| 6.0.2 | 2 / 4 | |
| 6.0.1 | 2 / 4 | |
| 6.0.0 | 2 / 4 | |
| 4.1.10 | 4 / 9 |
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.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.1.3
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.1.2
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.1.1
2 findingsThis version was published by a different npm account than previous versions on 2025-08-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.0
2 findingsThis version was published by a different npm account than previous versions on 2025-07-14. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.7
2 findingsThis version was published by a different npm account than previous versions on 2025-05-06. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.6
2 findingsThis version was published by a different npm account than previous versions on 2024-09-04. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.5
2 findingsThis version was published by a different npm account than previous versions on 2024-08-09. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.4
2 findingsThis version was published by a different npm account than previous versions on 2024-07-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.3
2 findingsThis version was published by a different npm account than previous versions on 2024-06-19. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.2
2 findingsThis version was published by a different npm account than previous versions on 2024-06-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.1
2 findingsThis version was published by a different npm account than previous versions on 2024-04-26. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
2 findingsThis version was published by a different npm account than previous versions on 2024-04-24. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-03-27. This could indicate a legitimate maintainer transition or an account compromise.
v4.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.