@uipath/orchestrator-tool@1.202.0
Manage Orchestrator folders, jobs, processes, and releases.
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe inspected entry points contain no install lifecycle behavior and expose an explicit Orchestrator command interface. Authentication and process-launch code observed is consistent with that interface, with no concrete malicious behavior found.
Decision evidence
public snapshot- Package metadata exposes a library and command-line entry point and contains no lifecycle hook.
- The main bundle registers user-invoked Orchestrator management commands.
- Authentication authorities are normalized and restricted to HTTPS.
- Stored refresh tokens are used only during an expired-token refresh flow.
- The required secondary bundle uses an explicit command-and-argument process launch helper.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-2bkr8p7q.jsView on unpkg · L4148Authentication authorities are normalized and restricted to HTTPS.
dist/tool-2bkr8p7q.jsView on unpkg · L26852Findings
Affected versions and remediation
This report applies to @uipath/orchestrator-tool@1.202.0.
See all versions of @uipath/orchestrator-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/orchestrator-tool@1.202.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.