@zerohash-sdk/crypto-withdrawals-js@1.16.12
A JavaScript SDK that enables frontend applications to seamlessly integrate with the Connect Crypto Withdrawals product.
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe SDK sends undisclosed runtime telemetry when widget loading fails, including page origin, browser user agent, and selected JWT claims. This is a real privacy risk, but the code sends the report to a Zerohash-branded collector and does not transmit the JWT itself.
Decision evidence
public snapshot- When script loading fails, the SDK builds a report containing decoded JWT claims, browser user agent, page origin, and failure details.
- The report is sent as a JSON POST to a Grafana Faro collector endpoint.
- Reporting is triggered by script load errors, timeouts, or a component that fails to register during the documented render flow.
- The manifest has no lifecycle scripts; network activity is initiated by the SDK’s widget-loading flow.
- The collector endpoints are Zerohash-branded, and the reported claims are selected from the JWT payload rather than sending the JWT itself.
Source & flagged code
8 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkgWhen script loading fails, the SDK builds a report containing decoded JWT claims, browser user agent, page origin, and failure details.
dist/index.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-withdrawals-js@1.16.12.
See all versions of @zerohash-sdk/crypto-withdrawals-js for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/crypto-withdrawals-js@1.16.12 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.