@uipath/flow-tool
Create, debug, and run UiPath Flow projects and jobs.
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 | obfuscated-file:dist/init.js | AI (source-diff): Bundled esbuild output (long lines), not true obfuscation. | ai | |
| source-diff | net-exec-file:dist/init.js | AI (source-diff): Bundler runtime helpers, not a dropper/loader; CLI tool needs dynamic requires. | ai | |
| provenance | publisher-changed | AI (provenance): Change to GitHub Actions is CI/CD provenance improvement, not compromise. | ai | |
| source-diff | encoded-string-file:dist/validation.js | AI (source-diff): Base64 encodes an Azure App Insights connection string for telemetry; benign and stable for this package. | ai | |
| source-diff | encoded-string-file:dist/tool.js | AI (source-diff): Encoded string is an Azure App Insights connection string for telemetry; benign and stable for this UiPath package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.196.1 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.0 | 0 / 0 | |
| 1.1.0 | 0 / 20 | |
| 1.0.4 | 0 / 19 | |
| 1.0.1 | 0 / 16 | |
| 0.9.1 | 0 / 16 | |
| 0.2.0 | 0 / 13 | |
| 0.1.15 | 0 / 13 | |
| 0.1.13 | 0 / 9 | |
| 0.1.12 | 0 / 9 | |
| 0.1.11 | 0 / 9 | |
| 0.1.10 | 0 / 10 | |
| 0.1.5 | 1 / 13 |
v1.197.0
4 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 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.
v1.196.1
4 findingsThis version was published by a different npm account than previous versions on 2026-06-25. This could indicate a legitimate maintainer transition or an account compromise.
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.
v1.0.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.