@gjsify/zlib
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/browser.js | AI (source-diff): Bundled browser polyfill (rolldown), long lines are minification not obfuscation. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publish (GitHub Actions) for monorepo package, not an account takeover indicator. | ai | |
| dependencies | unvetted-dep:@girs/gio-2.0 | AI (dependencies): Official GNOME typelib bindings used throughout gjsify ecosystem. | ai | |
| dependencies | unvetted-dep:@girs/glib-2.0 | AI (dependencies): Official GNOME typelib bindings used throughout gjsify ecosystem. | ai | |
| phantom-deps | phantom-dep:@girs/gio-2.0 | AI (phantom-deps): GJS type stubs referenced in config/types only; not directly imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): GJS type stubs referenced in config/types only; not directly imported at runtime by design. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @gjsify/zlib is a GJS zlib port, not a typo of glob; Levenshtein match is coincidental. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 3 / 5 | |
| 0.4.25 | 2 / 4 | |
| 0.4.4 | 2 / 4 | |
| 0.4.0 | 2 / 4 | |
| 0.3.20 | 2 / 4 | |
| 0.3.19 | 2 / 4 | |
| 0.3.18 | 2 / 4 | |
| 0.3.14 | 2 / 4 | |
| 0.3.13 | 2 / 4 | |
| 0.3.6 | 2 / 4 | |
| 0.3.5 | 2 / 4 | |
| 0.3.3 | 2 / 4 | |
| 0.2.0 | 2 / 4 | |
| 0.1.13 | 2 / 4 | |
| 0.1.12 | 2 / 4 | |
| 0.1.11 | 2 / 4 | |
| 0.1.8 | 2 / 4 | |
| 0.1.6 | 2 / 4 | |
| 0.1.4 | 2 / 4 | |
| 0.1.1 | 2 / 4 | |
| 0.1.0 | 2 / 4 |
v0.13.2
4 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.