@gjsify/fs — Greenflagged

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

gjsnodefs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@girs/gio-2.0	AI (dependencies): Standard GObject introspection binding; expected dependency for any GJS package.	ai	2026/05/24
dependencies	unvetted-dep:@girs/glib-2.0	AI (dependencies): Standard GObject introspection binding; expected dependency for any GJS package.	ai	2026/05/24
phantom-deps	phantom-dep:@gjsify/url	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly in the GJS module system.	ai	2026/05/18
phantom-deps	phantom-dep:@gjsify/buffer	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly in the GJS module system.	ai	2026/05/18
typosquat	typosquat.levenshtein:qs	AI (typosquat): Scoped GJS ecosystem package; no relation to 'qs'. Levenshtein match is coincidental.	ai	2026/05/18
phantom-deps	phantom-dep:@gjsify/stream	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly in the GJS module system.	ai	2026/05/18
phantom-deps	phantom-dep:@gjsify/events	AI (phantom-deps): Same-org dependency; likely re-exported or used indirectly in the GJS module system.	ai	2026/05/18
typosquat	typosquat.levenshtein:pg	AI (typosquat): Scoped GJS ecosystem package; no relation to 'pg'. Levenshtein match is coincidental.	ai	2026/05/18

Versions (showing 2 of 2)

Version	Deps	Published
0.3.20	7 / 4	2026-05-08
0.3.9	7 / 4	2026-05-05

v0.3.20

2 findings

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

Package name '@gjsify/fs' 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

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.