@uipath/flow-tool@1.202.0
Create, debug, and run UiPath Flow projects and jobs.
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection shows a first-party UiPath Flow CLI whose shell and environment use is tied to explicit user commands and local packaging. There is no lifecycle script, self-install chain, or covert exfiltration path.
Decision evidence
public snapshot- package.json names @uipath/flow-tool 1.202.0 as a UiPath Flow CLI, exports dist entrypoints, and defines only the flow-tool bin with no install lifecycle scripts.
- dist/packager-tool-m056vsmy.js uses execFileSync only to query the Windows registry when the platform is win32, as part of the CLI runtime.
- dist/node-yz5tz1jx.js calls execSync for dotnet --version as a local tooling check inside the packager, not at install time.
- dist/elk.bundled-vpsbxz0p.js is the Eclipse Layout Kernel graph layout bundle and constructs a worker only when a worker URL or factory is supplied.
- Bundled modules import node:child_process and read process environment variables for logging, auth, and packaging, but only after the user runs the CLI.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/packager-tool-m056vsmy.jsView on unpkg · L730Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/packager-tool-m056vsmy.jsView on unpkg · L4104Findings
Affected versions and remediation
This report applies to @uipath/flow-tool@1.202.0.
See all versions of @uipath/flow-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/flow-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.