@zerohash-sdk/crypto-withdrawals-js@1.16.11
A JavaScript SDK that enables frontend applications to seamlessly integrate with the Connect Crypto Withdrawals product.
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe reporting is limited to a user-requested render failure and goes to the package publisher’s collector, but it sends page metadata and JWT-derived identifiers by default with no public telemetry control. This is a runtime telemetry privacy risk, not credential theft or unrelated-host exfiltration.
Decision evidence
public snapshot- When a widget script load fails during render, the loader reports the failure automatically.
- The report includes the browser user agent and page origin.
- The report includes selected decoded JWT claims and is sent as a JSON POST.
- The collector URLs are Zerohash Grafana Faro endpoints.
- The type declarations disclose failure reporting to Faro with JWT claims, but the public configuration shows no telemetry control.
- The manifest defines no lifecycle scripts.
- Importing the package exports the SDK class; reporting is triggered only by a failed widget load after render is called.
- The package does not send the raw JWT to the collector, and the collector belongs to Zerohash.
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 unpkgThe type declarations disclose failure reporting to Faro with JWT claims, but the public configuration shows no telemetry control.
dist/index.d.tsView on unpkg · L227Findings
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-withdrawals-js@1.16.11.
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.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.