@gjsify/os No license 17 versions

@gjsify/os

npm Repository Homepage

17

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

gjsnodeos

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 bindings are referenced in tsconfig/build config rather than direct imports; stable pattern for this ecosystem.	ai	2026/05/28
phantom-deps	phantom-dep:@gjsify/utils	AI (phantom-deps): Same-org utility dep; phantom-dep heuristic is a false positive here.	ai	2026/05/28
phantom-deps	phantom-dep:@girs/glib-2.0	AI (phantom-deps): GJS type bindings referenced in config; stable false positive for this package.	ai	2026/05/28
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped GJS ecosystem package; no relation to 'pg'.	ai	2026/05/18
typosquat	typosquat.levenshtein:cors	AI (typosquat): Scoped GJS ecosystem package; no relation to 'cors'.	ai	2026/05/18
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped GJS ecosystem package; name collision with 'qs' is purely coincidental edit-distance artifact.	ai	2026/05/18
typosquat	typosquat.levenshtein:zod	AI (typosquat): Scoped GJS ecosystem package; no relation to 'zod'.	ai	2026/05/18
typosquat	typosquat.levenshtein:joi	AI (typosquat): Scoped GJS ecosystem package; no relation to 'joi'.	ai	2026/05/18
typosquat	typosquat.levenshtein:koa	AI (typosquat): Scoped GJS ecosystem package; no relation to 'koa'.	ai	2026/05/18
typosquat	typosquat.levenshtein:got	AI (typosquat): Scoped GJS ecosystem package; no relation to 'got'.	ai	2026/05/18

Versions (showing 17 of 17)

Version	Deps	Published
0.4.5	3 / 4	2026-05-17
0.4.0	3 / 4	2026-05-13
0.3.20	3 / 4	2026-05-08
0.3.18	3 / 4	2026-05-08
0.3.15	3 / 4	2026-05-07
0.3.11	3 / 4	2026-05-06
0.3.9	3 / 4	2026-05-05
0.3.8	3 / 4	2026-05-05
0.3.6	3 / 4	2026-05-05
0.3.5	3 / 4	2026-05-05
0.3.3	3 / 4	2026-05-04
0.1.15	3 / 4	2026-04-17
0.1.11	3 / 4	2026-04-15
0.1.8	3 / 4	2026-04-08
0.1.4	3 / 4	2026-04-03
0.1.1	3 / 4	2026-03-28
0.1.0	3 / 4	2026-03-28

v0.4.5

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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

2 findings

HIGH typosquat.levenshtein: Possible typosquat of 'qs' typosquat

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

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.