← Home

@mysten/ledgerjs-hw-app-sui

18
Versions
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

ebmifahayespaul-mystenrushrs

Keywords

LedgerLedgerWalletLedgerSignerSuiNanoSBlueHardware Wallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from personal account (ebmifa) to GitHub Actions CI publishing is a supply chain improvement, not a takeover. SLSA provenance attestation confirms legitimate CI build. ai
source-diff net-exec-file:dist/Sui.mjs AI (source-diff): dist/Sui.mjs is a rolldown bundle that inlines previously-external @ledgerhq/* runtime deps. Network imports are from bundled transport libraries, not malicious code. SLSA attestation confirms build integrity. ai
source-diff source-size-tripled AI (source-diff): Size increase from 44KB to 940KB is explained by bundling 8 previously-external @ledgerhq/* runtime deps into the output via tsdown/rolldown migration. ai
publish-pattern dormant-publish AI (publish-pattern): Dormancy followed by legitimate org-owned CI publish with SLSA provenance. Mysten Labs is the established Sui blockchain team with 191 versions in registry. ai
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is used to convert Ledger trust service token descriptor data and signatures into binary buffers — standard cryptographic handling for a hardware wallet integration, not a malicious payload. ai
phantom-deps phantom-dep:@ledgerhq/ledger-trust-service AI (phantom-deps): @ledgerhq/ledger-trust-service is a declared runtime dependency used in config/indirect references; not a security risk for this legitimate Ledger integration package. ai

Versions (showing 18 of 18)

Version Deps Published
0.9.0 7 / 5
0.8.3 7 / 5
0.8.2 7 / 5
0.8.1 7 / 5
0.8.0 7 / 5
0.7.1 0 / 13
0.7.0 8 / 8
0.6.0 2 / 7
0.5.2 2 / 7
0.5.1 2 / 7
0.5.0 2 / 7
0.4.2 2 / 7
0.4.1 2 / 7
0.4.0 2 / 7
0.3.1 2 / 7
0.3.0 2 / 7
0.2.0 2 / 11
0.1.0 2 / 11

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

v0.2.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.1.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.