@zerohash-sdk/crypto-deposits-js@0.1.1
This library was generated with [Nx](https://nx.dev).
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe package is a browser SDK with no install-time execution or local-system capabilities. Its network activity is aligned with user-invoked widget loading and failure reporting, with no concrete malicious behavior found.
Decision evidence
public snapshot- The manifest exposes only the distributed ESM entrypoint; it defines no lifecycle scripts or dependencies.
- On an explicit render call, the SDK injects a Zerohash-hosted web-component module.
- If that load fails, it sends a diagnostic POST with browser and page metadata to a Zerohash Faro collector.
- The high scanner path is a declaration file containing loader implementation text, but it describes the same configured CDN loader rather than hidden execution.
- No install hook, self-dependency, shell execution, file access, credential harvesting, or persistence was found.
- Network behavior is browser-side and tied to rendering the advertised crypto-deposits widget.
- The failure report sends decoded JWT claims as partner context, not the JWT itself.
Source & flagged code
5 flaggedA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkgThe high scanner path is a declaration file containing loader implementation text, but it describes the same configured CDN loader rather than hidden execution.
dist/index.d.tsView on unpkg · L202Findings
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-deposits-js@0.1.1.
See all versions of @zerohash-sdk/crypto-deposits-js for other recorded verdicts.
- Review the evidence and your use of @zerohash-sdk/crypto-deposits-js@0.1.1 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.