@uipath/cli
Cross platform CLI for UiPath
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 1.196.4 | 0 / 0 | |
| 1.196.3 | 0 / 0 | |
| 1.196.2 | 0 / 0 | |
| 1.196.1 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.1 | 0 / 0 | |
| 1.195.0 | 0 / 16 | |
| 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 | |
| 0.1.7 | 5 / 4 | |
| 0.1.6 | 5 / 4 | |
| 0.1.5 | 5 / 4 |
v1.196.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.196.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.