@uipath/apollo-react
Apollo Design System - React component library with Material UI theming
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; expected for UiPath org automation. | ai | |
| phantom-deps | phantom-dep:d3-scale | AI (phantom-deps): d3-scale is a charting dep consistent with canvas/visualization features in this large component library; bundled output not statically traceable. | ai | |
| phantom-deps | phantom-dep:@tiptap/core | AI (phantom-deps): Tiptap is a rich-text editor; ap-chat and editor components in this library clearly use it; bundled output not statically traceable. | ai | |
| phantom-deps | phantom-dep:@mui/x-date-pickers | AI (phantom-deps): MUI date pickers are consistent with the MUI-based component library scope; bundled output not statically traceable. | ai | |
| phantom-deps | phantom-dep:use-sync-external-store | AI (phantom-deps): Common React state utility; also listed in devDependencies confirming intentional use; bundled output not statically traceable. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.39.3 | 58 / 44 | |
| 4.39.1 | 58 / 44 | |
| 4.39.0 | 58 / 44 | |
| 4.37.1 | 58 / 44 | |
| 4.37.0 | 58 / 44 | |
| 4.36.2 | 58 / 44 | |
| 4.36.1 | 58 / 44 | |
| 4.35.0 | 58 / 44 | |
| 4.34.0 | 58 / 44 | |
| 4.33.0 | 58 / 44 | |
| 4.32.1 | 58 / 44 | |
| 4.32.0 | 58 / 44 | |
| 4.31.1 | 58 / 44 | |
| 4.31.0 | 58 / 44 | |
| 4.30.0 | 58 / 44 | |
| 4.29.1 | 58 / 44 | |
| 4.29.0 | 58 / 44 | |
| 4.28.0 | 58 / 44 | |
| 4.27.0 | 58 / 44 | |
| 4.26.1 | 58 / 44 | |
| 4.25.1 | 58 / 44 | |
| 4.25.0 | 58 / 44 | |
| 4.24.4 | 58 / 44 | |
| 4.23.3 | 58 / 44 | |
| 4.23.2 | 58 / 44 | |
| 4.22.3 | 58 / 44 | |
| 4.22.1 | 58 / 44 | |
| 4.22.0 | 58 / 44 | |
| 4.19.0 | 58 / 44 | |
| 4.18.2 | 58 / 44 | |
| 4.18.1 | 58 / 44 | |
| 4.17.0 | 58 / 44 | |
| 4.16.1 | 58 / 44 |
v4.39.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.39.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.39.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.37.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.37.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.36.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.36.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.35.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.34.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.33.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.32.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.32.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.31.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.31.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.29.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-22. 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.
v4.28.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v4.27.0
2 findingsThis version was published by a different npm account than previous versions on 2026-05-21. 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.
v4.26.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. 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.
v4.25.1
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.
v4.25.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.
v4.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.