The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Create protections against abusive activiy within a GitLab instance. This includes abuse, spam, and other activity for users within a GitLab instance.
Protect GitLab instances from user behavior that disrupts productivity or an organization's ability to build and deploy code.
We make abuse manageable.
Our goal is not to stop abuse. Barriers to stop abusive behavior have an exponentially diminishing rate of return. The more barriers that you impose to stop abuse the more you discourage legitimate usage. As a result, efforts to stop abuse become more costly than the abuse itself. Our goal is to surface abuse before it causes disruption and allow our automated systems, the Trust and Safety team, or the admin of the self-managed instance to take the correct action for that abuse – or correct any action that was taken in error
A number of issues are intentionally confidential despite our value of transparency. This is because we don't want to make it obvious to abusers the exact details of our controls. We aren't relying on "security by obscurity"; however, we also don't want to make it easier for the abusers.
Slack: #g_anti-abuse channel
Last Reviewed: 2021-10-26
Last Updated: 2021-10-26
