Public and private repositories
Validate repositories included in the authorized GitHub App installation scope.
GitHub repository validation
Continuous GitHub repository security validation for lean teams.
SecOpsium combines an authorized GitHub security scanner workflow with supported repository-control checks, practical prioritization, later validation, and reporting.
Definition
What this capability validates
GitHub access uses a GitHub App. Users select the repository scope in GitHub, and the product requests short-lived installation tokens when an authorized scan needs them.
Current capability
Branch-aware code validation
Select the repository and branch used for a supported code scan.
Supported configuration audit
Run defined GitHub repository-control checks through the provider API.
Manual and scheduled cadence
Run validations on demand or on a supported schedule, then compare history.
Scope and Limits
- SecOpsium can access only repositories included in the GitHub App installation scope.
- GitHub native controls remain important; SecOpsium complements them with a shared validation workflow.
- GitLab uses a different OAuth authorization and credential model.
Frequently Asked Questions
Does SecOpsium ask for a GitHub personal access token?
No. The hosted GitHub workflow uses a GitHub App and short-lived installation tokens.
Can private GitHub repositories be validated?
Yes, when they are included in the authorized GitHub App installation scope.
Is GitLab also supported?
Yes. GitLab code validation uses a separate OAuth-backed workflow with its own coverage and credential model.