@zerohash-sdk/travel-rule-js@0.7.12
This library was generated with [Nx](https://nx.dev).
AI Security Review
scanned 5d ago · by lpm-firewall-aiThe package is a widget SDK and the collector is operated by Zerohash, but it sends runtime telemetry containing participant context and browser/page metadata without a public way to disable it. This warrants a warning rather than a malicious verdict because the report is limited to script-load failures and does not send raw credentials or file contents.
Decision evidence
public snapshot- On script-load failure, the loader posts a report to a configured Faro collector.
- The report includes selected JWT claims, browser user agent, page origin, and failure details.
- The package documents that the shared loader reports failures to Faro with partner/participant context.
- There is no public telemetry opt-out in the SDK configuration.
- The report is triggered only when loading the widget script fails, after the caller invokes render().
- The collector endpoints are Zerohash-operated, and the report is limited to diagnostic context rather than raw credentials or file contents.
- The package has no lifecycle scripts, and importing its entry point does not start the loader.
Source & flagged code
6 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkgThe package documents that the shared loader reports failures to Faro with partner/participant context.
dist/index.d.tsView on unpkg · L227Findings
Affected versions and remediation
This report applies to @zerohash-sdk/travel-rule-js@0.7.12.
See all versions of @zerohash-sdk/travel-rule-js for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/travel-rule-js@0.7.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.