@uipath/api-workflow-tool@1.202.0
Run UiPath API Workflows locally.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThe package has no lifecycle hook or self-dependency and its inspected bundles implement explicit workflow tooling. Network and credential-related code is aligned with caller-provided publishing and authenticated UiPath operations.
Decision evidence
public snapshot- The manifest defines module entrypoints and contains no lifecycle scripts or dependencies.
- The Node bundle exposes project packager and publisher factories rather than executing work at import time.
- Authentication requires a logged-in connection with an access token and UiPath context before workflow configuration is returned.
- The packager bundle copies produced packages to a caller-selected destination.
- The browser helper only exports its application-opening API.
Source & flagged code
8 flagged · loading sourcePackage source references child process execution.
dist/node-wrbrw7qd.jsView on unpkg · L28Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/node-wrbrw7qd.jsView on unpkg · L11442Findings
Affected versions and remediation
This report applies to @uipath/api-workflow-tool@1.202.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.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.