← Home

@gjsify/http

npm Repository Homepage
2
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jumplinkschanzewlsh

Keywords

gjsnodehttp

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@gjsify/url AI (phantom-deps): Same-org sibling package; likely used transitively or via re-export pattern in this GJS module ecosystem. ai
phantom-deps phantom-dep:@gjsify/buffer AI (phantom-deps): Same-org sibling package; likely used transitively or via re-export pattern in this GJS module ecosystem. ai
phantom-deps phantom-dep:@gjsify/events AI (phantom-deps): Same-org sibling package; likely used transitively or via re-export pattern in this GJS module ecosystem. ai
phantom-deps phantom-dep:@gjsify/stream AI (phantom-deps): Same-org sibling package; likely used transitively or via re-export pattern in this GJS module ecosystem. ai
semgrep semgrep:shady-links-raw-ip AI (semgrep): All raw-IP hits are in test spec files using 127.0.0.1 for localhost server testing — standard unit test pattern. ai

Versions (showing 2 of 2)

Version Deps Published
0.3.20 10 / 4
0.1.0 9 / 4

v0.3.20

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.