@ledgerhq/hw-app-vet No license 42 versions

@ledgerhq/hw-app-vet

npm Repository Homepage

Ledger Hardware Wallet VeChain Application API

42

Versions

—

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

phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser

Keywords

LedgerLedgerWalletVeChainvetvthoVeThorNanoSHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:thor-devkit	AI (phantom-deps): thor-devkit is a legitimate VeChain SDK dependency; phantom-dep heuristic fires because it's used in build/config rather than direct import.	ai	2026/05/18
semgrep	semgrep:hex-decode	AI (semgrep): Buffer.from(rawHex, 'hex') is standard hex decoding for hardware wallet BIP32 path parsing — not obfuscated, not malicious, stable pattern for this package.	ai	2026/04/25
phantom-deps	phantom-dep:@ledgerhq/logs	AI (phantom-deps): Monorepo sibling package; phantom-dep finding is an artifact of workspace resolution, not a real risk for this org-scoped package.	ai	2026/04/25
phantom-deps	phantom-dep:@ledgerhq/cryptoassets	AI (phantom-deps): Monorepo sibling package; phantom-dep finding is an artifact of workspace resolution, not a real risk for this org-scoped package.	ai	2026/04/25
phantom-deps	phantom-dep:@ledgerhq/hw-transport-mocker	AI (phantom-deps): Declared in both deps and devDeps in a monorepo context; phantom-dep is a packaging quirk, not a security concern.	ai	2026/04/25
phantom-deps	phantom-dep:@vechain/sdk-core	AI (phantom-deps): Referenced in config files as expected for a VeChain integration package; not a security concern.	ai	2026/04/25

Versions (showing 42 of 42)

Version	Deps	Published
0.12.6	6 / 9	2026-06-05
0.12.5	6 / 9	2026-05-28
0.12.4	6 / 9	2026-05-21
0.12.3	6 / 9	2026-05-06
0.12.2	6 / 9	2026-05-04
0.12.1	6 / 9	2026-04-22
0.12.0	6 / 9	2026-04-15
0.11.2	6 / 9	2026-04-01
0.11.1	6 / 9	2026-03-26
0.11.0	6 / 9	2026-03-18
0.10.0	6 / 9	2026-03-12
0.9.6	6 / 9	2026-03-03
0.9.5	6 / 9	2026-02-25
0.9.4	6 / 9	2026-02-17
0.9.3	6 / 9	2026-02-10
0.9.2	6 / 9	2026-01-30
0.9.1	6 / 9	2026-01-26
0.9.0	6 / 9	2026-01-19
0.8.4	6 / 8	2026-01-13
0.8.3	6 / 8	2025-12-31
0.8.2	6 / 8	2025-12-29
0.8.1	6 / 8	2025-12-17
0.8.0	6 / 8	2025-12-08
0.7.0	5 / 8	2025-11-05
0.6.2	6 / 8	2025-10-16
0.6.1	6 / 8	2025-10-01
0.6.0	6 / 8	2025-09-25
0.5.16	6 / 8	2025-09-16
0.5.15	6 / 8	2025-09-05
0.5.14	6 / 8	2025-08-27
0.5.13	6 / 8	2025-08-18
0.5.12	6 / 8	2025-08-08
0.5.11	6 / 8	2025-07-31
0.5.10	6 / 8	2025-07-23
0.5.9	6 / 8	2025-07-07
0.5.8	6 / 8	2025-06-27
0.5.7	6 / 8	2025-06-20
0.5.6	6 / 8	2025-06-17
0.5.5	6 / 9	2025-06-06
0.5.4	6 / 9	2025-05-27
0.5.3	6 / 9	2025-05-20
0.5.2	6 / 9	2025-04-30

v0.12.6

1 finding

LOW No provenance attestation provenance

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

v0.12.5

1 finding

LOW No provenance attestation provenance

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

v0.12.4

1 finding

LOW No provenance attestation provenance

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

v0.12.3

1 finding

LOW No provenance attestation provenance

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

v0.12.2

1 finding

LOW No provenance attestation provenance

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

v0.12.1

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.

v0.12.0

1 finding

LOW No provenance attestation provenance

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

v0.11.2

1 finding

LOW No provenance attestation provenance

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

v0.11.1

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.

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

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.

v0.6.0

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.

v0.5.16

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.

v0.5.15

1 finding

LOW No provenance attestation provenance

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

v0.5.14

1 finding

LOW No provenance attestation provenance

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

v0.5.13

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.

v0.5.12

1 finding

LOW No provenance attestation provenance

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

v0.5.11

1 finding

LOW No provenance attestation provenance

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

v0.5.10

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.

v0.5.9

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.

v0.5.8

1 finding

LOW No provenance attestation provenance

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

v0.5.7

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.

v0.5.6

1 finding

LOW No provenance attestation provenance

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

v0.5.5

1 finding

LOW No provenance attestation provenance

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

v0.5.4

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.

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

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.