GitHub Permissions
Ceetrix requests the absolute minimum from GitHub. Here is exactly what we can and cannot access.
What We Request
i
Repository metadataRead-only. The single most minimal GitHub App permission.
What We Can See
✓
Repository nameTo identify which project you are working on
✓
VisibilityWhether the repo is public or private
✓
Primary languageThe main programming language detected by GitHub
✓
TopicsTags you have applied to the repository
✓
OwnerThe GitHub user or organisation that owns the repo
What We Cannot See
✕
Source codeWe have zero access to your files or commits
✕
File contentsWe cannot read, download, or clone your code
✕
Commit historyWe cannot see your diffs, branches, or commit messages
✕
Issues & pull requestsWe cannot read or create issues or PRs
✕
Actions & workflowsWe cannot see or trigger your CI/CD pipelines
✕
Secrets & variablesWe cannot access repository or environment secrets
✕
Branch protection rulesWe cannot see or modify your branch policies
✕
Write operationsWe cannot modify anything in your repository — ever
Why We Need Metadata
When you sign up, Ceetrix verifies you have access to the repository you claim to manage. Repository metadata lets us confirm the repo exists and that your GitHub account has access to it — without ever seeing your code.
That's it. No code scanning, no secret reading, no write operations. Your intellectual property stays entirely on GitHub.