@uipath/codedapp-tool
Build, pack, publish, deploy, and manage UiPath Coded Web Applications.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/tool.js | AI (source-diff): Base64 string decodes to an Azure App Insights connection string for telemetry; benign and consistent across UiPath CLI packages. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.0 | 0 / 0 | |
| 1.1.0 | 0 / 16 | |
| 1.0.0 | 0 / 15 | |
| 0.9.1 | 0 / 15 | |
| 0.9.0 | 0 / 15 | |
| 0.2.0 | 0 / 15 | |
| 0.1.14 | 0 / 15 | |
| 0.1.12 | 0 / 11 | |
| 0.1.11 | 0 / 11 | |
| 0.1.10 | 0 / 11 | |
| 0.1.6 | 2 / 7 | |
| 0.1.5 | 2 / 6 |
v1.197.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.196.0
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.