@uipath/conversational-tool@1.202.0
Handle conversations with deployed UiPath conversational processes.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiStatic inspection found a conventional UiPath conversational CLI with user-invoked commands and authenticated service requests. Package metadata contains no lifecycle hook or runtime self-dependency.
Decision evidence
public snapshot- Package metadata exposes a library and an explicit command-line entry point.
- Authentication configuration normalizes the configured service base URL.
- The bundled browser opener requires a string target before invoking its opener.
- The command registration code exposes conversational chat, agent, conversation, exchange, message, trunk, and user-settings commands.
- Service requests use the authenticated session base URL and bearer token for the UiPath conversational API.
Source & flagged code
6 flaggedSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-sz8zdfbv.jsView on unpkg · L4411Authentication configuration normalizes the configured service base URL.
dist/tool-sz8zdfbv.jsView on unpkg · L5967Findings
Affected versions and remediation
This report applies to @uipath/conversational-tool@1.202.0.
See all versions of @uipath/conversational-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/conversational-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.