@csstools/normalize.css
A cross-browser CSS foundation
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
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): romainmenke is a well-established csstools org maintainer with 900 approved packages and 0 rejections; the jonathantneal→romainmenke transition is a documented legitimate org handoff. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers romainmenke and alaguna are part of the csstools org; this is a legitimate team expansion, not a suspicious takeover. | ai | |
| provenance | no-provenance | AI (provenance): Pure CSS package with no executable code; lack of provenance attestation carries negligible risk for this package type. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 12.1.1 | 0 / 0 | |
| 12.1.0 | 0 / 0 | |
| 12.0.0 | 0 / 2 | |
| 11.0.1 | 0 / 2 | |
| 11.0.0 | 0 / 2 | |
| 10.1.0 | 0 / 2 | |
| 10.0.0 | 0 / 2 | |
| 9.0.1 | 0 / 2 | |
| 9.0.0 | 0 / 2 | |
| 8.0.0 | 0 / 2 |
v12.1.0
2 findingsThis version was published by a different npm account than previous versions on 2023-12-29. 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.
v12.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.