@gjsify/crypto
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:@gjsify/utils | AI (phantom-deps): Same org scope; likely re-exported or used indirectly via build tooling, consistent with sibling packages. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): Referenced in config files per finding; not a direct import but a legitimate transitive/type dependency. | ai | |
| dependencies | unvetted-dep:@girs/glib-2.0 | AI (dependencies): @girs/glib-2.0 is a GLib type binding, appropriate for a GJS-targeted crypto polyfill. | ai | |
| phantom-deps | phantom-dep:@gjsify/buffer | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a false positive for this package. | ai | |
| typosquat | typosquat.levenshtein:bcrypt | AI (typosquat): Scoped @gjsify/crypto is a GJS crypto polyfill, not a typosquat of bcrypt. | ai | |
| phantom-deps | phantom-dep:@gjsify/stream | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic is a false positive for this package. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): PEM/DER parsing in a crypto library legitimately uses base64 decoding; not a malicious payload. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding in cipher test vectors is expected in a crypto library; not obfuscation. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.4.11 | 4 / 5 | |
| 0.4.0 | 4 / 5 | |
| 0.3.20 | 4 / 5 | |
| 0.1.7 | 4 / 5 | |
| 0.1.1 | 4 / 5 | |
| 0.1.0 | 4 / 5 |
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.1.7
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.