@uipath/agent-tool@1.202.0
cli plugin for creating and managing UiPath low-code agents
AI Security Review
scanned 28d ago · by lpm-firewall-aiThere are no npm lifecycle hooks, and the entrypoints only start a UiPath agent CLI after the user invokes it. Process spawning and cloud authentication are package-aligned CLI behavior, not a hidden install attack.
Decision evidence
public snapshot- package.json version 1.202.0 has no install lifecycle scripts; main, exports, and bin point at dist CLI modules that run only when the user invokes the agent-tool command.
- Bundled command registration describes a UiPath low-code agent CLI with prefix agent; auth defaults to https://cloud.uipath.com and a local .uipath profile.
- child_process imports in dist/index-h8cph72k.js come from the bundled open/wsl helper libraries, not an install-time payload.
- Compiled bundles include child_process, new Function in schema validation, and UiPath session environment variables used when the CLI authenticates to the configured cloud host.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/packager-tool-wmd0pbnz.jsView on unpkg · L10156Findings
Affected versions and remediation
This report applies to @uipath/agent-tool@1.202.0.
See all versions of @uipath/agent-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/agent-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.