@relayprotocol/relay-ethers-wallet-adapter No license 16 versions

@relayprotocol/relay-ethers-wallet-adapter

npm Repository Homepage

An adapter used to convert an ethersjs signer to an Adapted Wallet for use in the @relayprotocol/relay-sdk

16

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pedromcunha-unevenjulien51

Keywords

nftreservoirrelay-ethers-wallet-adapterreservoir-ethers-wallet-adapterrelayprotocolsdk-adapter

Versions (showing 16 of 16)

Version	Deps	Published
29.0.5	1 / 1	2026-04-28
29.0.4	1 / 1	2026-04-24
29.0.3	1 / 1	2026-04-21
29.0.2	1 / 1	2026-04-17
29.0.1	1 / 1	2026-02-25
29.0.0	1 / 1	2026-02-23
28.0.1	1 / 1	2026-02-17
28.0.0	1 / 1	2026-02-02
27.0.3	1 / 1	2026-01-30
27.0.2	1 / 1	2026-01-21
27.0.1	1 / 1	2026-01-14
27.0.0	1 / 1	2026-01-08
26.0.1	1 / 1	2026-01-06
26.0.0	1 / 1	2025-12-17
25.0.0	1 / 1	2025-12-10
24.0.1	1 / 1	2025-11-21

v29.0.5

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.

v29.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.2

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.

v29.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v29.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v28.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v27.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v26.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v24.0.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.