@xrpl-wallet-kit/browser@0.3.2
Browser-ready XRPL Wallet Kit bundle for vanilla JavaScript and legacy HTML sites.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the examined bundle behavior fits a browser wallet kit: it restores Xumm session state for that integration and loads an associated runtime when requested. The scanner’s credential and dynamic-require flags are consistent with these features; no unrelated collection or concealed automatic action was found.
Decision evidence
public snapshot- The package exports a browser wallet bundle and an ES module entry; it declares no install lifecycle hooks.
- The ES module entry only installs a Buffer polyfill and re-exports the wallet client API.
- The Xahau runtime is loaded dynamically from a URL derived from the bundle’s own script URL, when the loader is used.
- The bundle’s Xumm integration restores its own session JWT from browser storage and uses the Xumm service.
- The XrpDomains resolver uses its documented service endpoint for name and profile lookups.
- The bundle reads a JWT from localStorage, but the surrounding code identifies it as Xumm session state.
- The examined external requests target wallet, ledger, and name-resolution services consistent with the package’s browser wallet purpose.
Source & flagged code
7 flaggedPackage source references dynamic require/import behavior.
dist/xahau-lazy.jsView on unpkg · L13Source appears to send environment or credential material to an external endpoint.
dist/xrpl-wallet-kit.iife.jsFindings
Affected versions and remediation
This report applies to @xrpl-wallet-kit/browser@0.3.2.
See all versions of @xrpl-wallet-kit/browser for other recorded verdicts.
- Review the evidence and your use of @xrpl-wallet-kit/browser@0.3.2 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.