@gjsify/xmlhttprequest
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@girs/gjs | AI (phantom-deps): GJS type binding used in tsconfig/types only; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@girs/gio-2.0 | AI (phantom-deps): GJS type binding used in tsconfig/types only; not directly imported at runtime. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): GJS type binding used in tsconfig/types only; not directly imported at runtime. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 0.4.0 | 4 / 3 | |
| 0.3.20 | 4 / 3 | |
| 0.3.3 | 4 / 3 | |
| 0.3.1 | 4 / 3 | |
| 0.1.10 | 3 / 3 |
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.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.