@csstools/postcss-logical-resize
Use logical values in the resize property
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): Legitimate maintainer transition from alaguna to romainmenke; both are listed as contributors in package.json and romainmenke is a highly trusted publisher in the csstools ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): romainmenke is a core csstools maintainer with an extensive trusted publishing history; this is a legitimate project handoff. | ai | |
| license | uncommon-license:MIT-0 | AI (license): MIT-0 is a well-known permissive license (no-attribution MIT); consistently used across the csstools package family. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 1 / 0 | |
| 3.0.0 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 1 | |
| 1.0.1 | 1 / 0 | |
| 1.0.0 | 1 / 0 |
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
2 findingsThis version was published by a different npm account than previous versions on 2023-12-15. 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.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.