← Home

@gjsify/net

npm Repository Homepage
14
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

gjsnodenet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@gjsify/utils AI (phantom-deps): Same org scope; likely re-exported or used indirectly via peer packages, consistent with gjsify modular architecture. ai
phantom-deps phantom-dep:@girs/glib-2.0 AI (phantom-deps): GLib type bindings referenced in config/tsconfig; not directly imported in source is expected for type-only deps. ai
provenance no-provenance AI (provenance): Consistent across all versions of this package; no other risk signals present. ai
typosquat typosquat.levenshtein:got AI (typosquat): Coincidental edit-distance match; unrelated GJS ecosystem package. ai
typosquat typosquat.levenshtein:knex AI (typosquat): Coincidental edit-distance match; unrelated GJS ecosystem package. ai
typosquat typosquat.levenshtein:next AI (typosquat): @gjsify/net is a GJS net module polyfill, not a typosquat of 'next'; scoped package with 47 versions. ai
phantom-deps phantom-dep:@gjsify/events AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via peer modules. ai
phantom-deps phantom-dep:@gjsify/stream AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via peer modules. ai
phantom-deps phantom-dep:@gjsify/buffer AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly via peer modules. ai
typosquat typosquat.levenshtein:nuxt AI (typosquat): Same as above; edit-distance match is coincidental for this GJS net module. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Coincidental edit-distance match; unrelated GJS ecosystem package. ai

Versions (showing 14 of 14)

Version Deps Published
0.4.13 6 / 4
0.4.0 6 / 4
0.3.21 6 / 4
0.3.20 6 / 4
0.3.19 6 / 4
0.3.15 6 / 4
0.3.14 6 / 4
0.3.7 6 / 4
0.3.1 6 / 4
0.2.0 6 / 4
0.1.13 6 / 4
0.1.6 6 / 4
0.1.5 6 / 4
0.1.4 6 / 4

v0.4.13

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.4.0

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@gjsify/net' is 1 edit(s) away from popular package 'next'.

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.3.21

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@gjsify/net' is 1 edit(s) away from popular package 'next'.

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.3.20

2 findings
HIGH typosquat.levenshtein: Possible typosquat of 'next' typosquat

Package name '@gjsify/net' is 1 edit(s) away from popular package 'next'.

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.3.19

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.3.15

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.3.14

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.3.7

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.3.1

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.2.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.

v0.1.13

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.6

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.5

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.4

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.