@onekeyfe/hd-core ISC 36 versions

@onekeyfe/hd-core

npm Repository Homepage

Core processes and APIs for communicating with OneKey hardware devices.

36

Versions

ISC

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
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	2026/05/08
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding of transaction payloads is expected in a hardware wallet SDK; not a malicious pattern.	ai	2026/05/04
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	2026/05/04

Versions (showing 36 of 36)

Version	Deps	Published
1.1.26	8 / 5	2026-05-15
1.1.25	8 / 5	2026-04-09
1.1.24	8 / 5	2026-03-05
1.1.23	8 / 5	2026-02-11
1.1.22	8 / 5	2026-01-20
1.1.21	8 / 5	2025-12-24
1.1.20	8 / 5	2025-12-19
1.1.19	8 / 5	2025-12-01
1.1.18	8 / 6	2025-11-21
1.1.17	8 / 6	2025-11-11
1.1.16	8 / 6	2025-10-29
1.1.15	8 / 6	2025-10-10
1.1.14	8 / 6	2025-09-26
1.1.13	8 / 6	2025-09-17
1.1.12	8 / 6	2025-09-12
1.1.11	8 / 6	2025-08-29
1.1.10	8 / 6	2025-08-28
1.1.9	8 / 6	2025-08-18
1.1.8	8 / 6	2025-08-17
1.1.7	8 / 6	2025-08-14
1.1.6	8 / 6	2025-08-14
1.1.5	8 / 6	2025-08-12
1.1.3	8 / 6	2025-08-05
1.1.2	8 / 6	2025-08-04
1.1.1	8 / 6	2025-07-29
1.1.0	8 / 6	2025-07-24
1.0.37	8 / 6	2025-06-27
1.0.36	8 / 6	2025-06-26
1.0.35	8 / 6	2025-06-25
1.0.34	8 / 6	2025-06-24
1.0.33	8 / 6	2025-06-24
1.0.32	8 / 6	2025-06-06
1.0.31	8 / 6	2025-05-28
1.0.30	8 / 6	2025-05-26
1.0.29	8 / 6	2025-05-21
1.0.28	8 / 6	2025-05-16

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

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.24

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.23

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.22

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.21

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.20

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.19

2 findings

HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 52 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.18

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.

v1.1.17

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.

v1.1.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.33

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.

v1.0.32

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.

v1.0.31

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.

v1.0.30

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.

v1.0.29

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.

v1.0.28

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.