@uipath/vertical-solutions-tool
Scaffold and generate Vertical Solution projects.
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 is an Azure App Insights connection string for telemetry; benign and consistent across UiPath packages. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.0 | 0 / 0 | |
| 1.0.0 | 0 / 10 | |
| 0.9.1 | 0 / 10 | |
| 0.9.0 | 0 / 10 | |
| 0.2.0 | 0 / 11 | |
| 0.1.13 | 0 / 11 | |
| 0.1.11 | 0 / 7 | |
| 0.1.10 | 0 / 7 | |
| 0.1.9 | 0 / 7 | |
| 0.1.7 | 1 / 10 |
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.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.