← Home

@uipath/maestro-tool

npm Repository Homepage

Create, debug, and run Maestro projects and jobs.

14
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-balintaolteanuipathandreihodoroaga

Keywords

cli-tool

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Both old (aoltean16) and new (aolteanuipath) accounts follow UiPath naming; repo is official UiPath/cli org. Consistent with internal account migration. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers appear to be UiPath org members; consistent with team expansion under official org. ai
maintainer-change maintainer-removed AI (maintainer-change): aoltean16 removed alongside addition of aolteanuipath; consistent with account rename/migration within UiPath org. ai
source-diff encoded-string-file:dist/index.js AI (source-diff): Base64 encodes an Azure App Insights connection string; standard telemetry pattern for this UiPath package. ai
source-diff encoded-string-file:dist/tool.js AI (source-diff): Encoded string is an Azure App Insights connection string for telemetry; standard pattern for this UiPath package. ai

Versions (showing 14 of 14)

Version Deps Published
1.1.0 0 / 16
1.0.4 0 / 16
1.0.2 0 / 16
1.0.0 0 / 16
0.9.1 0 / 15
0.9.0 0 / 15
0.2.0 0 / 10
0.1.14 0 / 10
0.1.12 0 / 6
0.1.11 0 / 6
0.1.10 0 / 6
0.1.9 0 / 6
0.1.7 1 / 10
0.1.5 1 / 4

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.4

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

This version was published by a different npm account than previous versions on 2026-05-15. 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.2

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

This version was published by a different npm account than previous versions on 2026-05-15. 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

1 finding
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. Consider requesting the maintainer enable provenance via CI/CD.

v0.2.0

2 findings
HIGH Long encoded string in modified file: dist/tool.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.1.14

2 findings
HIGH Long encoded string in modified file: dist/tool.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.1.12

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.11

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.10

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.9

1 finding
LOW No provenance attestation provenance

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

v0.1.7

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

Modified file contains 2 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.1.5

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.