@ledgerhq/hw-app-multiversx No license 20 versions

@ledgerhq/hw-app-multiversx

npm Repository Homepage

20

Versions

—

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

LedgerLedgerWalletegldMultiversXNanoSBlueHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:axios	AI (phantom-deps): Declared dependency legitimately used in MultiversX app; phantom-dep false positive in monorepo context.	ai	2026/04/26
phantom-deps	phantom-dep:protobufjs	AI (phantom-deps): Declared dependency legitimately used in MultiversX app; phantom-dep false positive in monorepo context.	ai	2026/04/26
phantom-deps	phantom-dep:bignumber.js	AI (phantom-deps): Declared dependency legitimately used in MultiversX app; phantom-dep false positive in monorepo context.	ai	2026/04/26
semgrep	semgrep:hex-decode	AI (semgrep): Hex decoding of cryptographic signature buffers is standard and expected in a hardware wallet signing library; not a malicious payload indicator.	ai	2026/04/26
dependencies	unvetted-dep:protobufjs	AI (dependencies): protobufjs is a widely-used legitimate serialization library; appropriate dependency for MultiversX blockchain transaction encoding.	ai	2026/04/26
dependencies	unvetted-dep:@multiversx/sdk-core	AI (dependencies): Official MultiversX blockchain SDK; appropriate dependency for a hardware wallet app targeting the MultiversX network.	ai	2026/04/26

Versions (showing 20 of 20)

Version	Deps	Published
6.30.3	6 / 10	2026-06-05
6.30.2	6 / 10	2026-05-06
6.30.1	6 / 10	2026-04-22
6.30.0	6 / 10	2026-04-15
6.29.1	6 / 10	2026-03-26
6.29.0	6 / 10	2026-03-18
6.28.0	6 / 10	2026-03-12
6.27.0	6 / 10	2026-01-19
6.26.3	6 / 9	2026-01-13
6.26.2	6 / 9	2025-12-29
6.26.1	6 / 9	2025-12-17
6.26.0	6 / 9	2025-11-05
6.25.3	6 / 9	2025-10-01
6.25.2	6 / 9	2025-09-25
6.25.1	6 / 9	2025-09-05
6.25.0	6 / 9	2025-08-18
6.24.4	6 / 9	2025-07-23
6.24.3	6 / 9	2025-06-20
6.24.2	6 / 10	2025-06-06
6.24.1	6 / 10	2025-05-27

v6.30.3

1 finding

LOW No provenance attestation provenance

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

v6.30.2

1 finding

LOW No provenance attestation provenance

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

v6.30.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.

v6.30.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.

v6.29.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.

v6.29.0

1 finding

LOW No provenance attestation provenance

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

v6.28.0

1 finding

LOW No provenance attestation provenance

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

v6.27.0

1 finding

LOW No provenance attestation provenance

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

v6.26.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.

v6.26.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.

v6.25.3

1 finding

LOW No provenance attestation provenance

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

v6.25.2

1 finding

LOW No provenance attestation provenance

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

v6.25.1

1 finding

LOW No provenance attestation provenance

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

v6.25.0

1 finding

LOW No provenance attestation provenance

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

v6.24.4

1 finding

LOW No provenance attestation provenance

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

v6.24.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.

v6.24.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.

v6.24.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.