@xrpl-wallet-kit/browser@0.1.16
Browser-ready XRPL Wallet Kit bundle for vanilla JavaScript and legacy HTML sites.
AI Security Review
scanned 26d ago · by lpm-firewall-aiThe inspected bundle’s credential use is tied to wallet authentication and API calls, with no evidence of an unrelated recipient. The flagged domains are used for a wallet deep link and error documentation, so the source supports a clean verdict.
Decision evidence
public snapshot- The manifest exposes the IIFE bundle as the main entrypoint and has only a build script.
- The SDK sends its bearer token with requests to its configured API endpoint.
- The OAuth flow accepts messages only from the named Xumm origins.
- The flagged Bitget domain is used as a WalletConnect deep link, and the other unusual domain builds error documentation URLs.
- No source evidence showed a hidden credential recipient or unrelated credential forwarding.
- The examined network and storage behavior is consistent with wallet and authentication functions.
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.16.
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.16 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.