registry / @uipath/docsai-tool / 1.200.0
@uipath/docsai-tool@1.200.0
Search UiPath documentation with AI-powered answers.
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection found a normal CLI entry point and an explicit documentation-search command. Authentication is required before the token is used for the constructed service request, and no malicious behavior was identified.
Static reason
One or more suspicious static signals were detected.
Trigger
A user runs the command-line tool and invokes its ask command.
Impact
No unconsented installation action, persistence, destructive behavior, or confirmed credential exfiltration was found.
Mechanism
The command obtains an existing UiPath login status and sends the supplied query through an MCP client.
AI rationale
Static inspection found a normal CLI entry point and an explicit documentation-search command. Authentication is required before the token is used for the constructed service request, and no malicious behavior was identified.
Decision evidence
public snapshotAI called this Clean at 93.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a library entry point and a command-line binary, with no lifecycle hook declared.
- The tool registers an explicit `ask` command that submits the supplied question to a documentation-search tool.
- The client requires an existing logged-in session before it can run.
- The access token is attached to an MCP request constructed from the session base URL, organization, and tenant.
- The auxiliary browser utility launches an assembled command with explicit arguments rather than evaluating source text.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetwork
HighEntropyStringsUrlStrings
Source & flagged code
7 flagged · loading sourcedist/tool-ja8rhmbw.jsView file
738var EventEmitter = __require("node:events").EventEmitter;
L739: var childProcess = __require("node:child_process");
L740: var path = __require("node:path");
High
Child Process
Package source references child process execution.
dist/tool-ja8rhmbw.jsView on unpkg · L73820Cross-file remote execution chain: dist/tool-ja8rhmbw.js spawns dist/tool-hxjzwxa7.js; helper contains network access plus dynamic code execution.
L20: class CommanderError extends Error {
L21: constructor(exitCode, code, message) {
L22: super(message);
...
L738: var EventEmitter = __require("node:events").EventEmitter;
L739: var childProcess = __require("node:child_process");
L740: var path = __require("node:path");
...
L784: this._outputConfiguration = {
L785: writeOut: (str) => process2.stdout.write(str),
L786: writeErr: (str) => process2.stderr.write(str),
...
L4276: id = normalizeId(id);
L4277: return resolver.resolve(baseId, id);
L4278: }
High
Cross File Remote Execution Context
Source spawns a local helper that also contains network and dynamic execution context; review data flow before blocking.
dist/tool-ja8rhmbw.jsView on unpkg · L2015001var telemetryInstanceSlot = singleton("TelemetryService");
L15002: var DEFAULT_AI_CONNECTION_STRING = atob("[redacted]...
L15003: function getGlobalTelemetryInstance() {
Findings
4 High2 Medium6 Low
HighChild Processdist/tool-ja8rhmbw.js
HighCross File Remote Execution Contextdist/tool-ja8rhmbw.js
HighBase64 Obscured Urldist/tool-ja8rhmbw.js
HighSemantic Analysis Limiteddist/tool-hxjzwxa7.js
MediumNetwork
MediumEnvironment Vars
LowEvaldist/tool-ja8rhmbw.js
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowSuspicious Lifecycle Evidencepackage.json
LowAi Review Evidencedist/tool-ja8rhmbw.js
Affected versions and remediation
This report applies to @uipath/docsai-tool@1.200.0.
See all versions of @uipath/docsai-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/docsai-tool@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.