@uipath/packager-tool-workflowcompiler-browser@1.200.0
UiPath Workflow Compiler tool - browser implementation
AI Security Review
scanned 13d ago · by lpm-firewall-aiSource inspection found no install-time hooks or concrete attack behavior. Its network calls are tied to invoked workflow compiler operations and use supplied connection details.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and exposes the browser workflow compiler as its package entrypoint.
- Network operations occur when a caller invokes pack or connect, and send the supplied UiPath access token to caller-provided service URLs.
- No concrete malicious behavior was identified in the inspected source.
Source & flagged code
4 flagged · loading sourceThe manifest has no lifecycle scripts and exposes the browser workflow compiler as its package entrypoint.
package.jsonView on unpkg · L1Network operations occur when a caller invokes pack or connect, and send the supplied UiPath access token to caller-provided service URLs.
src/workflow-compiler-tool.tsView on unpkg · L66Findings
Affected versions and remediation
This report applies to @uipath/packager-tool-workflowcompiler-browser@1.200.0.
See all versions of @uipath/packager-tool-workflowcompiler-browser for other recorded verdicts.
- Review the evidence and your use of @uipath/packager-tool-workflowcompiler-browser@1.200.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.