@gjsify/bridge-types
Shared interfaces and environment classes for GTK-DOM bridge containers
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@girs/glib-2.0 | AI (dependencies): Standard GLib 2.0 introspection type-def package; stable dependency for this GTK bridge library. | ai | |
| dependencies | unvetted-dep:@girs/gjs | AI (dependencies): Standard GJS introspection type-def package; stable dependency for this GTK bridge library. | ai | |
| dependencies | unvetted-dep:@girs/gdk-4.0 | AI (dependencies): Standard GDK 4.0 introspection type-def package; stable dependency for this GTK bridge library. | ai | |
| dependencies | unvetted-dep:@girs/gtk-4.0 | AI (dependencies): Standard GTK 4.0 introspection type-def package; stable dependency for this GTK bridge library. | ai | |
| phantom-deps | phantom-dep:@girs/gjs | AI (phantom-deps): Type-only dep referenced in tsconfig config files, not runtime imports; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gdk-4.0 | AI (phantom-deps): Type-only dep referenced in tsconfig config files, not runtime imports; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gtk-4.0 | AI (phantom-deps): Type-only dep referenced in tsconfig config files, not runtime imports; stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): Type-only dep referenced in tsconfig config files, not runtime imports; stable FP for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 0.3.21 | 6 / 3 | |
| 0.3.20 | 6 / 3 | |
| 0.3.19 | 6 / 3 | |
| 0.3.18 | 6 / 3 |
v0.3.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.