@wallet-ui/react-native-web3js
React components for Wallet UI
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from beeman to GitHub Actions CI with SLSA attestation; legitimate automation handoff for this monorepo. | ai | |
| dependencies | unvetted-dep:@wallet-standard/react | AI (dependencies): @wallet-standard/react is a legitimate Solana wallet standard library; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@solana/wallet-standard-features | AI (phantom-deps): Peer/config-level reference in a multi-platform Solana wallet package; stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals present for this package. | ai | |
| phantom-deps | phantom-dep:@wallet-standard/react | AI (phantom-deps): Declared dep referenced in config files only; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@solana/react | AI (phantom-deps): Declared dep referenced in config files only; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 4.1.1 | 12 / 0 | |
| 4.1.0 | 12 / 0 | |
| 4.0.5 | 12 / 0 | |
| 4.0.4 | 12 / 0 | |
| 4.0.3 | 12 / 0 | |
| 4.0.2 | 12 / 0 | |
| 4.0.1 | 12 / 0 | |
| 4.0.0 | 12 / 0 | |
| 3.3.0 | 12 / 0 | |
| 3.2.1 | 12 / 0 | |
| 3.2.0 | 12 / 0 | |
| 3.1.0 | 12 / 0 | |
| 3.0.0 | 12 / 0 | |
| 2.2.2 | 11 / 0 | |
| 2.2.1 | 11 / 0 | |
| 2.2.0 | 11 / 0 |
v4.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.1
2 findingsThis version was published by a different npm account than previous versions on 2026-02-26. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.