@uipath/api-workflow-tool@1.201.0
Run UiPath API Workflows locally.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe static signals are consistent with a workflow-packaging CLI and its bundled dependencies. There is no lifecycle trigger or concrete malicious behavior.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and only exports distributed modules.
- The flagged child-process and Base64 code belongs to a vendored URL-opening helper, not a decoded remote endpoint.
- Network calls publish user-selected package files to configured feed or Orchestrator URLs.
- The node packager is dynamically loaded only while a packager command is run.
- No install-time execution, self-dependency, credential harvesting, or covert endpoint was found.
- No confirmed persistence, destructive action, remote payload execution, or AI-agent configuration write was found.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/node-mcg2g1ts.jsView on unpkg · L28Findings
Affected versions and remediation
This report applies to @uipath/api-workflow-tool@1.201.0.
See all versions of @uipath/api-workflow-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/api-workflow-tool@1.201.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.