@ledgerhq/coin-vechain Apache-2.0 47 versions

@ledgerhq/coin-vechain

npm Repository Homepage

Ledger VeChain Coin integration

47

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 No source commit

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

LedgerLedgerWalletVeChainvetvthoHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:lodash	AI (phantom-deps): lodash is a declared dependency in package.json; phantom-dep finding is a false positive for this package's build/config structure.	ai	2026/04/26
phantom-deps	phantom-dep:invariant	AI (phantom-deps): invariant is a declared dependency in package.json; phantom-dep finding is a false positive for this package's build/config structure.	ai	2026/04/26
phantom-deps	phantom-dep:@ledgerhq/devices	AI (phantom-deps): Same-org package declared as a dependency; phantom-dep finding is a false positive for this monorepo package.	ai	2026/04/26
semgrep	semgrep:hex-decode	AI (semgrep): Buffer.from(signature, 'hex') is standard hex decoding of a cryptographic signature in a blockchain transaction broadcast — expected and benign for a VeChain coin integration library.	ai	2026/04/25

Versions (showing 47 of 47)

Version	Deps	Published
2.22.3	14 / 14	2026-06-05
2.22.2	14 / 14	2026-05-28
2.22.1	14 / 14	2026-05-21
2.22.0	14 / 15	2026-05-13
2.21.2	14 / 15	2026-05-06
2.21.1	14 / 15	2026-05-04
2.21.0	14 / 15	2026-04-22
2.20.0	14 / 15	2026-04-15
2.19.1	14 / 13	2026-04-01
2.19.0	14 / 13	2026-03-26
2.18.0	13 / 13	2026-03-18
2.17.0	13 / 13	2026-03-12
2.16.6	13 / 12	2026-03-03
2.16.5	13 / 12	2026-02-25
2.16.4	13 / 12	2026-02-17
2.16.3	13 / 12	2026-02-10
2.16.2	13 / 12	2026-01-30
2.16.1	13 / 12	2026-01-26
2.16.0	13 / 12	2026-01-19
2.15.0	13 / 11	2026-01-13
2.14.1	13 / 11	2025-12-31
2.14.0	13 / 11	2025-12-29
2.13.1	13 / 11	2025-12-17
2.13.0	13 / 11	2025-12-08
2.12.1	13 / 11	2025-11-20
2.12.0	13 / 11	2025-11-05
2.11.0	13 / 11	2025-10-16
2.10.1	13 / 11	2025-10-01
2.10.0	13 / 11	2025-09-25
2.9.1	12 / 11	2025-09-16
2.9.0	12 / 11	2025-09-05
2.8.2	12 / 11	2025-08-27
2.8.1	12 / 11	2025-08-18
2.8.0	12 / 11	2025-08-08
2.7.15	12 / 12	2025-07-31
2.7.14	12 / 12	2025-07-23
2.7.13	12 / 12	2025-07-17
2.7.12	12 / 12	2025-07-07
2.7.11	12 / 12	2025-06-27
2.7.10	12 / 12	2025-06-20
2.7.9	12 / 12	2025-06-17
2.7.8	12 / 13	2025-06-06
2.7.7	12 / 13	2025-05-27
2.7.6	12 / 13	2025-05-20
2.7.5	12 / 13	2025-05-13
2.7.4	12 / 12	2025-04-30
2.7.3	12 / 12	2025-04-25

v2.22.3

1 finding

LOW No provenance attestation provenance

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

v2.22.2

1 finding

LOW No provenance attestation provenance

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

v2.22.1

1 finding

LOW No provenance attestation provenance

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

v2.22.0

1 finding

LOW No provenance attestation provenance

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

v2.21.2

1 finding

LOW No provenance attestation provenance

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

v2.21.1

1 finding

LOW No provenance attestation provenance

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

v2.21.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.

v2.20.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.

v2.19.1

1 finding

LOW No provenance attestation provenance

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

v2.19.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.

v2.11.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.

v2.10.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.

v2.10.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.

v2.9.1

1 finding

LOW No provenance attestation provenance

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

v2.9.0

1 finding

LOW No provenance attestation provenance

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

v2.8.2

1 finding

LOW No provenance attestation provenance

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

v2.8.1

1 finding

LOW No provenance attestation provenance

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

v2.8.0

1 finding

LOW No provenance attestation provenance

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

v2.7.15

1 finding

LOW No provenance attestation provenance

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

v2.7.14

1 finding

LOW No provenance attestation provenance

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

v2.7.13

1 finding

LOW No provenance attestation provenance

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

v2.7.12

1 finding

LOW No provenance attestation provenance

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

v2.7.11

1 finding

LOW No provenance attestation provenance

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

v2.7.10

1 finding

LOW No provenance attestation provenance

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

v2.7.9

1 finding

LOW No provenance attestation provenance

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

v2.7.8

1 finding

LOW No provenance attestation provenance

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

v2.7.7

1 finding

LOW No provenance attestation provenance

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

v2.7.6

1 finding

LOW No provenance attestation provenance

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

v2.7.5

1 finding

LOW No provenance attestation provenance

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

v2.7.4

1 finding

LOW No provenance attestation provenance

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

v2.7.3

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.