@gjsify/http2-native
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 | bundled-binaries | AI (npm-metadata): Package is a documented native binding shipping prebuilt .so files for multiple Linux architectures; consistent with its stated purpose. | ai | |
| phantom-deps | phantom-dep:@girs/gjs | AI (phantom-deps): GObject introspection type stub; referenced in config/types only, not runtime import. Expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): GObject introspection type stub; referenced in config/types only. Expected pattern for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gobject-2.0 | AI (phantom-deps): GObject introspection type stub; referenced in config/types only. Expected pattern for this package. | ai |
v0.4.26
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsifyhttp2.so • prebuilds/linux-ppc64/libgjsifyhttp2.so • prebuilds/linux-riscv64/libgjsifyhttp2.so • prebuilds/linux-s390x/libgjsifyhttp2.so • prebuilds/linux-x86_64/libgjsifyhttp2.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.14
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsifyhttp2.so • prebuilds/linux-ppc64/libgjsifyhttp2.so • prebuilds/linux-riscv64/libgjsifyhttp2.so • prebuilds/linux-s390x/libgjsifyhttp2.so • prebuilds/linux-x86_64/libgjsifyhttp2.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.11
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-aarch64/libgjsifyhttp2.so • prebuilds/linux-ppc64/libgjsifyhttp2.so • prebuilds/linux-riscv64/libgjsifyhttp2.so • prebuilds/linux-s390x/libgjsifyhttp2.so • prebuilds/linux-x86_64/libgjsifyhttp2.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.