@uipath/traces-tool@1.202.1
Query execution traces for UiPath jobs
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic inspection shows a normal UiPath CLI with no install lifecycle and network calls bound to the user's logged-in base URL. Bundled browser-open helpers and generated SDK defaults do not run on install or send credentials to a hidden recipient.
Decision evidence
public snapshot- package.json declares a CLI with bin traces-tool and main dist/tool.js and has no preinstall, install, or postinstall scripts.
- dist/index.js builds a commander program and parses process.argv only when the user runs the CLI.
- Span retrieval requires an existing logged-in UiPath session and calls that session base URL with its bearer token.
- child_process imports in dist/index-sby22td6.js come from the bundled open and default-browser helpers, not an install hook.
- No eval, dynamic code load, self-dependency, or lifecycle hook appears in package metadata or entrypoints.
- Orchestrator clients set basePath from the authenticated organization and tenant context rather than a hidden recipient.
Source & flagged code
6 flagged · loading sourceSource decodes a Base64-obscured HTTP endpoint at runtime.
dist/tool-2w2shkbx.jsView on unpkg · L4355Span retrieval requires an existing logged-in UiPath session and calls that session base URL with its bearer token.
dist/tool-2w2shkbx.jsView on unpkg · L12079Findings
Affected versions and remediation
This report applies to @uipath/traces-tool@1.202.1.
See all versions of @uipath/traces-tool for other recorded verdicts.
- Review the evidence and your use of @uipath/traces-tool@1.202.1 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.