@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, so a manually published version cannot be tied back to a reviewed commit.
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 100 of 101)
| Version | Deps | Published |
|---|---|---|
| 1.8.10 | 7 / 14 | |
| 1.8.9 | 7 / 14 | |
| 1.8.8 | 7 / 14 | |
| 1.8.7 | 7 / 14 | |
| 1.8.6 | 7 / 14 | |
| 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 | |
| 1.2.27 | 7 / 12 | |
| 1.2.26 | 7 / 12 | |
| 1.2.25 | 7 / 12 | |
| 1.2.24 | 7 / 12 | |
| 1.2.23 | 7 / 12 | |
| 1.2.22 | 7 / 12 | |
| 1.2.21 | 7 / 12 | |
| 1.2.20 | 7 / 12 | |
| 1.2.19 | 7 / 12 | |
| 1.2.18 | 7 / 12 | |
| 1.2.17 | 7 / 12 | |
| 1.2.16 | 7 / 12 | |
| 1.2.15 | 7 / 12 | |
| 1.2.14 | 7 / 12 | |
| 1.2.13 | 7 / 12 | |
| 1.2.12 | 7 / 12 | |
| 1.2.11 | 7 / 12 | |
| 1.2.10 | 7 / 12 | |
| 1.2.9 | 7 / 12 | |
| 1.2.8 | 7 / 12 | |
| 1.2.7 | 7 / 12 | |
| 1.2.6 | 7 / 12 | |
| 1.2.5 | 7 / 12 | |
| 1.2.4 | 7 / 12 | |
| 1.2.3 | 7 / 12 | |
| 1.2.2 | 7 / 12 | |
| 1.2.1 | 7 / 12 | |
| 1.2.0 | 7 / 12 | |
| 1.1.21 | 7 / 12 | |
| 1.1.20 | 7 / 12 | |
| 1.1.19 | 7 / 13 | |
| 1.1.18 | 7 / 13 | |
| 1.1.17 | 7 / 13 | |
| 1.1.16 | 7 / 13 | |
| 1.1.15 | 7 / 13 | |
| 1.1.14 | 7 / 13 | |
| 1.1.13 | 8 / 13 | |
| 1.1.12 | 8 / 13 | |
| 1.1.11 | 8 / 13 | |
| 1.1.10 | 8 / 13 | |
| 1.1.9 | 8 / 13 | |
| 1.1.8 | 8 / 13 | |
| 1.1.7 | 8 / 13 | |
| 1.1.6 | 8 / 13 | |
| 1.1.5 | 8 / 13 | |
| 1.1.4 | 8 / 21 | |
| 1.1.3 | 8 / 21 | |
| 1.1.2 | 8 / 21 | |
| 1.1.1 | 8 / 21 | |
| 1.1.0 | 8 / 21 | |
| 1.0.1 | 8 / 22 |
v1.8.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.