@uipath/project-packager@1.201.0
UiPath Project Packager - core library for packing individual UiPath projects
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe high-risk primitives are consistent with a project packager's explicit signing and publishing features, and there is no install-time execution or hidden payload chain. The encoded telemetry setting alone does not establish malicious behavior.
Decision evidence
public snapshot- The bundle includes an encoded telemetry configuration.
- The Node entrypoint invokes dotnet for package signing with shell execution disabled.
- Publishing sends package files and supplied credentials only to caller-provided feed or Orchestrator URLs.
- package.json has no preinstall, install, postinstall, or other lifecycle script.
- The manifest exposes library entrypoints rather than an automatically run binary.
- No self-dependency, remote payload loader, credential harvesting, or destructive action was found.
Source & flagged code
7 flagged · loading sourceThis package version adds a dangerous source file absent from the previous stored version; route for source-aware review.
dist/node.jsView on unpkgFindings
Affected versions and remediation
This report applies to @uipath/project-packager@1.201.0.
See all versions of @uipath/project-packager for other recorded verdicts.
- Review the evidence and your use of @uipath/project-packager@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.