@gjsify/terminal-native
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 |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): libgjsifyterminal.so is the documented Vala/GObject native bridge; meson build source is included in the package. | ai | |
| phantom-deps | phantom-dep:@girs/glib-2.0 | AI (phantom-deps): GIR type-definition package; referenced in config, not directly imported in JS — stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@girs/gobject-2.0 | AI (phantom-deps): GIR type-definition package; referenced in config, not directly imported in JS — stable false positive for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.11 | 2 / 4 | |
| 0.4.5 | 2 / 4 | |
| 0.4.0 | 2 / 4 | |
| 0.3.21 | 2 / 4 | |
| 0.3.20 | 2 / 4 | |
| 0.3.17 | 2 / 4 | |
| 0.3.9 | 2 / 4 | |
| 0.3.7 | 2 / 4 | |
| 0.3.0 | 2 / 4 |
v0.4.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: jumplink.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.21
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.20
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.17
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.9
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.7
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
2 findingsPackage contains compiled binaries that could be backdoors: • prebuilds/linux-x86_64/libgjsifyterminal.so
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.