@uipath/maestro-tool@1.201.0
Create, debug, and run Maestro projects and jobs.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiStatic inspection found a normal CLI manifest with no install hook and no self-dependency. The flagged primitives are contained in explicit packaging, publishing, telemetry logging, and bundled dependency code rather than an automatic or covert attack chain.
Decision evidence
public snapshot- The manifest exposes library and CLI entry points and contains no lifecycle scripts.
- The node helper uploads package files only in its explicit publish flow to a caller-supplied destination.
- The telemetry provider records events through local debug logging.
- The large case-schema bundle uses localhost values in its CLI configuration shim.
- The ELK artifact identifies itself as a bundled third-party layout dependency.
- The package includes command execution and network-capable publishing helpers.
- Bundled dependencies contain generic telemetry and fetch code, increasing static-analysis noise.
- No install-time execution, secret harvesting, covert exfiltration, persistence, or self-dependency was found.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/packager-tool-gh6pjm6h.jsView on unpkg · L730Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/packager-tool-gh6pjm6h.jsView on unpkg · L3746Findings
Affected versions and remediation
This report applies to @uipath/maestro-tool@1.201.0.
See all versions of @uipath/maestro-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/maestro-tool@1.201.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.