PPlatformAppStores

GitLab CI/CD Catalog

Developer Tools

GitLab · Developer tools & code hosting

Best for: Engineering teams that want discoverable, reusable, version-controlled CI/CD building blocks inside GitLab-based development and delivery workflows.

Overview

GitLab CI/CD Catalog is an official directory for discovering reusable CI/CD components. A component is a reusable single pipeline-configuration unit that can provide part of a larger pipeline or compose a complete pipeline. Components may accept input parameters, are listed in the catalog, and can be released and consumed at specific versions. Authors publish components from GitLab projects containing documented YAML configurations, a top-level templates directory, a license, and CI/CD configuration used to test and release them. Consumers add a component with include: component syntax and a fully qualified project path plus version. Catalog content can include third-party material subject to the provider's terms.

How to build & ship

  1. 1Create a GitLab project with a README.md that clearly introduces the component.
  2. 2Add one or more YAML component configurations under the required top-level templates directory.
  3. 3Add a license and configure .gitlab-ci.yml to test the components and release new versions.
  4. 4Publish a release tagged with a semantic version.
  5. 5Consume or verify the published component through include: component using the project path, component name, and version.

Key APIs & SDKs

GitLab CI/CD include: component keyword and fully qualified component reference
GitLab CI/CD component spec: inputs interface
GitLab projects and repositories hosting component projects and templates files
Git tags and releases using semantic versions
GitLab CI/CD pipelines and .gitlab-ci.yml for testing and releasing components

Integration types

Embedded app
Connector
Workflow action

Authentication & security

  • Primary auth: GitLab project and group visibility and access permissions; components are referenced from GitLab CI/CD configuration.
  • Also supports: Component-dependent tokens, passwords, or other sensitive data supplied through CI/CD configuration and secrets.
  • Security review: Not required
  • Operational security review is required when components use tokens, passwords, or sensitive data. GitLab advises auditing component source code and applying minimum required permissions; the sources do not document universal manual approval.
  • Publication is project-based rather than a separately described marketplace application review. Create a compliant component project, document the components, place configurations under templates, add a license, configure CI/CD testing and release, and publish a semantic-versioned release. The sources do not state that every submission receives manual editorial or security approval.
  • Not publicly specified
Auth docs Store policies

Monetization

Free
Onboarding
Not publicly specified
Commission
Not publicly specified
Merchant of Record
Not publicly specified

Pros & cons for builders

Pros

  • Reusable pipeline units can be shared across projects and composed into larger or complete pipelines.
  • Versioned releases, semantic-version selection, and partial-version references support controlled reuse and updates.
  • The catalog exposes GitLab and third-party components for security, scanning, deployment, and infrastructure workflows.

Cons

  • Catalog entries may contain third-party content that GitLab does not control or assume liability for.
  • Components can merge into consumer pipeline configuration, so duplicate names or configuration interactions may produce unexpected behavior.
  • GitLab.com components must be mirrored before use on a GitLab Self-Managed instance.

Frequently asked questions

How do I get my app approved on GitLab CI/CD Catalog?

Publication is project-based rather than a separately described marketplace application review. Create a compliant component project, document the components, place configurations under templates, add a license, configure CI/CD testing and release, and publish a semantic-versioned release. The sources do not state that every submission receives manual editorial or security approval.

What authentication does GitLab CI/CD Catalog use?

GitLab CI/CD Catalog apps primarily authenticate with GitLab project and group visibility and access permissions; components are referenced from GitLab CI/CD configuration., also supporting Component-dependent tokens, passwords, or other sensitive data supplied through CI/CD configuration and secrets..

How is GitLab CI/CD Catalog monetized?

GitLab CI/CD Catalog supports Free. Typical commission: Not publicly specified. Onboarding fee: Not publicly specified.

Is a security review required to list on GitLab CI/CD Catalog?

No, GitLab CI/CD Catalog does not require a formal security review before listing.