How SecOpsium scans, stores, scores, and reports.
These docs are written for founders, engineers, and security reviewers who need direct answers about how SecOpsium handles code, GitHub access, findings, severity, reports, and the open-source CLI.
Scanning Model
How SecOpsium turns authorized repository access into scan findings, severity, fix queues, and reports.
GitHub Permissions
How SecOpsium explains GitHub authorization, repository scope, private repository access, and safe usage boundaries.
Code Retention
What SecOpsium stores, what it avoids retaining, and how scan data is separated from full source-code retention.
Severity Scoring
How SecOpsium explains severity, grade impact, fix order, and the limits of scoring security findings.
Security Reports
How SecOpsium reports summarize supported findings, grade context, remediation guidance, and progress.
Detection Rules
How SecOpsium describes supported detection coverage for secrets, repository posture, and exposure-oriented findings.
Open-Source CLI
How the open-source SecOpsium CLI supports local checks while the SaaS adds hosted workflows, reports, and collaboration.