Gitea
Connect Gitea to Safeguard: what it provides, how to set it up, and the frameworks it provides evidence for.
Connect Gitea 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 |
| Gitea's guide | docs.gitea.com |
Connect with an API token
-
In Gitea:
- Sign in to your Gitea instance.
- Go to Settings › Applications (or https://<your-gitea>/user/settings/applications) to open Manage Access Tokens.
- Enter a token name and open Select permissions.
- Grant read:organization, read:repository and read:user.
- Click Generate New Token and copy the token from the message shown above Manage Access Tokens; it is shown only once.
Where to find the other values:
- Instance URL: The https base address of your Gitea server (the host in https://<your-gitea>/user/settings/applications).
- Organization: The organization's name as used in its URL on your Gitea instance (not stated in the fetched docs).
Gitea shows the secret only once, so copy it before you leave the page.
Gitea docs: the token is displayed once in a toast above the Manage Access Tokens dialog and cannot be redisplayed. Verification: the fetched docs do not say the token must be created by an organization owner.
Source: docs.gitea.com, checked 2026-10-07.
The permissions Safeguard needs:
read:organization,read:repository,read:user. Gitea shows some settings only to owners, so create the token as an owner. Safeguard only reads with it. -
On Compliance › Connectors, open Gitea, click Connect, choose API token and fill in:
Field What to enter Instance URL Required. Your own server: an https address reachable from the internet. Access token Required. Stored encrypted and never shown again. Organization Required. -
Click Connect with token.
Frameworks
Safeguard's automated tests read Gitea 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