@uipath/conversational-tool@1.204.0
Handle conversations with deployed UiPath conversational processes.
AI Security Review
scanned 16d ago · by lpm-firewall-aiThe flagged Base64 handling decodes JWT claims, while the network and environment references support UiPath authentication and product telemetry. Source inspection found no lifecycle hook or concrete attack behavior.
Decision evidence
public snapshot- package.json exposes the tool module and CLI entrypoint and declares no lifecycle scripts; the CLI registers product commands for invocation.
- Authentication uses the configured authority or UiPath default, constructs its token endpoints from that authority, and rejects non-HTTPS URLs.
- The flagged Base64 decoding reads the payload section of a JWT to parse claims.
- SDK telemetry sends service and account context to UiPath-hosted Application Insights, including organization, tenant, and user identifiers.
- The browser helper selects among known installed browsers as part of its browser-opening support.
Source & flagged code
5 flaggedSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-3m2me0j6.jsView on unpkg · L4619A bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
dist/index-h8cph72k.jsView on unpkgFindings
Affected versions and remediation
This report applies to @uipath/conversational-tool@1.204.0.
See all versions of @uipath/conversational-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/conversational-tool@1.204.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.