registry / @uipath/project-packager / 1.203.0
@uipath/project-packager@1.203.0
UiPath Project Packager - core library for packing individual UiPath projects
AI Security Review
scanned 12d ago · by lpm-firewall-aiThe static indicators resolve to a base64-encoded Azure telemetry connection string and package-aligned .NET tooling; the inspected telemetry provider logs events locally, and the endpoint constant has no use in the bundle. The manifest exposes library entry points and declares no install lifecycle hook.
Static reason
One or more suspicious static signals were detected.
Trigger
Importing the package exposes library entry points; .NET checks and signing run when those features are invoked.
Impact
No confirmed attack surface was established from the inspected source.
Mechanism
The observed process calls check the .NET installation or invoke dotnet for package signing; telemetry in the inspected Node code logs locally.
AI rationale
The static indicators resolve to a base64-encoded Azure telemetry connection string and package-aligned .NET tooling; the inspected telemetry provider logs events locally, and the endpoint constant has no use in the bundle. The manifest exposes library entry points and declares no install lifecycle hook.
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes library entry points and has no install lifecycle hook.
- The decoded endpoint constant is not used by the inspected code; telemetry events in the Node bundle are logged locally.
- The inspected process execution checks the installed .NET version and is used for package signing with shell disabled.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsEvalFilesystemNetworkShell
HighEntropyStringsUrlStrings
NoLicense
Source & flagged code
5 flagged · loading sourcedist/node.jsView file
1396import { promisify } from "node:util";
L1397: import childProcess from "node:child_process";
L1398: import { promisify as promisify2 } from "node:util";
High
1539var execFile;
L1540: var powerShellPath = () => `${process3.env.SYSTEMROOT || process3.env.windir || String.raw`C:\Windows`}\\System32\\WindowsPowerShell\\v1.0\\powershell.exe`;
L1541: var executePowerShell = async (command, options = {}) => {
High
1396Cross-file remote execution chain: dist/node.js spawns dist/browser.js; helper contains network access plus dynamic code execution.
L1396: import { promisify } from "node:util";
L1397: import childProcess from "node:child_process";
L1398: import { promisify as promisify2 } from "node:util";
...
L1563: ];
L1564: executePowerShell.encodeCommand = (command) => Buffer2.from(command, "utf16le").toString("base64");
L1565: executePowerShell.escapeArgument = (value) => `'${String(value).replaceAll("'", "''")}'`;
...
L1602: const command = String.raw`(Get-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\Shell\Associations\UrlAssociations\http\UserChoice").ProgId`;
L1603: const { stdout } = await executePowerShell(command, { powerShellPath: psPath });
L1604: return stdout.trim();
...
L1808: var
Findings
4 High2 Medium6 Low
HighChild Processdist/node.js
HighShelldist/node.js
HighCross File Remote Execution Contextdist/node.js
HighBase64 Obscured Urldist/node.js
MediumNetwork
MediumEnvironment Vars
LowEval
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowNo License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @uipath/project-packager@1.203.0.
See all versions of @uipath/project-packager for other recorded verdicts.
- Review the evidence and your use of @uipath/project-packager@1.203.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.