@onekeyfe/hd-core
Core processes and APIs for communicating with OneKey hardware devices.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Long hex strings are device bitmap/icon data embedded in a hardware wallet SDK — not obfuscated payloads. | ai | |
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding of transaction payloads is expected in a hardware wallet SDK; not a malicious pattern. | ai | |
| phantom-deps | phantom-dep:parse-uri | AI (phantom-deps): parse-uri is declared in dependencies and devDependencies; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 66 of 66)
| Version | Deps | Published |
|---|---|---|
| 1.1.32 | 8 / 5 | |
| 1.1.31 | 8 / 5 | |
| 1.1.30 | 8 / 5 | |
| 1.1.29 | 8 / 5 | |
| 1.1.28 | 8 / 5 | |
| 1.1.27 | 8 / 5 | |
| 1.1.26 | 8 / 5 | |
| 1.1.25 | 8 / 5 | |
| 1.1.24 | 8 / 5 | |
| 1.1.23 | 8 / 5 | |
| 1.1.22 | 8 / 5 | |
| 1.1.21 | 8 / 5 | |
| 1.1.20 | 8 / 5 | |
| 1.1.19 | 8 / 5 | |
| 1.1.18 | 8 / 6 | |
| 1.1.17 | 8 / 6 | |
| 1.1.16 | 8 / 6 | |
| 1.1.15 | 8 / 6 | |
| 1.1.14 | 8 / 6 | |
| 1.1.13 | 8 / 6 | |
| 1.1.12 | 8 / 6 | |
| 1.1.11 | 8 / 6 | |
| 1.1.10 | 8 / 6 | |
| 1.1.9 | 8 / 6 | |
| 1.1.8 | 8 / 6 | |
| 1.1.7 | 8 / 6 | |
| 1.1.6 | 8 / 6 | |
| 1.1.5 | 8 / 6 | |
| 1.1.3 | 8 / 6 | |
| 1.1.2 | 8 / 6 | |
| 1.1.1 | 8 / 6 | |
| 1.1.0 | 8 / 6 | |
| 1.0.37 | 8 / 6 | |
| 1.0.36 | 8 / 6 | |
| 1.0.35 | 8 / 6 | |
| 1.0.34 | 8 / 6 | |
| 1.0.33 | 8 / 6 | |
| 1.0.32 | 8 / 6 | |
| 1.0.31 | 8 / 6 | |
| 1.0.30 | 8 / 6 | |
| 1.0.29 | 8 / 6 | |
| 1.0.28 | 8 / 6 | |
| 1.0.26 | 8 / 6 | |
| 1.0.25 | 8 / 6 | |
| 1.0.24 | 8 / 6 | |
| 1.0.23 | 8 / 6 | |
| 1.0.22 | 8 / 6 | |
| 1.0.21 | 8 / 4 | |
| 1.0.20 | 8 / 4 | |
| 1.0.19 | 8 / 4 | |
| 1.0.18 | 8 / 4 | |
| 1.0.17 | 8 / 4 | |
| 1.0.16 | 8 / 4 | |
| 1.0.15 | 8 / 4 | |
| 1.0.14 | 8 / 4 | |
| 1.0.13 | 8 / 4 | |
| 1.0.9 | 8 / 4 | |
| 1.0.8 | 8 / 4 | |
| 1.0.7 | 8 / 4 | |
| 1.0.6 | 8 / 4 | |
| 1.0.5 | 8 / 4 | |
| 1.0.4 | 8 / 4 | |
| 1.0.3 | 8 / 4 | |
| 1.0.2 | 8 / 4 | |
| 1.0.1 | 8 / 4 | |
| 1.0.0 | 8 / 4 |
v1.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.