@connect-xyz/withdraw-react@0.52.1
A React SDK that enables frontend React applications to seamlessly integrate with the Connect Withdraw product.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time, host-level, destructive, or covert exfiltration behavior was found. The runtime remote-code loading capability remains a concrete security risk, so this should be warned rather than marked clean.
Decision evidence
public snapshot- The React component dynamically appends a remote module script from Connect SDK hosts when it is rendered.
- The remote custom element receives the caller-provided JWT as an attribute, so remotely supplied code can access authentication material.
- On load failures, the package posts diagnostic data including browser and page-origin metadata to Grafana collector endpoints.
- The published manifest exposes an ESM dist entry and contains no lifecycle scripts.
- All inspected executable code is readable JavaScript; there is no obfuscation, shell execution, filesystem access, eval, or install hook.
- Remote loading occurs only after the application renders the Withdraw component, not during package installation or import.
- The loader targets fixed vendor-aligned Connect SDK URLs and provides sandbox and production choices.
Source & flagged code
5 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgThe published manifest exposes an ESM dist entry and contains no lifecycle scripts.
package.jsonView on unpkg · L1Findings
Affected versions and remediation
This report applies to @connect-xyz/withdraw-react@0.52.1.
See all versions of @connect-xyz/withdraw-react for other recorded verdicts.
- Review the evidence and your use of @connect-xyz/withdraw-react@0.52.1 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.