@gjsify/utils
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition to GitHub Actions CI publisher is consistent with legitimate automation; no code/dep changes accompany the switch. | ai | |
| dependencies | unvetted-dep:@girs/gjs | AI (dependencies): GObject introspection type stub; expected dependency for gjsify ecosystem packages. | ai | |
| dependencies | unvetted-dep:@girs/gio-2.0 | AI (dependencies): GObject introspection type stub; expected dependency for gjsify ecosystem packages. | ai | |
| dependencies | unvetted-dep:@girs/giounix-2.0 | AI (dependencies): GObject introspection type stub; expected dependency for gjsify ecosystem packages. | ai | |
| phantom-deps | phantom-dep:@girs/giounix-2.0 | AI (phantom-deps): Type-only dependency; not directly imported at runtime by design. | ai | |
| dependencies | unvetted-dep:@girs/glib-2.0 | AI (dependencies): GObject introspection type stub; expected dependency for gjsify ecosystem packages. | ai | |
| phantom-deps | phantom-dep:@girs/gjs | AI (phantom-deps): @girs/gjs is a type-only GJS binding; referenced in config but not directly imported is expected for this package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.4.21 | 4 / 2 | |
| 0.4.11 | 4 / 2 | |
| 0.4.3 | 4 / 2 | |
| 0.4.0 | 4 / 2 | |
| 0.3.21 | 4 / 2 | |
| 0.3.20 | 4 / 2 | |
| 0.3.19 | 4 / 2 | |
| 0.3.18 | 4 / 2 | |
| 0.3.14 | 4 / 2 | |
| 0.3.11 | 4 / 2 | |
| 0.3.10 | 4 / 2 | |
| 0.3.7 | 4 / 2 | |
| 0.3.6 | 4 / 2 | |
| 0.3.4 | 4 / 2 | |
| 0.3.2 | 4 / 2 | |
| 0.3.0 | 4 / 2 | |
| 0.1.15 | 4 / 2 | |
| 0.1.12 | 4 / 2 | |
| 0.1.11 | 4 / 2 | |
| 0.1.7 | 4 / 2 | |
| 0.1.6 | 4 / 2 | |
| 0.1.3 | 4 / 2 | |
| 0.1.2 | 4 / 2 | |
| 0.1.1 | 4 / 2 |
v0.4.21
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.21
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.3.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.11
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.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
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.