@gjsify/event-bridge
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:@gjsify/dom-events | AI (phantom-deps): Same-org sibling package; likely used as a transitive/runtime dep rather than directly imported in source. | ai | |
| phantom-deps | phantom-dep:@girs/gjs | AI (phantom-deps): Type-binding dep referenced in tsconfig/config only; not directly imported at runtime — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gdk-4.0 | AI (phantom-deps): Same pattern: config-only type reference for GTK binding. | ai | |
| phantom-deps | phantom-dep:@girs/gtk-4.0 | AI (phantom-deps): Same pattern: config-only type reference for GTK binding. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): Same pattern: config-only type reference for GLib binding. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.4.14 | 5 / 4 | |
| 0.4.12 | 5 / 4 | |
| 0.4.11 | 5 / 4 | |
| 0.4.10 | 5 / 4 | |
| 0.4.0 | 5 / 4 | |
| 0.3.20 | 5 / 4 | |
| 0.3.15 | 5 / 4 | |
| 0.3.13 | 5 / 4 | |
| 0.3.8 | 5 / 4 | |
| 0.3.2 | 5 / 4 | |
| 0.3.0 | 5 / 4 | |
| 0.2.0 | 5 / 4 | |
| 0.1.10 | 5 / 3 | |
| 0.1.9 | 5 / 3 | |
| 0.1.7 | 5 / 3 | |
| 0.1.6 | 5 / 3 |
v0.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.12
1 findingPackage 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.10
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.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.8
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.2.0
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.
v0.1.9
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.