@uipath/flow-tool@1.202.2
Create, debug, and run UiPath Flow projects and jobs.
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection found ordinary module and CLI entry points without lifecycle execution or a concrete malicious behavior. The observed child-process and registry use are scoped to CLI and Windows registry querying.
Decision evidence
public snapshot- The manifest exposes module entry points and a command-line binary, with no lifecycle-script section.
- The command bundle’s registry command is limited to querying a Windows registry value and returns empty on other platforms.
- The large required bundle identifies itself as vendored elkjs code.
- The binary is explicitly mapped to dist/index.js.
- The command framework can spawn a selected subcommand executable, which is normal CLI delegation rather than an automatic install-time action.
Source & flagged code
4 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.umd.min-fqefd9kn.jsView on unpkg · L1834Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/packager-tool-rew0hp2h.jsView on unpkg · L4104Findings
Affected versions and remediation
This report applies to @uipath/flow-tool@1.202.2.
See all versions of @uipath/flow-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/flow-tool@1.202.2 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.