@uipath/solutionpackager-tool-core
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 |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): UiPath-affiliated maintainers added, matches official repo/org context. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Single prior maintainer removed as part of org-internal handoff. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher swap within same UiPath org, repo unchanged. | ai | |
| provenance | no-provenance | AI (provenance): UiPath org package; provenance attestation not yet enabled but no other risk signals present. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.198.0 | 2 / 0 | |
| 1.197.0 | 2 / 0 | |
| 1.196.0 | 2 / 6 | |
| 0.0.33 | 2 / 6 | |
| 0.0.31 | 2 / 6 | |
| 0.0.29 | 2 / 7 | |
| 0.0.26 | 2 / 7 |
v1.198.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.197.0
2 findings[Accepted risk] Package 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-07-07. This could indicate a legitimate maintainer transition or an account compromise.
v1.196.0
2 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.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.