@zerohash-sdk/csp-crypto-sell-react@1.15.11
A React SDK that enables frontend React applications to seamlessly integrate with the Connect CSP Crypto Sell product.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package serves its stated widget-loading purpose, but it also sends undisclosed runtime telemetry containing the page origin and browser user agent on load failure. This warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- The package exports a React wrapper component for the Connect CSP Crypto Sell product.
- When the component is rendered, an effect starts loading the remote widget and uses ZeroHash collector URLs by default.
- If loading the remote script fails, the loader reports the failure to the collector.
- The error report includes the browser user agent, page origin, app and environment details, and selected claims decoded from the JWT; it does not send the full JWT.
- The manifest has no lifecycle scripts, and the network behavior is tied to rendering the widget.
- The report is sent only on a widget script load failure and targets ZeroHash's collector.
- The exported component's documented purpose is to render the Connect CSP Crypto Sell interface.
Source & flagged code
7 flaggedThe package exports a React wrapper component for the Connect CSP Crypto Sell product.
dist/index.d.tsView on unpkg · L16When the component is rendered, an effect starts loading the remote widget and uses ZeroHash collector URLs by default.
dist/index.jsView on unpkg · L5Findings
Affected versions and remediation
This report applies to @zerohash-sdk/csp-crypto-sell-react@1.15.11.
See all versions of @zerohash-sdk/csp-crypto-sell-react for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/csp-crypto-sell-react@1.15.11 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.