@uipath/project-packager@1.202.0
UiPath Project Packager - core library for packing individual UiPath projects
AI Security Review
scanned 28d ago · by lpm-firewall-aiStatic review shows a normal UiPath project-packaging library with no lifecycle scripts and no self-install chain. Process execution and authenticated requests are limited to caller-invoked packing, signing, and publishing.
Decision evidence
public snapshot- package.json declares a UiPath library at 1.202.0 with ESM exports and no install lifecycle scripts or self-dependency.
- dist/node.js only exports packager factories and services and does not run packing or publishing at import.
- The fixed dotnet version check and later process launches sit inside caller-invoked discovery, signing, and publish methods.
- Bearer tokens and NuGet API keys are sent only to caller-supplied cloud or feed URLs during explicit publish or policy download.
- Bundled open-helper process calls target local OS launchers and are not install hooks.
Source & flagged code
6 flagged · loading sourceFindings
Affected versions and remediation
This report applies to @uipath/project-packager@1.202.0.
See all versions of @uipath/project-packager for other recorded verdicts.
- Review the evidence and your use of @uipath/project-packager@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.