@ledgerhq/domain-service
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): Hex decoding is used for EIP-712 typed data parsing (TRUSTED_NAME field), standard blockchain domain logic. Not obfuscation or malicious payload handling. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom listed as dep in a monorepo library context; used for testing infrastructure, not a security concern for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 1.8.5 | 7 / 14 | |
| 1.8.4 | 7 / 14 | |
| 1.8.3 | 7 / 14 | |
| 1.8.2 | 7 / 14 | |
| 1.8.1 | 7 / 14 | |
| 1.8.0 | 7 / 14 | |
| 1.7.4 | 7 / 13 | |
| 1.7.3 | 7 / 13 | |
| 1.7.2 | 7 / 13 | |
| 1.7.1 | 7 / 13 | |
| 1.7.0 | 7 / 13 | |
| 1.6.6 | 7 / 13 | |
| 1.6.5 | 7 / 13 | |
| 1.6.4 | 7 / 13 | |
| 1.6.3 | 7 / 13 | |
| 1.6.2 | 7 / 13 | |
| 1.6.1 | 7 / 13 | |
| 1.6.0 | 7 / 13 | |
| 1.5.2 | 7 / 12 | |
| 1.5.1 | 7 / 12 | |
| 1.5.0 | 7 / 12 | |
| 1.4.3 | 7 / 12 | |
| 1.4.2 | 7 / 12 | |
| 1.4.1 | 7 / 12 | |
| 1.4.0 | 7 / 12 | |
| 1.3.0 | 7 / 12 | |
| 1.2.45 | 7 / 12 | |
| 1.2.44 | 7 / 12 | |
| 1.2.43 | 7 / 12 | |
| 1.2.42 | 7 / 12 | |
| 1.2.41 | 7 / 12 | |
| 1.2.40 | 7 / 12 | |
| 1.2.39 | 7 / 12 | |
| 1.2.38 | 7 / 12 | |
| 1.2.37 | 7 / 12 | |
| 1.2.36 | 7 / 12 | |
| 1.2.35 | 7 / 12 | |
| 1.2.34 | 7 / 12 | |
| 1.2.33 | 7 / 12 | |
| 1.2.32 | 7 / 12 | |
| 1.2.31 | 7 / 12 | |
| 1.2.30 | 7 / 12 | |
| 1.2.29 | 7 / 12 | |
| 1.2.28 | 7 / 12 |
v1.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.