← Home

@uipath/common

npm Repository Homepage
15
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

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): aoltean16 → aolteanuipath is an internal UiPath org account rename/migration, not a takeover. ai
source-diff net-exec-file:dist/index.browser.js AI (source-diff): Standard esbuild browser bundle; net+exec pattern is bundled library code, not dropper malware. ai
phantom-deps phantom-dep:@uipath/telemetry AI (phantom-deps): Same org scope as this package; declared dep, not a phantom risk. ai
source-diff encoded-string-file:dist/index.js AI (source-diff): Base64 decodes to an Azure AppInsights connection string; standard telemetry key embedding pattern for UiPath tooling. ai
phantom-deps phantom-dep:js-yaml AI (phantom-deps): Declared runtime dependency; used via config files, not direct imports. ai
phantom-deps phantom-dep:@jmespath-community/jmespath AI (phantom-deps): Declared runtime dependency; used via config files, not direct imports. ai
phantom-deps phantom-dep:jsonpath-plus AI (phantom-deps): Declared runtime dependency; used via config files, not direct imports. ai

Versions (showing 15 of 15)

Version Deps Published
1.1.0 0 / 8
1.0.4 0 / 8
1.0.2 0 / 8
1.0.0 0 / 8
0.9.1 0 / 8
0.9.0 0 / 8
0.2.0 0 / 8
0.1.15 0 / 8
0.1.13 3 / 4
0.1.12 3 / 4
0.1.10 3 / 4
0.1.8 4 / 3
0.1.7 4 / 3
0.1.6 4 / 3
0.1.5 4 / 3

v1.1.0

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

HIGH New file with network + code execution: dist/index.browser.js source-diff

Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.

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

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

1 finding
LOW No provenance attestation provenance

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

v0.1.15

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

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

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.