@uipath/maestro-tool@1.202.0
Create, debug, and run Maestro projects and jobs.
AI Security Review
scanned 28d ago · by lpm-firewall-aiThis is a user-run UiPath Maestro CLI with no npm lifecycle hooks and no self-install chain. Process spawning and network publish calls are package-aligned and use caller-provided destinations and credentials.
Decision evidence
public snapshot- package.json declares the UiPath Maestro CLI with main and bin entrypoints and no install lifecycle scripts.
- dist/index.js only builds a command program and parses process.argv when the user runs the binary.
- dist/index-h8cph72k.js is the vendored open helper and spawns a local browser command with an argument array.
- dist/node-39h6t9g1.js reads a local UiPath registry analytics id and publishes only to a caller-supplied NuGet or Orchestrator URL using a caller-supplied key.
- dist/elk.bundled-vpsbxz0p.js is the vendored elkjs layout bundle.
- Publish and signing code can send packages and caller-supplied keys to an operator-chosen feed and can spawn dotnet nuget sign, which is expected CLI behavior rather than an install-time attack.
Source & flagged code
7 flagged · loading sourcePackage source references child process execution.
dist/index-h8cph72k.jsView on unpkg · L6Findings
Affected versions and remediation
This report applies to @uipath/maestro-tool@1.202.0.
See all versions of @uipath/maestro-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/maestro-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.