@uipath/tasks-tool
Manage Action Center tasks.
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Switch to GitHub Actions publisher reflects CI/CD automation for official @uipath scope. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal scoped tool lacking marketing metadata; not spam indicative. | ai | |
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Base64 encodes an Azure App Insights connection string for telemetry; stable pattern across UiPath packages. | ai | |
| source-diff | encoded-string-file:dist/tool.js | AI (source-diff): Same App Insights connection string pattern; benign telemetry initialization. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.0 | 0 / 0 | |
| 1.1.0 | 0 / 6 | |
| 1.0.4 | 0 / 6 | |
| 1.0.2 | 0 / 6 | |
| 1.0.0 | 0 / 6 | |
| 0.9.1 | 0 / 6 | |
| 0.9.0 | 0 / 6 |
v1.197.0
2 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.
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.
v1.0.2
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.