css-whitespace
Whitespace significant CSS to regular CSS
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): Publisher change from tjholowaychuk to mattmueller occurred in 2015 as part of a known reworkcss project maintainer transition. Historical, not indicative of compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mattmueller was added as maintainer in 2015 during the documented reworkcss transition. Stable historical fact for this package. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy followed by 2015 publish aligns with the known maintainer handoff period. No recent suspicious activity; this is a historical signal. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.1.1 | 1 / 2 | |
| 1.1.0 | 1 / 2 | |
| 1.0.0 | 1 / 2 | |
| 0.0.6 | 1 / 2 | |
| 0.0.5 | 1 / 2 | |
| 0.0.4 | 1 / 2 | |
| 0.0.3 | 1 / 2 | |
| 0.0.2 | 1 / 2 | |
| 0.0.1 | 1 / 2 |
v1.1.1
2 findingsThis version was published by a different npm account than previous versions on 2015-02-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.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.