units-css
Parse length and angle CSS values and convert between units
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Package is 3889 days old with 152k weekly downloads; the 0.0.0 version label is a metadata artifact, not a malware indicator. Clearly a legitimate long-lived package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): 152k weekly downloads and ecosystem adoption confirm this is not a spam/low-value package despite minor README and keyword gaps. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 2 / 23 | |
| 0.3.0 | 2 / 23 | |
| 0.2.0 | 2 / 23 | |
| 0.1.0 | 2 / 24 | |
| 0.0.0 | 2 / 24 |
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.