@js-eyes/native-host
JS Eyes browser native messaging host and cross-platform installer
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): tryRequire is a safe optional-module loader; not arbitrary code execution. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): execFileSync in installer.js is expected for a native messaging host installer. | ai | |
| phantom-deps | phantom-dep:@js-eyes/config | AI (phantom-deps): Same-org sibling dep; may be used indirectly via dynamic require pattern. | ai | |
| phantom-deps | phantom-dep:@js-eyes/protocol | AI (phantom-deps): Same-org sibling dep; may be used indirectly via dynamic require pattern. | ai | |
| phantom-deps | phantom-dep:@js-eyes/runtime-paths | AI (phantom-deps): Same-org sibling dep; may be used indirectly via dynamic require pattern. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 2.7.0 | 3 / 0 | |
| 2.6.2 | 3 / 0 | |
| 2.6.1 | 3 / 0 | |
| 2.6.0 | 3 / 0 | |
| 2.5.0 | 3 / 0 | |
| 2.4.0 | 3 / 0 |
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.