@uipath/solution-tool
Create, pack, publish, and deploy UiPath Automation Solutions.
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Org account transition to CI publishing for official UiPath package. | ai | |
| source-diff | obfuscated-file:dist/pack.js | AI (source-diff): Bundled esbuild output, not true obfuscation; official UiPath CLI tool. | ai | |
| source-diff | obfuscated-file:dist/resource.js | AI (source-diff): Bundled esbuild output, not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/deploy.js | AI (source-diff): Bundler preamble; deploy tool legitimately needs network+exec for its stated function. | ai | |
| source-diff | net-exec-file:dist/pack.js | AI (source-diff): Bundled build output, expected for CLI packaging tool. | ai | |
| source-diff | net-exec-file:dist/publish.js | AI (source-diff): Bundled build output, expected for CLI publish tool. | ai | |
| source-diff | net-exec-file:dist/resource.js | AI (source-diff): Bundled build output, expected for CLI resource tool. | ai | |
| source-diff | encoded-string-file:dist/tool.js | AI (source-diff): Base64 string is an Azure App Insights connection string for telemetry; benign and consistent with UiPath tooling patterns. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.1.0 | 0 / 18 | |
| 1.0.0 | 0 / 17 | |
| 0.9.1 | 0 / 16 | |
| 0.9.0 | 0 / 16 | |
| 0.2.0 | 0 / 17 | |
| 0.1.14 | 0 / 17 | |
| 0.1.12 | 1 / 12 | |
| 0.1.11 | 1 / 12 | |
| 0.1.10 | 1 / 12 | |
| 0.1.9 | 1 / 11 | |
| 0.1.5 | 2 / 11 |
v1.197.0
8 findingsThis 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.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package 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.