> ## Documentation Index
> Fetch the complete documentation index at: https://docs.amplify.security/llms.txt
> Use this file to discover all available pages before exploring further.

# Hosted GitLab

> Secure your GitLab projects with Amplify.

## Overview

The Amplify Security Platform integrates with GitLab's CI/CD infrastructure to secure your GitLab
projects and provide actionable security code fixes directly to developers within their merge
requests.

<Note>
  The Amplify Security GitLab integration is currently in beta. Documentation and functionality may
  change frequently.
</Note>

<CardGroup cols={2}>
  <Card title="GitLab Component" icon="circle-play" href="https://gitlab.com/amplify-security/components/">
    View the Amplify Security GitLab Component on GitLab.
  </Card>
</CardGroup>

## Components

### GitLab Component

Amplify provides a GitLab component that must be installed in a GitLab Pipeline for any GitLab
projects added to the Amplify Platform. The following example pipeline configuration runs Amplify's
Runner component on every merge request. Using the `main` branch will ensure you're always using the
latest stable version of the component. Pre-release or experimental versions will never be in `main`.

```yaml .gitlab-ci.yml theme={null}
---
stages: [test]

include:
  - component: gitlab.com/amplify-security/components/runner@main
```

#### Specifying a component version

If you want to specify a particular Amplify component version, you can use our semantic version tags
instead of `main`. For example:

```yaml .gitlab-ci.yml theme={null}
---
stages: [test]

include:
  - component: gitlab.com/amplify-security/components/runner@0.1.0
```

To find the latest tagged version, please refer to the [list of tags on GitLab](https://gitlab.com/amplify-security/components/-/tags).