@reown/appkit-experimental
The @reown/appkit-experimental package provides a set of cutting-edge, experimental features for Web3 developers. This package serves as a testing ground for innovative concepts and implementations that are not yet widely adopted or standardized in the bl
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org-wide publisher migration, consistent across many Reown packages, not a takeover. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org migration; old individual maintainers replaced by org account. | ai | |
| provenance | publisher-changed-stale | AI (provenance): Stable for 458 days post-change, inconsistent with compromise. | ai | |
| phantom-deps | phantom-dep:@reown/appkit | AI (phantom-deps): Same-org monorepo sibling dependency, false positive. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.8.23 | 9 / 2 | |
| 1.8.22 | 9 / 2 | |
| 1.8.21 | 9 / 2 | |
| 1.8.20 | 9 / 2 | |
| 1.8.19 | 9 / 2 | |
| 1.8.18 | 9 / 2 | |
| 1.8.17 | 9 / 2 | |
| 1.8.16 | 9 / 2 | |
| 1.8.15 | 9 / 2 | |
| 1.8.14 | 9 / 2 | |
| 1.8.13 | 9 / 2 | |
| 1.8.12 | 9 / 2 | |
| 1.8.11 | 9 / 2 | |
| 1.8.10 | 9 / 2 | |
| 1.8.9 | 9 / 2 | |
| 1.8.8 | 9 / 2 | |
| 1.8.7 | 9 / 2 | |
| 1.8.6 | 9 / 2 | |
| 1.8.5 | 9 / 2 | |
| 1.8.4 | 9 / 2 | |
| 1.8.3 | 9 / 2 | |
| 1.8.2 | 9 / 2 | |
| 1.8.1 | 9 / 2 | |
| 1.8.0 | 9 / 2 | |
| 1.7.20 | 9 / 2 | |
| 1.7.19 | 9 / 2 | |
| 1.7.18 | 9 / 2 | |
| 1.7.17 | 9 / 2 | |
| 1.7.16 | 9 / 2 | |
| 1.7.15 | 9 / 2 | |
| 1.7.14 | 9 / 2 | |
| 1.7.13 | 9 / 2 | |
| 1.7.12 | 9 / 2 | |
| 1.7.11 | 9 / 2 | |
| 1.7.10 | 9 / 2 | |
| 1.7.9 | 9 / 2 | |
| 1.7.8 | 9 / 2 | |
| 1.7.7 | 9 / 2 | |
| 1.7.6 | 9 / 2 | |
| 1.7.5 | 9 / 2 | |
| 1.7.4 | 9 / 2 | |
| 1.7.3 | 9 / 2 | |
| 1.7.2 | 9 / 2 | |
| 1.7.1 | 9 / 2 | |
| 1.7.0 | 8 / 2 | |
| 1.6.9 | 8 / 2 | |
| 1.6.8 | 7 / 2 | |
| 1.6.7 | 7 / 2 | |
| 1.6.6 | 7 / 2 | |
| 1.6.5 | 7 / 2 | |
| 1.6.4 | 7 / 2 |
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.