@uipath/codedagent-tool@1.200.0
Build, run, deploy, and manage AI Agents.
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection shows a first-party CLI with no preinstall, install, or postinstall hooks and with network and process use tied to an https UiPath authority and a local uipath executable. Those behaviors match the package purpose and do not form a concrete attack chain.
Decision evidence
public snapshot- package.json exposes a module entry and codedagent-tool bin and defines no install lifecycle scripts.
- The CLI spawns a cached local uipath executable with the caller command arguments and local auth environment only after command execution.
- OAuth authorize and token URLs are built from an https-validated authority that defaults to https://cloud.uipath.com.
- dist/tool-nvhfxv67.js is bundled filesystem and local-server helper code, not an install-time payload.
- child_process and fetch are present, but they run from the user CLI or init API for UiPath Python and the configured UiPath identity host.
- Python subcommands are limited to a local whitelist such as init, deploy, publish, and run.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/tool-5be0qe39.jsView on unpkg · L737Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/tool-5be0qe39.jsView on unpkg · L19Findings
Affected versions and remediation
This report applies to @uipath/codedagent-tool@1.200.0.
See all versions of @uipath/codedagent-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/codedagent-tool@1.200.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.