@onekeyfe/hardware-cli
OneKey hardware wallet CLI for AI agent integration
2
Versions
Apache-2.0
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
1keyfe
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Buffer.from(hex, 'hex') in secure-storage.linux.ts is standard hex decoding of keychain output, not payload obfuscation. | ai | |
| phantom-deps | phantom-dep:@onekeyfe/hd-transport-usb | AI (phantom-deps): Same-org dependency; likely used transitively or conditionally in CLI context. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Declared as dep, likely used transitively or in bundled output; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eventemitter2 | AI (phantom-deps): Same pattern — declared dep used via bundled/transitive path; stable false positive. | ai | |
| phantom-deps | phantom-dep:@onekeyfe/hd-shared | AI (phantom-deps): Same-org dep; likely re-exported or used indirectly in build output. | ai |
v1.1.26
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.25
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.