Create new gitlab module for scorecard

[christoph-jerolimov]

Scorecard is a backstage plugin and supports multiple metric, grouped as modules in folder workspaces/scorecard/plugins.

There are already modules that support GitHub, OpenSSF, SonarQube. Add a new module for GitLab, called gitlab.

Similar to the github module it should use the existing Backstage scm configuration for gitlab.

All metrics providers should filter for entities with annotation gitlab.com/project-slug.

For these entities it should call the GitLab API to populate these metrics.

These for issues and merge requests:

1. Open issues (current count)
2. Opened issues that was opened in the last 7 days
3. Closed issues that was closed in the last 7 days
4. Open merge requests (current count)
5. Opened merge request that was opened in the last 7 days
6. Closed merge requests was was closed or merged in the last 7 days

These for pipelines and jobs:

7. Number of started pipelines and jobs in the last 7 days.
8. Number of successfully finished pipelines and jobs in the last 7 days. Ignore these which are pending, running, canceled, etc.9, Number of failed pipelines and jobs in the last 7 days. Ignore these which are pending, running, canceled, etc.
9. Two metrics for Ratio of successful vs successful+failed pipelines and jobs, once for the last 7 days and one for the last 24 hours. Ignore these which are pending, running, canceled, etc.

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 1:01 PM UTC · Completed 1:03 PM UTC
Commit: 7ccaff1 · View workflow run →

[fullsend-ai-triage]

Triage Summary

Category: Feature · Severity: Medium

Problem

The scorecard plugin supports GitHub, OpenSSF, SonarQube, and other providers but has no GitLab integration. Entities annotated with gitlab.com/project-slug cannot receive scorecard metrics.

Recommended Approach

Create a new scorecard-backend-module-gitlab plugin under workspaces/scorecard/plugins/, following the existing scorecard-backend-module-github as a pattern. The module should:

1. Use Backstage SCM configuration for GitLab API access
2. Filter for entities with the gitlab.com/project-slug annotation
3. Implement ~10 metrics providers covering issues, merge requests, pipelines, and jobs

Proposed Test Case

Unit tests per metrics provider:
- Mock GitLab API responses for /projects/:id/issues, /merge_requests, /pipelines, /jobs
- Verify correct date-range filtering (last 7 days, last 24 hours)
- Verify status filtering (exclude pending/running/canceled for pipeline/job metrics)
- Verify correct count aggregation

Integration test:
- Verify module registers with scorecard backend
- Verify only entities with gitlab.com/project-slug annotation are processed
- Verify entities without the annotation are skipped

The issue is well-specified and ready for implementation. Existing modules provide clear patterns to follow.

---

Labels: This feature request targets the scorecard workspace with a new GitLab module.

[christoph-jerolimov]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ✅ Success · Started 1:12 PM UTC · Completed 1:51 PM UTC
Commit: 7ccaff1 · View workflow run →