Codeberg
Connect Codeberg to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Codeberg to collect version control evidence with automated compliance tests, switched on per workspace.
| Category | Version Control |
| Connect with | API token |
| What a connection produces | Automated compliance tests |
| Codeberg's guide | forgejo.org |
Connect with an API token
-
In Codeberg:
- Sign in to Codeberg.
- Click your profile picture (top right) and select Settings.
- Open the Applications tab.
- Under access tokens, enter a name in Token Name.
- Grant the token read access for organization (read:organization), repository (read:repository) and user (read:user).
- Click Generate token, then copy the token and store it securely.
Where to find the other values:
- Organization: Your organization's name on Codeberg; the fetched docs do not say where it is shown.
Codeberg runs Forgejo; scope names come from Forgejo's token-scope docs, which do not describe the selection UI. Codeberg's page does not cover permissions or required organization roles. It says to copy the token and store it securely but does not state that it cannot be shown again.
Source: docs.codeberg.org, forgejo.org, checked 2026-10-07.
The permissions Safeguard needs:
read:organization,read:repository,read:user. Codeberg shows some settings only to owners, so create the token as an owner. Safeguard only reads with it. -
On Compliance › Connectors, open Codeberg, click Connect, choose API token and fill in:
Field What to enter Organization Required. Access token Required. Stored encrypted and never shown again. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Codeberg and map to the controls below. When a test passes, the result is evidence toward each control it maps to, in every framework listed. It is evidence toward a control, not proof that the control is met on its own.
| Framework | Evidence | Controls | Tests |
|---|---|---|---|
| SOC2 | Automated tests | C1.1, CC6.1, CC6.2, CC6.3, CC8.1 | 6 |
| ISO/IEC 27001 | Automated tests | A.5.15, A.5.16, A.5.18, A.6.5, A.8.2, A.8.4, A.8.25, A.8.32 | 6 |
| HIPAA Security Rule | Automated tests | 164.308(a)(1), 164.308(a)(3), 164.308(a)(4), 164.312(a)(1), 164.312(c)(1) | 6 |
| PCI DSS | Automated tests | 6.5.1, 7.2.1, 7.2.2, 7.2.4, 8.2.5 | 6 |
| NIST CSF 2.0 | Automated tests | PR.AA-01, PR.AA-05, PR.DS-01, PR.PS-01, PR.PS-06 | 6 |
These tests are switched on per workspace by the Safeguard team.
Related
- Version Control connectors
- Compliance connectors: how connecting works, card statuses and multiple accounts
- Connector setup reference: every connector in one table
- Frameworks and connectors: how connectors provide evidence for frameworks