Branch protection
Check whether the default branch exposes supported branch-protection gaps.
Repository control validation
Continuously validate the repository controls your release process depends on.
SecOpsium's configuration audit reads supported GitHub settings through the authorized integration and turns missing or risky controls into reviewable findings.
Definition
What this capability validates
Repository control validation currently applies to GitHub. It checks a defined set of provider-returned controls; GitLab configuration audit is not currently implemented.
Current capability
Review and push controls
Surface supported missing review requirements or permissive default-branch controls.
Repository posture
Review visibility, SECURITY.md availability, and stale default-branch evidence.
Provider security settings
Report supported GitHub API signals for secret scanning and Dependabot availability.
Scope and Limits
- Configuration audit is currently GitHub-specific.
- A provider permission or API limitation can make a check partial or unavailable.
- The audit is not a complete review of every repository, organization, or CI/CD setting.
Frequently Asked Questions
Which controls are currently checked?
Supported checks include branch protection, required reviews, repository visibility, SECURITY.md, secret-scanning availability, Dependabot availability, and stale default-branch evidence.
Is GitLab configuration audit supported?
No. GitLab currently supports authorized code validation. Repository configuration audit is implemented for GitHub.
Does a passing audit prove the repository is secure?
No. It means the supported controls returned enough evidence for the current checks.