@uipath/apollo-wind
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
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): New maintainers are ipath-scoped accounts consistent with org team rotation. | ai | |
| provenance | publisher-changed | AI (provenance): UiPath org package migrated to GitHub Actions CI publishing; SLSA attestation confirms pipeline integrity. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of aoltean16 alongside new ipath-scoped maintainers is consistent with org team rotation, not takeover. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-avatar | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this component library. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-select | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this component library. | ai | |
| dependencies | unvetted-dep:@radix-ui/react-hover-card | AI (dependencies): Radix UI is a well-known, widely-trusted primitive library; stable false positive for this component library. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-navigation-menu | AI (phantom-deps): Same as react-toast — bundled component library pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/sortable | AI (phantom-deps): Same as @dnd-kit/core — bundled component library pattern. | ai | |
| phantom-deps | phantom-dep:react-live | AI (phantom-deps): UI component library; deps referenced in config/storybook, not direct imports — stable false positive. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/core | AI (phantom-deps): DnD kit deps used in tree-view component; phantom-dep heuristic misfires on bundled output. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/modifiers | AI (phantom-deps): Same as @dnd-kit/core — bundled component library pattern. | ai | |
| phantom-deps | phantom-dep:@dnd-kit/utilities | AI (phantom-deps): Same as @dnd-kit/core — bundled component library pattern. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-menubar | AI (phantom-deps): Same as react-toast — bundled component library pattern. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Tailwind CSS component library; tailwindcss referenced in config/preset files, not direct imports. | ai | |
| phantom-deps | phantom-dep:@radix-ui/react-toast | AI (phantom-deps): Radix UI component; may be re-exported or used indirectly in bundled output. | ai | |
| phantom-deps | phantom-dep:@uipath/apollo-core | AI (phantom-deps): Same-org dependency; likely used via type imports or re-exports in build output. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 2.18.0 | 55 / 37 | |
| 2.17.0 | 55 / 37 | |
| 2.16.0 | 55 / 37 | |
| 2.15.1 | 55 / 37 | |
| 2.13.0 | 55 / 37 | |
| 2.11.0 | 55 / 37 | |
| 2.10.0 | 55 / 37 | |
| 2.8.0 | 55 / 37 | |
| 2.7.1 | 55 / 37 | |
| 2.7.0 | 55 / 37 | |
| 2.6.0 | 55 / 37 | |
| 2.5.0 | 55 / 37 | |
| 2.4.0 | 55 / 37 | |
| 2.3.0 | 55 / 37 | |
| 2.2.1 | 55 / 37 | |
| 2.2.0 | 55 / 37 | |
| 2.1.1 | 55 / 37 | |
| 2.1.0 | 55 / 37 | |
| 2.0.1 | 55 / 37 | |
| 2.0.0 | 55 / 37 | |
| 1.5.0 | 55 / 37 | |
| 1.4.0 | 55 / 37 | |
| 1.3.0 | 55 / 37 | |
| 1.2.1 | 55 / 37 | |
| 1.2.0 | 55 / 37 | |
| 1.1.0 | 55 / 37 | |
| 1.0.2 | 55 / 37 | |
| 1.0.1 | 55 / 37 | |
| 1.0.0 | 55 / 37 | |
| 0.15.3 | 55 / 37 | |
| 0.15.2 | 55 / 37 | |
| 0.15.1 | 55 / 37 | |
| 0.15.0 | 55 / 37 | |
| 0.14.0 | 55 / 37 | |
| 0.13.0 | 55 / 37 | |
| 0.12.2 | 55 / 37 | |
| 0.12.1 | 55 / 37 | |
| 0.12.0 | 55 / 37 | |
| 0.11.0 | 55 / 37 | |
| 0.10.0 | 47 / 34 | |
| 0.9.1 | 47 / 34 | |
| 0.9.0 | 47 / 34 | |
| 0.8.1 | 47 / 34 | |
| 0.8.0 | 47 / 34 | |
| 0.7.3 | 47 / 34 |
v2.18.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.17.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-19. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.