@zerohash-sdk/csp-crypto-withdrawals-js@1.15.11
A JavaScript SDK that enables frontend applications to seamlessly integrate with the Connect CSP Crypto Withdrawals product.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package sends runtime failure telemetry to its vendor that includes JWT-derived participant context and browser/page details, with no exposed opt-out. The trigger is limited to the explicit widget render flow and a script-loading failure, so this warrants a warning rather than a malicious verdict.
Decision evidence
public snapshot- On widget load failures, diagnostics include participant, platform and region claims decoded from the supplied JWT, plus browser user agent and page origin.
- The diagnostic payload is sent by POST to hard-coded Zerohash Grafana Faro collector endpoints.
- Failure reporting is wired into the script loader used when the widget is rendered; no telemetry opt-out is exposed in the inspected entry point.
- The package has no lifecycle scripts, and importing its entry point does not itself load the widget or send a request.
- The widget script and failure reporting are activated through the explicit render flow; reporting occurs only when loading fails.
Source & flagged code
7 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkgOn widget load failures, diagnostics include participant, platform and region claims decoded from the supplied JWT, plus browser user agent and page origin.
dist/index.jsView on unpkg · L41Findings
Affected versions and remediation
This report applies to @zerohash-sdk/csp-crypto-withdrawals-js@1.15.11.
See all versions of @zerohash-sdk/csp-crypto-withdrawals-js for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/csp-crypto-withdrawals-js@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.