← Home

@uipath/integrationservice-sdk

npm Repository Homepage

TypeScript SDK for UiPath Integration Service APIs (Connections and Elements).

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

qbrandonmihhdutoxiksergiunetvasyopvnaren23chibionosady_mccristiancalinaruud.andriessendanboantaandbalasecatalinb7madalin-turluianucsvancea-uipathpeachfaunmbughiuuipandrei-balintaolteanuipathgabrielavaduvamviton_uiapthandreihodoroaga

Keywords

uipathintegrationservicesdk

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from individual account to GitHub Actions CI publisher is consistent with UiPath org automation; repo URL confirms official org ownership. 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): Original maintainer removed as part of org-level CI publishing transition; no takeover indicators. ai
source-diff encoded-string-file:dist/index.js AI (source-diff): Base64 decodes to Azure App Insights connection string; standard telemetry config for UiPath SDK, not obfuscated malware. ai

Versions (showing 9 of 9)

Version Deps Published
1.195.0 0 / 0
1.2.0 0 / 0
1.1.0 0 / 5
1.0.1 0 / 5
0.9.1 0 / 5
0.2.0 0 / 4
0.1.7 0 / 4
0.1.6 1 / 3
0.1.5 1 / 3

v1.195.0

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

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

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

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

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.2.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.1.7

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

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