@ledgerhq/coin-sui Apache-2.0 47 versions

@ledgerhq/coin-sui

npm Repository Homepage

Ledger Sui 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

LedgerLedgerWalletSui

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-removed	AI (maintainer-change): LedgerHQ org uses CI publisher; individual maintainer removals are routine org hygiene, not takeover signals.	ai	2026/05/18
semgrep	semgrep:api-obfuscation-reflect	AI (semgrep): Reflect.get() is used in a standard JavaScript Proxy trap handler for SDK wrapping — a common, legitimate pattern in this network SDK context. Not obfuscation.	ai	2026/04/25

Versions (showing 47 of 47)

Version	Deps	Published
0.36.0	18 / 13	2026-06-05
0.35.0	18 / 13	2026-05-28
0.34.0	18 / 13	2026-05-21
0.33.0	16 / 12	2026-05-13
0.32.1	16 / 12	2026-05-06
0.32.0	16 / 12	2026-05-04
0.31.0	16 / 12	2026-04-22
0.30.0	16 / 12	2026-04-15
0.29.0	16 / 10	2026-04-01
0.28.0	16 / 10	2026-03-26
0.27.0	15 / 10	2026-03-18
0.26.0	15 / 10	2026-03-12
0.25.0	15 / 9	2026-03-03
0.24.1	15 / 9	2026-02-25
0.24.0	15 / 9	2026-02-17
0.23.0	15 / 8	2026-02-10
0.22.1	15 / 8	2026-01-30
0.22.0	15 / 8	2026-01-26
0.21.0	15 / 8	2026-01-19
0.20.0	15 / 7	2026-01-13
0.19.1	15 / 7	2025-12-31
0.19.0	15 / 7	2025-12-29
0.18.2	15 / 7	2025-12-17
0.18.1	15 / 7	2025-12-08
0.18.0	16 / 7	2025-11-20
0.17.0	16 / 7	2025-11-05
0.16.0	16 / 7	2025-10-16
0.15.0	15 / 7	2025-10-01
0.14.0	16 / 7	2025-09-25
0.13.0	15 / 7	2025-09-16
0.12.0	15 / 7	2025-09-05
0.11.0	15 / 7	2025-08-27
0.10.0	15 / 7	2025-08-18
0.9.0	15 / 7	2025-08-08
0.8.0	15 / 7	2025-07-31
0.7.0	15 / 7	2025-07-23
0.6.1	15 / 7	2025-07-11
0.6.0	15 / 7	2025-07-07
0.5.2	13 / 7	2025-06-27
0.5.1	13 / 7	2025-06-20
0.5.0	13 / 7	2025-06-17
0.4.1	13 / 7	2025-06-06
0.4.0	13 / 7	2025-05-27
0.3.3	13 / 7	2025-05-20
0.3.2	13 / 7	2025-05-13
0.3.1	13 / 7	2025-04-30
0.3.0	13 / 7	2025-04-25

v0.36.0

1 finding

LOW No provenance attestation provenance

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

v0.35.0

1 finding

LOW No provenance attestation provenance

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

v0.34.0

1 finding

LOW No provenance attestation provenance

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

v0.33.0

1 finding

LOW No provenance attestation provenance

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

v0.32.1

1 finding

LOW No provenance attestation provenance

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

v0.32.0

1 finding

LOW No provenance attestation provenance

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

v0.31.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.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.

v0.29.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.28.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.22.0

1 finding

LOW No provenance attestation provenance

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

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.0

1 finding

LOW No provenance attestation provenance

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

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.0

1 finding

LOW No provenance attestation provenance

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

v0.10.0

1 finding

LOW No provenance attestation provenance

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

v0.9.0

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.3

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.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.