@walletconnect/relay-auth
Relay Client Authentication
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uint8arrays | AI (phantom-deps): uint8arrays is a legitimate dependency for cryptographic operations in relay auth; phantom-dep is a code-quality signal, not a security risk. | ai | |
| phantom-deps | phantom-dep:@noble/curves | AI (phantom-deps): @noble/curves is a legitimate dependency for EdDSA/Ed25519 operations; phantom-dep is a code-quality signal, not a security risk. | ai | |
| phantom-deps | phantom-dep:@noble/hashes | AI (phantom-deps): @noble/hashes is a legitimate dependency for cryptographic hashing; phantom-dep is a code-quality signal, not a security risk. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 1.1.0 | 5 / 7 | |
| 1.0.4 | 6 / 9 | |
| 1.0.3 | 5 / 10 | |
| 1.0.2 | 5 / 10 | |
| 1.0.1 | 5 / 10 | |
| 1.0.0 | 4 / 10 |
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.