← Home

@gjsify/sab-native

2
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

gjsshared-memoryshared-array-bufferatomicsmemfdmmapfutexworker-threadsvalanative

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata bundled-binaries AI (npm-metadata): Prebuilt .so files are documented native bindings for a GJS/Vala shared-memory library; consistent with package purpose. ai
phantom-deps phantom-dep:@girs/gjs AI (phantom-deps): @girs/* packages are GObject introspection TypeScript type stubs; used in config/types, not runtime imports. ai
phantom-deps phantom-dep:@girs/gio-2.0 AI (phantom-deps): @girs/* packages are GObject introspection TypeScript type stubs; used in config/types, not runtime imports. ai
phantom-deps phantom-dep:@girs/glib-2.0 AI (phantom-deps): @girs/* packages are GObject introspection TypeScript type stubs; used in config/types, not runtime imports. ai
phantom-deps phantom-dep:@girs/gobject-2.0 AI (phantom-deps): @girs/* packages are GObject introspection TypeScript type stubs; used in config/types, not runtime imports. ai

Versions (showing 2 of 2)

Version Deps Published
0.4.21 4 / 5
0.4.14 4 / 5

v0.4.21

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsifysabnative.so • prebuilds/linux-ppc64/libgjsifysabnative.so • prebuilds/linux-riscv64/libgjsifysabnative.so • prebuilds/linux-s390x/libgjsifysabnative.so • prebuilds/linux-x86_64/libgjsifysabnative.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.14

2 findings
HIGH Bundled binary files (5) npm-metadata

Package contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsifysabnative.so • prebuilds/linux-ppc64/libgjsifysabnative.so • prebuilds/linux-riscv64/libgjsifysabnative.so • prebuilds/linux-s390x/libgjsifysabnative.so • prebuilds/linux-x86_64/libgjsifysabnative.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.