@zerohash-sdk/crypto-withdrawals-js@1.16.13
A JavaScript SDK that enables frontend applications to seamlessly integrate with the Connect Crypto Withdrawals product.
AI Security Review
scanned 7h ago · by lpm-firewall-aiThe SDK performs automatic runtime telemetry to Zerohash’s collector with identifying context, including selected JWT claims and the integrator page origin, and exposes no opt-out. This is suspicious telemetry; the source does not show the raw JWT being sent or unrelated collection.
Decision evidence
public snapshot- When widget script loading fails, the SDK reports the failure with selected JWT claims to a configured Zerohash Faro collector.
- The report includes the browser user-agent and the current page origin, which can identify the integrator’s site.
- Reporting is wired into the loader’s failure handler and runs by default when the widget is rendered; no opt-out is exposed.
- The package has no lifecycle scripts, and importing it defines the SDK without making a request.
- The report is limited to widget script-load failures and contains diagnostic context, not the raw JWT.
- The type declaration comments disclose Faro failure reporting with partner/participant context.
- The endpoints are Zerohash collector hosts selected for the configured environment.
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 unpkgReporting is wired into the loader’s failure handler and runs by default when the widget is rendered; no opt-out is exposed.
dist/index.d.tsView on unpkg · L227Findings
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-withdrawals-js@1.16.13.
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.13 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.