@uipath/data-fabric-tool
Manage Data Fabric entities and records.
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): CI/CD publisher (GitHub Actions) with consistent UiPath maintainer roster. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are UiPath team members, consistent with official org. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Single maintainer removed as part of normal team transition. | 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 this package's versions. | ai | |
| source-diff | encoded-string-file:dist/tool.js | AI (source-diff): Same Azure App Insights connection string pattern as dist/index.js; benign telemetry use. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 1.197.0 | 0 / 0 | |
| 1.196.0 | 0 / 0 | |
| 1.195.0 | 0 / 0 | |
| 1.1.0 | 0 / 7 | |
| 1.0.4 | 0 / 7 | |
| 1.0.1 | 0 / 7 | |
| 0.9.1 | 0 / 7 | |
| 0.9.0 | 0 / 7 |
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.196.0
2 findingsThis version was published by a different npm account than previous versions on 2026-06-22. 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.