@uipath/docsai-tool@1.202.1
Search UiPath documentation with AI-powered answers.
AI Security Review
scanned 28d ago · by lpm-firewall-aiInspection of package.json and the CLI bundles shows no lifecycle hook and a user-run docs search that uses the login token only against the same configured UiPath base URL. Process spawning is limited to a bundled URL opener and a fixed Windows registry read, which matches the product rather than an attack.
Decision evidence
public snapshot- package.json declares a CLI bin and module entrypoints and has no preinstall, install, or postinstall scripts.
- The ask command sends the stored UiPath login bearer only to an MCP URL built from that same login base URL, organization, and tenant.
- child_process use is the bundled open helper plus a fixed Windows reg query for a UiPath analytics id, not a remote payload.
- The shared auth helper accepts any https authority, including a customer Automation Suite host, so the token destination is not a hard-coded UiPath hostname.
- A large bundled CLI runtime includes schema compilation via Function and local file writes for auth state.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-12cm1ym5.jsView on unpkg · L10908Package source references a known benign dynamic code generation pattern.
dist/tool-12cm1ym5.jsView on unpkg · L4945The ask command sends the stored UiPath login bearer only to an MCP URL built from that same login base URL, organization, and tenant.
dist/tool-12cm1ym5.jsView on unpkg · L22726Findings
Affected versions and remediation
This report applies to @uipath/docsai-tool@1.202.1.
See all versions of @uipath/docsai-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/docsai-tool@1.202.1 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.