@uipath/maestro-tool@1.202.2
Create, debug, and run Maestro projects and jobs.
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe published metadata has no install lifecycle and points at a commander-based CLI plus an ELK layout bundle. Risky-looking child_process imports sit in user-run tooling, not an automatic install chain.
Decision evidence
public snapshot- package.json exposes a module CLI (main dist/tool.js, bin maestro-tool to dist/index.js) and has no preinstall, install, or postinstall scripts.
- dist/packager-tool-79gws1zn.js bundles the commander library and exports Command for the user-run CLI.
- dist/elk.bundled-vpsbxz0p.js is the Eclipse Layout Kernel graph layout bundle and constructs ELK only with a worker URL and factory.
- Some other dist chunks import node:child_process, which is consistent with a user-invoked CLI rather than an install-time hook.
Source & flagged code
4 flagged · loading sourcePackage source references a known benign dynamic code generation pattern.
dist/index.umd.min-fqefd9kn.jsView on unpkg · L1834Source decodes a Base64-obscured HTTP endpoint at runtime.
dist/packager-tool-79gws1zn.jsView on unpkg · L4104Findings
Affected versions and remediation
This report applies to @uipath/maestro-tool@1.202.2.
See all versions of @uipath/maestro-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/maestro-tool@1.202.2 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.