# Extract projects with public visibility in GitLab

> A weekly run lists GitLab projects set to public or internal visibility with their owners so exposure drift is caught on a schedule.

Source: https://stepwork.com/marketplace/extract-projects-with-public-visibility-in-gitlab

Automatically extract GitLab projects with public or internal visibility every week with Stepwork, so code exposure is caught before it spreads.

**Apps:** GitLab
**Starts with:** Weekly schedule
**Use case:** Security monitoring
**Best for:** Security Engineer
**Applications used:** GitLab
**Business outcome:** Risk reduction

## Visibility drift is found by accident.

A project flips to public or internal during a demo, a fork, or a hurried setting change. Nobody is assigned to re-check visibility every week.

Security learns when a scanner, a customer, or a reporter spots it. By then the exposure window is already open.

## Code exposure via visibility settings caught weekly

Stepwork extracts projects set to public or internal visibility with their owners into one report. The run records when it ran and how many projects matched.

- The check runs every week on its own.
- Public and internal projects are listed with owners.
- Private-only projects are left out of the report.

## From weekly schedule to a GitLab visibility report

Every week, Stepwork reviews project visibility settings in GitLab and extracts the ones that are public or internal.

1. **Start on schedule** (Stepwork): The run starts every week on its own. Nobody has to remember to open the project settings list.
2. **List the projects** (GitLab): Stepwork signs in to GitLab and walks the groups and projects in scope for the visibility check.
3. **Extract public and internal** (GitLab): Stepwork extracts projects set to public or internal visibility with their owners into one table.
4. **Confirm and deliver** (Slack): Stepwork checks that the extract finished, then delivers the report to the security channel or destination you recorded.

## Visibility review stays on the path you recorded

Stepwork runs the GitLab visibility extract path you recorded. Exposure checks happen on a schedule instead of after a surprise.

## Questions

**Q: How do I find GitLab projects with public visibility automatically?**
Schedule the weekly run. Stepwork lists public and internal projects with their owners and delivers the report.

**Q: Does this change project visibility?**
No. It only extracts the list. Someone still decides which projects should be locked down.

**Q: Is there a similar check for cloud storage?**
Yes. Extracting publicly accessible storage buckets in Google Cloud Platform is a related exposure report.

---

This is the Markdown version of https://stepwork.com/marketplace/extract-projects-with-public-visibility-in-gitlab, built from the same copy as the page. Everything about Stepwork for AI tools: https://stepwork.com/llms.txt. Book a demo: https://calendly.com/shaun-maclellan/1-1-w-shaun-stepwork
