← Home

@uipath/traces-tool

Fetch LLM Observability traces for UiPath jobs

9
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

qbrandonmihhdutoxiksergiunetvasyopvnaren23chibionosady_mccristiancalinaruud.andriessendanboantaandbalasecatalinb7madalin-turluianucsvancea-uipathpeachfaunmbughiuuipandrei-balintaolteanuipathgabrielavaduvamviton_uiapthandreihodoroaga

Keywords

cli-tool

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publish now via GitHub Actions CI, consistent with legitimate org automation. ai
source-diff encoded-string-file:dist/tool.js AI (source-diff): Base64 string is an Azure Application Insights connection string; telemetry instrumentation pattern stable for this UiPath package. ai

Versions (showing 9 of 9)

Version Deps Published
1.197.0 0 / 0
1.1.0 0 / 6
1.0.4 0 / 6
1.0.2 0 / 6
1.0.0 0 / 6
0.9.1 0 / 6
0.9.0 0 / 6
0.2.0 0 / 6
0.1.0 0 / 3

v1.197.0

2 findings
HIGH Publisher changed: aoltean16 → GitHub Actions (on 2026-07-07) provenance

This version was published by a different npm account than previous versions on 2026-07-07. 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
LOW No provenance attestation provenance

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

INFO Publisher changed: aoltean16 → aolteanuipath (on 2026-05-15) provenance

[Accepted risk] 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.

v1.0.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: aoltean16 → aolteanuipath (on 2026-05-15) provenance

[Accepted risk] 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.