@gjsify/lightningcss-native No license 5 versions

@gjsify/lightningcss-native

npm Repository Homepage

5

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jumplinkschanzewlsh

Keywords

gjslightningcsscssminifybrowserslistvalarustnative

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): Package is a native GJS binding; prebuilt .so files for multiple Linux architectures are the core deliverable.	ai	2026/05/29
phantom-deps	phantom-dep:@girs/gjs	AI (phantom-deps): @girs/* packages are GObject introspection type stubs used in config/tsconfig, not directly imported at runtime.	ai	2026/05/29
phantom-deps	phantom-dep:@girs/glib-2.0	AI (phantom-deps): @girs/* packages are GObject introspection type stubs used in config/tsconfig, not directly imported at runtime.	ai	2026/05/29
phantom-deps	phantom-dep:@girs/gobject-2.0	AI (phantom-deps): @girs/* packages are GObject introspection type stubs used in config/tsconfig, not directly imported at runtime.	ai	2026/05/29

Versions (showing 5 of 5)

Version	Deps	Published
0.4.28	3 / 4	2026-05-27
0.4.27	3 / 4	2026-05-26
0.4.26	3 / 4	2026-05-26
0.4.11	3 / 4	2026-05-18
0.4.5	3 / 4	2026-05-17

v0.4.28

2 findings

HIGH Bundled binary files (10) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsify_lightningcss.so • prebuilds/linux-aarch64/libgjsifylightningcss.so • prebuilds/linux-ppc64/libgjsify_lightningcss.so • prebuilds/linux-ppc64/libgjsifylightningcss.so • prebuilds/linux-riscv64/libgjsify_lightningcss.so • prebuilds/linux-riscv64/libgjsifylightningcss.so • prebuilds/linux-s390x/libgjsify_lightningcss.so • prebuilds/linux-s390x/libgjsifylightningcss.so • prebuilds/linux-x86_64/libgjsify_lightningcss.so • prebuilds/linux-x86_64/libgjsifylightningcss.so

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.27

2 findings

HIGH Bundled binary files (10) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsify_lightningcss.so • prebuilds/linux-aarch64/libgjsifylightningcss.so • prebuilds/linux-ppc64/libgjsify_lightningcss.so • prebuilds/linux-ppc64/libgjsifylightningcss.so • prebuilds/linux-riscv64/libgjsify_lightningcss.so • prebuilds/linux-riscv64/libgjsifylightningcss.so • prebuilds/linux-s390x/libgjsify_lightningcss.so • prebuilds/linux-s390x/libgjsifylightningcss.so • prebuilds/linux-x86_64/libgjsify_lightningcss.so • prebuilds/linux-x86_64/libgjsifylightningcss.so

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.26

2 findings

HIGH Bundled binary files (10) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsify_lightningcss.so • prebuilds/linux-aarch64/libgjsifylightningcss.so • prebuilds/linux-ppc64/libgjsify_lightningcss.so • prebuilds/linux-ppc64/libgjsifylightningcss.so • prebuilds/linux-riscv64/libgjsify_lightningcss.so • prebuilds/linux-riscv64/libgjsifylightningcss.so • prebuilds/linux-s390x/libgjsify_lightningcss.so • prebuilds/linux-s390x/libgjsifylightningcss.so • prebuilds/linux-x86_64/libgjsify_lightningcss.so • prebuilds/linux-x86_64/libgjsifylightningcss.so

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.11

2 findings

HIGH Bundled binary files (10) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsify_lightningcss.so • prebuilds/linux-aarch64/libgjsifylightningcss.so • prebuilds/linux-ppc64/libgjsify_lightningcss.so • prebuilds/linux-ppc64/libgjsifylightningcss.so • prebuilds/linux-riscv64/libgjsify_lightningcss.so • prebuilds/linux-riscv64/libgjsifylightningcss.so • prebuilds/linux-s390x/libgjsify_lightningcss.so • prebuilds/linux-s390x/libgjsifylightningcss.so • prebuilds/linux-x86_64/libgjsify_lightningcss.so • prebuilds/linux-x86_64/libgjsifylightningcss.so

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.4.5

2 findings

HIGH Bundled binary files (10) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsify_lightningcss.so • prebuilds/linux-ppc64/libgjsify_lightningcss.so • prebuilds/linux-riscv64/libgjsify_lightningcss.so • prebuilds/linux-s390x/libgjsify_lightningcss.so • prebuilds/linux-x86_64/libgjsify_lightningcss.so • prebuilds/linux-aarch64/libgjsifylightningcss.so • prebuilds/linux-ppc64/libgjsifylightningcss.so • prebuilds/linux-riscv64/libgjsifylightningcss.so • prebuilds/linux-s390x/libgjsifylightningcss.so • prebuilds/linux-x86_64/libgjsifylightningcss.so

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.