registry / @zerohash-sdk/crypto-deposits-js / 0.4.9
@zerohash-sdk/crypto-deposits-js@0.4.9
This library was generated with [Nx](https://nx.dev).
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe manifest and required declaration file match a caller-configured widget SDK. Runtime network activity is tied to rendering and failure diagnostics sent to Zerohash endpoints; the inspected report body contains metadata rather than the JWT itself.
Static reason
No blocking static signals were detected.
Trigger
The consumer calls render and the widget script fails to load.
Impact
The reviewed behavior supports widget loading and failure diagnostics; no confirmed attack surface was established.
Mechanism
The SDK sends a diagnostic POST containing application, environment, browser, page-origin, and selected JWT-derived claim metadata.
AI rationale
The manifest and required declaration file match a caller-configured widget SDK. Runtime network activity is tied to rendering and failure diagnostics sent to Zerohash endpoints; the inspected report body contains metadata rather than the JWT itself.
Evidence
dist/index.js
Network endpoints10
grafana-faro-collector.dev.0hash.comgrafana-faro-collector.cert.zerohash.comgrafana-faro-collector.zerohash.comgrafana-faro-collector.cert.zerohash.eugrafana-faro-collector.zerohash.eusdk-cdn.dev.0hash.comsdk-cdn.cert.zerohash.comsdk-cdn.zerohash.comsdk-cdn.cert.zerohash.eusdk-cdn.zerohash.eu
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest points to the bundled runtime entrypoint and declares no lifecycle scripts.
- The declared API uses a caller-provided JWT and renders the widget on request.
- Rendering loads the widget from Zerohash CDN hosts; only a script-load failure triggers diagnostic reporting.
- The failure report posts diagnostic metadata to environment-specific Zerohash collectors; the visible payload includes page origin, browser user agent, and selected JWT-derived claims, not a JWT field.
Evidence against
Behavioral surface
Network
UrlStrings
Source & flagged code
9 flaggeddist/index.d.tsView file
•stage = ast_semantic_analysis; reason = ast_parse_error; limitedFiles = 1
High
Semantic Analysis Limited
A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index.d.tsView on unpkg28* (`updateConfig({ jwt })`).
*/
jwt: string;
/**
* Target environment
* @default 'production'
*/
env?: Environment;
/**
* Theme mode
* @default 'light'
*
* Available themes:
* -
Low
Ai Review Evidence
The declared API uses a caller-provided JWT and renders the widget on request.
dist/index.d.tsView on unpkg · L28package.jsonView file
1{
"name": "@zerohash-sdk/crypto-deposits-js",
"version": "0.4.9",
"private": false,
"type": "module",
"main": "./dist/index.js",
"module": "./dist/index.js",
"types": "./dist/index.d.ts",
"license": "MIT",
"exports": {
"./package.json": "./package.json",
".": {
"types": "./dist/index.d.ts",
"import": "./dist/index.js",
"default": "./dist/index.js"
}
},
"files": [
"dist",
"!**/*.tsbuildinfo"
],
"nx": {
"name": "crypto-deposits-js"
}
}
Findings
1 High1 Medium9 Low
HighSemantic Analysis Limiteddist/index.d.ts
MediumNetwork
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/index.d.ts
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
LowAi Review Evidencedist/index.js
Affected versions and remediation
This report applies to @zerohash-sdk/crypto-deposits-js@0.4.9.
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.4.9 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.