@parcel/css
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): These are NAPI-RS prebuilt Rust native addons for each platform/arch — the standard distribution pattern for this package. Not backdoors. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @parcel/css is a scoped package in the well-known @parcel namespace; levenshtein match to 'cors' is a false positive. | ai | |
| typosquat | typosquat.levenshtein:qs | AI (typosquat): @parcel/css is a scoped package in the well-known @parcel namespace; levenshtein match to 'qs' is a false positive. | ai | |
| phantom-deps | phantom-dep:@parcel/css-linux-x64-musl | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-win32-x64-msvc | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-linux-arm64-gnu | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-darwin-x64 | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-linux-arm-gnueabihf | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require constructs platform-specific NAPI-RS binary package names. Input is derived from os/arch/libc detection, not user input. Stable false positive for this package. | ai | |
| dependencies | unvetted-dep:detect-libc | AI (dependencies): detect-libc is a well-known utility used to distinguish GNU vs musl Linux for native binary selection. Standard usage in NAPI-RS packages. | ai | |
| phantom-deps | phantom-dep:@parcel/css-linux-arm64-musl | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-darwin-arm64 | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai | |
| phantom-deps | phantom-dep:@parcel/css-linux-x64-gnu | AI (phantom-deps): Standard NAPI-RS pattern: platform-specific native binaries listed as optionalDependencies, loaded dynamically at runtime. Same org scope, legitimate pattern. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 1.14.0 | 1 / 0 | |
| 1.13.1 | 9 / 11 | |
| 1.13.0 | 9 / 11 | |
| 1.12.2 | 9 / 11 | |
| 1.12.1 | 9 / 11 | |
| 1.12.0 | 9 / 11 | |
| 1.11.2 | 9 / 11 | |
| 1.11.1 | 9 / 11 | |
| 1.11.0 | 9 / 11 | |
| 1.10.1 | 9 / 11 | |
| 1.10.0 | 9 / 11 | |
| 1.9.0 | 9 / 11 | |
| 1.8.3 | 9 / 11 | |
| 1.8.2 | 9 / 11 | |
| 1.8.1 | 9 / 11 | |
| 1.8.0 | 9 / 11 | |
| 1.7.4 | 9 / 11 | |
| 1.7.3 | 9 / 11 | |
| 1.7.2 | 9 / 11 | |
| 1.7.1 | 9 / 11 | |
| 1.7.0 | 9 / 11 | |
| 1.6.0 | 9 / 11 | |
| 1.5.0 | 9 / 11 | |
| 1.4.0 | 9 / 11 | |
| 1.3.2 | 9 / 11 | |
| 1.3.1 | 9 / 11 | |
| 1.3.0 | 9 / 11 | |
| 1.2.0 | 9 / 11 | |
| 1.1.0 | 9 / 11 | |
| 1.0.3 | 9 / 11 | |
| 1.0.2 | 9 / 11 | |
| 1.0.1 | 9 / 11 | |
| 1.0.0 | 1 / 11 |
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
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
2 findingsPackage contains compiled binaries that could be backdoors: • parcel-css.darwin-arm64.node • parcel-css.darwin-x64.node • parcel-css.linux-arm-gnueabihf.node • parcel-css.linux-arm64-gnu.node • parcel-css.linux-arm64-musl.node • parcel-css.linux-x64-gnu.node • parcel-css.linux-x64-musl.node • parcel-css.win32-x64-msvc.node
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.