@zerogpu/worker@0.4.0
ZeroGPU Worker — join the ZeroGPU network from a Docker container or any Node.js host (servers, macOS desktop apps, developer laptops), and serve inference locally.
AI Security Review
scanned 4d ago · by lpm-firewall-aiNo malicious exfiltration or unrelated attack behavior was identified. However, runtime telemetry is sent automatically without disclosure or an apparent opt-out, so this warrants a warning.
Decision evidence
public snapshot- Starting the worker creates an event client that flushes telemetry on a recurring timer.
- Telemetry sends device and session identifiers plus events; event records can include clipped error messages and model/task metadata.
- The telemetry endpoint uses the worker’s configured ZeroGPU registry host. The README describes joining that fleet with the operator key.
- The package describes a worker that registers with ZeroGPU and serves local inference, matching its stated purpose.
- The operator key is sent to the ZeroGPU registry for device registration; no source evidence shows it being sent to an unrelated host.
- No install hook or unrelated credential collection was identified.
Source & flagged code
6 flaggedThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/index.jsView on unpkgFindings
Affected versions and remediation
This report applies to @zerogpu/worker@0.4.0.
See all versions of @zerogpu/worker for other recorded verdicts.
- Review the evidence and your use of @zerogpu/worker@0.4.0 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.