@deveco-test/deveco-cli-common@1.3.10-Test.2
HarmonyOS application development command line tool
AI Security Review
scanned 6d ago · by lpm-firewall-aiThe package sends runtime telemetry by default to its vendor's endpoint and includes machine details beyond basic anonymous usage metrics. An opt-out exists, but the reviewed source does not establish that users are informed, so this warrants a warning rather than a block.
Decision evidence
public snapshot- The CLI initializes telemetry and starts its scheduler by default unless DEVECO_CLI_DISABLE_TELEMETRY is set to 1 or true.
- Telemetry uploads go to Huawei DevEco Studio's CLI trace endpoint; the background process flushes pending events at startup.
- Trace events include a persistent install ID, session ID, runtime and OS details, total RAM, and event details; the source does not establish that users are told about this collection.
- The package describes itself as a HarmonyOS development CLI, and the telemetry endpoint is on Huawei's DevEco Studio domain.
- Users can disable telemetry with DEVECO_CLI_DISABLE_TELEMETRY=1 or true.
- The reviewed telemetry code does not show credential collection or transmission to an unrelated host.
Source & flagged code
7 flaggedPackage source references child process execution.
dist/internal/telemetry-upload-background.jsView on unpkg · L8A single source file combines environment access, network access, and code or shell execution; review context before blocking.
dist/internal/telemetry-upload-background.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @deveco-test/deveco-cli-common@1.3.10-Test.2.
See all versions of @deveco-test/deveco-cli-common for other recorded verdicts.
- Review the evidence and your use of @deveco-test/deveco-cli-common@1.3.10-Test.2 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.