**Background** For large organizations with hundreds or thousands of projects, shared CI components are the backbone of standardization, security, and compliance. CI Catalog Components Analytics turns that backbone from a black box into a measurable, governable system, making it easier to prove that required controls are consistently enforced and that the up-to-date components are rolled out everywhere they matter, providing full visibility on components usage across your GitLab projects ### Target persona Central DevOps team in large organizations ### Problem Central DevOps teams invest heavily in reusable CI components, but once they’re deployed to the Catalog, it’s hard to answer basic questions: Who is using what? where is it used? Which versions are live? What breaks if we change this? CI Catalog Components Analytics gives you a single place to see and manage the impact of shared CI across your entire organization Today, most teams rely on homegrown scripts, spreadsheets, or guesswork to track component usage. That means: * Outdated component versions quietly linger in critical pipelines. * Critical security fixes in components are not consistently adopted downstream, leaving some pipelines running versions with known vulnerabilities. * Required components are missing from some projects and no one notices * Deprecation and removal of old versions is risky and slow * The impact of a change is unknown until something breaks in production ### The solution: CI Catalog Components Analytics CI Catalog Components Analytics centralizes how you see, manage, and evolve your CI components inside GitLab: - See where each component is used, across which projects and pipelines - Quickly identify projects running outdated component versions and understand their risk profile. - Plan upgrades with confidence instead of best guesses. - When you publish a new version or plan a breaking change, you know exactly which teams are affected and can notify them directly, with clear guidance on what to do. - Treat components like products: deprecate, phase out, and remove old versions in a controlled way, while ensuring only supported versions remain in use. ### Design Shipped in 18.9 ~"GitLab Free" {width=722 height=285} A high-level dashboard that tracks overall adoption of each shared CI component across your organization. In progress ETA 19.0 ~"GitLab Ultimate" {width=721 height=600} A detailed view of a single CI component that shows exactly which projects use which versions, so you can target upgrades and notify the right maintainers when deprecating or fixing issues. ### Design board - [Figma for sharing purpose](https://www.figma.com/design/t5Ru4qsAUhiRdnAngkoiow/CI-CD-Catalog---post-GA?node-id=862-15896&t=IjFCfJS1ZYZkzvL1-1) ### Related issues https://gitlab.com/gitlab-org/gitlab/-/issues/208957 https://gitlab.com/gitlab-org/gitlab/-/issues/356724