@ledgerhq/domain-service
1
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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
phenry-ledgersergii-shkolingbrahm-ledgerthomas.coudrayldg-github-civbouzonledger-releaser
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 1 of 101)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 8 / 22 |
v1.0.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.