@xrpl-wallet-kit/browser@0.1.21
Browser-ready XRPL Wallet Kit bundle for vanilla JavaScript and legacy HTML sites.
AI Security Review
scanned 21d ago · by lpm-firewall-aiSource inspection found no malicious behavior. Scanner flags correspond to a caller-configurable XUMM API client and a Bitget Wallet connection link, while wallet transactions require a caller request and active adapter.
Decision evidence
public snapshot- package.json points to the browser bundle and lists only a build script, with no install lifecycle hook.
- The wallet kit constructs a client; transaction submission requires an active adapter and a caller request.
- The embedded XUMM SDK defaults to xumm.app and changes endpoint only through its explicit setter.
- The SDK sends XUMM API credentials to its configured API endpoint; no unrelated recipient is shown by the inspected flow.
- bkcode.vip appears as Bitget Wallet's WalletConnect universal link.
Source & flagged code
7 flaggedSource appears to send environment or credential material to an external endpoint.
dist/xrpl-wallet-kit.iife.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @xrpl-wallet-kit/browser@0.1.21.
See all versions of @xrpl-wallet-kit/browser for other recorded verdicts.
- Review the evidence and your use of @xrpl-wallet-kit/browser@0.1.21 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.