@uipath/orchestrator-tool@1.201.0
Manage Orchestrator folders, jobs, processes, and releases.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe suspicious primitives are consistent with a bundled management CLI and are activated by explicit commands. No lifecycle hook, covert execution path, credential harvesting, or exfiltration behavior was found.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and exposes only library and CLI entry points.
- The encoded telemetry connection string is declared once and has no other source references.
- The flagged child-process code begins in a bundled browser-opening helper.
- No install-time execution, self-dependency, persistence, or hidden payload loading was found.
- Network and file operations implement user-invoked Orchestrator commands, including explicit uploads and downloads.
- Telemetry properties are redacted for tokens, secrets, passwords, credentials, and authorization fields.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-x2zr87wv.jsView on unpkg · L3727Package source references dynamic require/import behavior.
dist/tool-x2zr87wv.jsView on unpkg · L740The encoded telemetry connection string is declared once and has no other source references.
dist/tool-x2zr87wv.jsView on unpkg · L3728Findings
Affected versions and remediation
This report applies to @uipath/orchestrator-tool@1.201.0.
See all versions of @uipath/orchestrator-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/orchestrator-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.