Ensure an organization’s identity is confirmed with a “Verified” badge

How it is checked

Audit method: Shell command

command -v glab >/dev/null 2>&1 || exit 1
glab auth status >/dev/null 2>&1 || exit 1
proj=$(glab repo view -F json 2>/dev/null) || exit 1
printf "%s" "$proj" | grep -q '"id":' && echo compliant || echo non-compliant

Expected output

compliant

How it is fixed

Fix method: Guidance or infrastructure patch

Step 1: - On the left sidebar, select Search or go to and find your top-level group. - Select Settings > Domain Verification. - In the upper-right corner, select Add Domain. - In Domain, enter the domain name. - In Project, link to a project. - In Certificate: o If you do not have or do not want to use an SSL certificate, leave Automatic certificate management using Let’s Encrypt selected. o Optional. Turn on the Manually enter certificate information toggle to add an SSL/TLS certificate. You can also add the certificate and key later. - Select Add Domain. Step 2: After you create a new domain, the verification code prompts you. Copy the values from GitLab and paste them in your domain’s control panel as a TXT record. Step 3: After you have added all the DNS records: - On the left sidebar, select Search or go to and find your group. - Select Settings > Domain Verification. - On the domain table row, Select Retry verification ().

Check this host

Run this on a machine you are allowed to audit. The scan is read-only.

tmaegis scan --target gitlab --level 2