@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 — 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 |
|---|---|---|---|---|
| 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 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 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.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.