@uipath/traces-tool@1.201.0
Query execution traces for UiPath jobs
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo install-time execution, self-dependency, credential harvesting, or confirmed exfiltration path was found. The Base64-obscured telemetry connection string and process-launching URL helper remain suspicious enough to warn because static analysis coverage was incomplete.
Decision evidence
public snapshot- The manifest exposes an executable CLI, so package code runs when the user invokes the command.
- The bundle Base64-decodes a built-in Application Insights telemetry connection string.
- A bundled URL-opening helper can spawn a platform opener process.
- The manifest has no preinstall, install, postinstall, or other lifecycle script.
- The executable registers trace and feedback commands rather than performing work at installation or import time.
- Trace requests are made only from a command action after checking login state and attach the existing UiPath bearer token to the configured service URL.
- The decoded telemetry constant is not used by the shown local telemetry initialization, which selects a logger provider.
Source & flagged code
5 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-e67apx6g.jsView on unpkg · L3705The bundle Base64-decodes a built-in Application Insights telemetry connection string.
dist/tool-e67apx6g.jsView on unpkg · L3704Findings
Affected versions and remediation
This report applies to @uipath/traces-tool@1.201.0.
See all versions of @uipath/traces-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/traces-tool@1.201.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.