@uipath/docsai-tool@1.202.0
Search UiPath documentation with AI-powered answers.
AI Security Review
scanned 28d ago · by lpm-firewall-aiInspection shows a UiPath documentation CLI with no lifecycle hooks and network use limited to the caller’s authenticated UiPath authority. Bundled process execution is the open helper and a local Windows registry read, which matches the product.
Decision evidence
public snapshot- package.json is a module CLI with main and bin under dist and no install lifecycle scripts.
- The ask command sends the caller query to SearchDocumentation only after a logged-in session.
- The docs MCP URL is built from the authenticated UiPath base URL, organization id, and tenant.
- child_process use is the bundled open helper plus a Windows registry query, not a hidden installer.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-xrkfnz4j.jsView on unpkg · L10908Package source references a known benign dynamic code generation pattern.
dist/tool-xrkfnz4j.jsView on unpkg · L4945The docs MCP URL is built from the authenticated UiPath base URL, organization id, and tenant.
dist/tool-xrkfnz4j.jsView on unpkg · L22686Findings
Affected versions and remediation
This report applies to @uipath/docsai-tool@1.202.0.
See all versions of @uipath/docsai-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/docsai-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.