@abstraxn/signer-react
React SDK for Abstraxn Wallet - React components, hooks, and providers for seamless Web3 wallet integration
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@walletconnect/ethereum-provider | AI (dependencies): @walletconnect/ethereum-provider is a mainstream WalletConnect package; expected dependency for any Web3 wallet integration SDK. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all 42 versions; no provenance is the norm for this publisher. | ai | |
| phantom-deps | phantom-dep:@solana/wallet-adapter-base | AI (phantom-deps): Solana adapter deps are re-exported/config-referenced in a React SDK; not directly imported but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@solana/wallet-adapter-react-ui | AI (phantom-deps): Same pattern — UI adapter used via config/re-export in this React SDK. | ai | |
| phantom-deps | phantom-dep:@walletconnect/ethereum-provider | AI (phantom-deps): WalletConnect provider likely referenced indirectly through wagmi/viem integration layer. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.3.1 | 14 / 6 | |
| 3.3.0 | 14 / 6 | |
| 3.2.0 | 13 / 6 | |
| 3.1.4 | 13 / 6 | |
| 3.1.3 | 13 / 6 | |
| 2.1.0 | 13 / 6 | |
| 2.0.1 | 9 / 6 | |
| 1.0.16 | 8 / 6 | |
| 1.0.14 | 8 / 6 | |
| 1.0.11 | 8 / 6 | |
| 1.0.0 | 8 / 6 |
v3.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.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.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.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.