@reown/appkit-adapter-ethers5
The full stack toolkit to build onchain app UX.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@reown/appkit-ui | AI (phantom-deps): Monorepo adapter; @reown/appkit-ui used transitively through @reown/appkit. | ai | |
| phantom-deps | phantom-dep:@walletconnect/utils | AI (phantom-deps): Declared and used transitively; stable pattern for this package. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with same org migration seen across reown packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide publisher migration with strong track record, not a takeover. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stable 458d on npm, consistent with legitimate account migration. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-wallet | AI (phantom-deps): Intra-org dependency; stable pattern for @reown monorepo packages. | ai | |
| phantom-deps | phantom-dep:@reown/appkit-scaffold-ui | AI (phantom-deps): Intra-org dependency; stable pattern for @reown monorepo packages. | ai | |
| phantom-deps | phantom-dep:valtio | AI (phantom-deps): Valtio is used transitively through @reown internal modules; stable pattern for this monorepo. | ai |
Versions (showing 51 of 82)
| Version | Deps | Published |
|---|---|---|
| 1.8.23 | 9 / 3 | |
| 1.8.22 | 9 / 3 | |
| 1.8.21 | 9 / 3 | |
| 1.8.20 | 9 / 3 | |
| 1.8.19 | 9 / 3 | |
| 1.8.18 | 9 / 3 | |
| 1.8.17 | 9 / 3 | |
| 1.8.16 | 9 / 3 | |
| 1.8.15 | 9 / 3 | |
| 1.8.14 | 9 / 3 | |
| 1.8.13 | 9 / 3 | |
| 1.8.12 | 9 / 3 | |
| 1.8.11 | 9 / 3 | |
| 1.8.10 | 9 / 3 | |
| 1.8.9 | 9 / 3 | |
| 1.8.8 | 9 / 3 | |
| 1.8.7 | 9 / 3 | |
| 1.8.6 | 9 / 3 | |
| 1.8.5 | 9 / 3 | |
| 1.8.4 | 9 / 3 | |
| 1.8.3 | 9 / 3 | |
| 1.8.2 | 9 / 3 | |
| 1.8.1 | 9 / 3 | |
| 1.8.0 | 9 / 3 | |
| 1.7.20 | 9 / 3 | |
| 1.7.19 | 9 / 3 | |
| 1.7.18 | 9 / 3 | |
| 1.7.17 | 9 / 3 | |
| 1.7.16 | 9 / 3 | |
| 1.7.15 | 9 / 3 | |
| 1.7.14 | 9 / 3 | |
| 1.7.13 | 9 / 3 | |
| 1.7.12 | 9 / 3 | |
| 1.7.11 | 9 / 3 | |
| 1.7.10 | 9 / 3 | |
| 1.7.9 | 9 / 3 | |
| 1.7.8 | 9 / 3 | |
| 1.7.7 | 9 / 3 | |
| 1.7.6 | 9 / 3 | |
| 1.7.5 | 9 / 3 | |
| 1.7.4 | 9 / 3 | |
| 1.7.3 | 9 / 3 | |
| 1.7.2 | 9 / 3 | |
| 1.7.1 | 9 / 3 | |
| 1.7.0 | 9 / 3 | |
| 1.6.9 | 11 / 3 | |
| 1.6.8 | 11 / 3 | |
| 1.6.7 | 11 / 3 | |
| 1.6.6 | 11 / 3 | |
| 1.6.5 | 11 / 3 | |
| 1.6.4 | 11 / 3 |
v1.8.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.8.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.7.3
2 findingsThis version was published by a different npm account (reown-npm-org) than the most recent previously approved version (rocky-wc) on 2025-04-15. It has since remained available on npm for 458 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.