@uipath/orchestrator-tool@1.202.1
Manage Orchestrator folders, jobs, processes, and releases.
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection shows a first-party CLI with no lifecycle hooks and only user-invoked process and network behavior aligned with Orchestrator management. Registry reads and the bundled open helper do not form a covert install or exfiltration chain.
Decision evidence
public snapshot- package.json declares a CLI for Orchestrator management with bin orchestrator-tool and main dist/tool.js and has no install lifecycle scripts.
- The only child_process use in the tool bundle is a Windows-only execFileSync of reg query for the UiPath AnalyticsUniqueId registry value.
- dist/index-sby22td6.js is the vendored open helper that spawns a local process to open a URL, used from the user-run CLI rather than at install time.
- No eval, dynamic Function, preinstall/install/postinstall hooks, or self-dependency were found.
- Network calls target caller-configured UiPath Orchestrator and identity hosts after explicit CLI use, plus generated OpenAPI fallbacks.
Source & flagged code
5 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-2p58ckbh.jsView on unpkg · L4148The only child_process use in the tool bundle is a Windows-only execFileSync of reg query for the UiPath AnalyticsUniqueId registry value.
dist/tool-2p58ckbh.jsView on unpkg · L3560Findings
Affected versions and remediation
This report applies to @uipath/orchestrator-tool@1.202.1.
See all versions of @uipath/orchestrator-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/orchestrator-tool@1.202.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.