@gjsify/http2
Node.js http2 module for Gjs
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/esm/native-client-dispatcher.js | AI (source-diff): Rolldown-bundled ESM output; readable HTTP/2 client logic with GJS GLib/Gio imports, no obfuscation or hostile behavior. | ai | |
| source-diff | obfuscated-file:lib/esm/native-dispatcher.js | AI (source-diff): Rolldown-bundled ESM output; readable HTTP/2 server dispatcher logic, no obfuscation or hostile behavior. | ai | |
| source-diff | obfuscated-file:lib/esm/server/http2-server.js | AI (source-diff): Rolldown-bundled ESM output; readable HTTP/2 server implementation, no obfuscation or hostile behavior. | ai | |
| phantom-deps | phantom-dep:@gjsify/events | AI (phantom-deps): Same-org scope dep; likely re-exported or used indirectly in the GJS module pattern. | ai | |
| phantom-deps | phantom-dep:@girs/gobject-2.0 | AI (phantom-deps): GObject type bindings are commonly referenced in config/type files rather than direct imports. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 7 / 4 | |
| 0.2.0 | 6 / 4 | |
| 0.1.15 | 1 / 4 | |
| 0.1.13 | 1 / 4 | |
| 0.1.12 | 1 / 4 | |
| 0.1.11 | 1 / 4 | |
| 0.1.10 | 1 / 4 | |
| 0.1.9 | 1 / 4 | |
| 0.1.8 | 1 / 4 | |
| 0.1.7 | 1 / 4 | |
| 0.1.6 | 1 / 4 | |
| 0.1.5 | 1 / 4 | |
| 0.1.4 | 1 / 4 | |
| 0.1.3 | 1 / 4 | |
| 0.1.2 | 1 / 4 | |
| 0.1.1 | 1 / 4 | |
| 0.1.0 | 1 / 4 |
v0.13.2
5 findingsThis version was published by a different npm account than previous versions on 2026-06-29. This could indicate a legitimate maintainer transition or an account compromise.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.