lightningcss-linux-arm64-musl
A CSS parser, transformer, and minifier written in Rust
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): This package's sole purpose is to distribute a compiled Rust native addon (.node file) for lightningcss on Linux ARM64 musl. Bundled binary is expected and legitimate for this platform-specific sub-package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary sub-packages intentionally have minimal READMEs, no keywords, and no deps — these are not standalone packages but native addon carriers for the main lightningcss package. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 1.32.0 | 0 / 0 | |
| 1.31.1 | 0 / 0 | |
| 1.31.0 | 0 / 0 | |
| 1.30.2 | 0 / 0 | |
| 1.30.1 | 0 / 0 | |
| 1.30.0 | 0 / 0 | |
| 1.29.3 | 0 / 0 | |
| 1.29.2 | 0 / 0 | |
| 1.29.1 | 0 / 0 | |
| 1.29.0 | 0 / 0 | |
| 1.28.2 | 0 / 0 | |
| 1.28.1 | 0 / 0 | |
| 1.28.0 | 0 / 0 | |
| 1.27.0 | 0 / 0 | |
| 1.26.0 | 0 / 0 | |
| 1.25.1 | 0 / 0 | |
| 1.25.0 | 0 / 0 | |
| 1.24.1 | 0 / 0 | |
| 1.24.0 | 0 / 0 | |
| 1.23.0 | 0 / 0 | |
| 1.22.1 | 0 / 0 | |
| 1.22.0 | 0 / 0 | |
| 1.21.8 | 0 / 0 | |
| 1.21.7 | 0 / 0 | |
| 1.21.6 | 0 / 0 | |
| 1.21.5 | 0 / 0 | |
| 1.21.4 | 0 / 0 | |
| 1.21.3 | 0 / 0 | |
| 1.21.2 | 0 / 0 | |
| 1.21.1 | 0 / 0 | |
| 1.21.0 | 0 / 0 | |
| 1.20.0 | 0 / 0 | |
| 1.19.0 | 0 / 0 | |
| 1.18.0 | 0 / 0 | |
| 1.17.1 | 0 / 0 | |
| 1.17.0 | 0 / 0 | |
| 1.16.1 | 0 / 0 | |
| 1.16.0 | 0 / 0 | |
| 1.15.1 | 0 / 0 | |
| 1.15.0 | 0 / 0 | |
| 1.14.0 | 0 / 0 |
v1.32.0
2 findingsPackage contains compiled binaries that could be backdoors: • lightningcss.linux-arm64-musl.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
2 findingsPackage contains compiled binaries that could be backdoors: • lightningcss.linux-arm64-musl.node
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.