← Home

@uipath/cli

npm Repository Homepage

Cross platform CLI for UiPath

16
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

qbrandonmihhdutoxiksergiunetvasyopvnaren23chibionosady_mccristiancalinaruud.andriessendanboantaandbalasecatalinb7madalin-turluianucsvancea-uipathpeachfaunmbughiuuipandrei-balintaolteanuipathmviton_uiapthandreihodoroaga

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff encoded-string-file:dist/index.js AI (source-diff): Encoded string is an Azure App Insights connection string for telemetry; standard key-hiding pattern, not malicious. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Scoped @uipath/cli is the official UiPath CLI; Levenshtein match to 'joi' is a false positive. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Bun-bundled build; deps may be inlined rather than directly imported at source level. ai
phantom-deps phantom-dep:js-yaml AI (phantom-deps): Bun-bundled build; deps may be inlined rather than directly imported at source level. ai
phantom-deps phantom-dep:applicationinsights AI (phantom-deps): Bun-bundled build; deps may be inlined rather than directly imported at source level. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): Bun-bundled build; deps may be inlined rather than directly imported at source level. ai

Versions (showing 16 of 16)

Version Deps Published
1.1.1 0 / 0
1.1.0 0 / 14
1.0.0 0 / 13
0.9.1 0 / 13
0.9.0 0 / 13
0.2.2 0 / 13
0.2.1 0 / 13
0.2.0 0 / 13
0.1.21 0 / 13
0.1.19 4 / 5
0.1.17 4 / 5
0.1.16 4 / 5
0.1.13 4 / 5
0.1.11 4 / 4
0.1.9 5 / 4
0.1.8 5 / 4

v1.1.1

2 findings
HIGH Publisher changed: aolteanuipath → GitHub Actions (on 2026-06-04) provenance

This version was published by a different npm account than previous versions on 2026-06-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

2 findings
HIGH Publisher changed: aoltean16 → aolteanuipath (on 2026-05-26) provenance

This version was published by a different npm account than previous versions on 2026-05-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.0

2 findings
HIGH Long encoded string in modified file: dist/index.js source-diff

Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.9.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.21

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.19

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.17

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.16

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.13

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aoltean16.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.11

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: aoltean16.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.1.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.1.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.