How codexeron/projects-triadguard-ci works
TriadGuard-CI runs repository scans on pushes to main and pull requests, then evaluates SARIF findings and reports a verdict on the pull request. The README documents Trivy and CodeQL, with optional SonarQube; the sampled conductor code confirms configuration loading, SARIF aggregation, policy decisions, and GitHub comments and commit statuses. Workflow internals were not sampled, so scanner-to-conductor wiring is shown only at the documented workflow level.
Main entry points: triadguard.yml CI Workflow · conductor.py Conductor · config.yaml Rules Config
Components 10
Scanning
- CI Workflow
.github/workflows/triadguard.yml - Trivy
- CodeQL
- SonarQube
Findings Review
- SARIF Reports
- Conductor
scripts/conductor.py - Rules Config
.triadguard/config.yaml
GitHub Reporting
- GitHub API
Other components
- Push / Pull Request
- Pull Request
Connections 13
- Push / Pull Request → CI Workflow: triggers
- CI Workflow → Trivy: runs scan
- CI Workflow → CodeQL: runs analysis
- CI Workflow → SonarQube: optional scan
- Trivy → SARIF Reports: produces
- CodeQL → SARIF Reports: produces
- SonarQube → SARIF Reports: may produce
- CI Workflow → Conductor: runs
- Conductor → SARIF Reports: reads
- Conductor → Rules Config: loads
- Conductor → GitHub API: posts comment
- Conductor → GitHub API: sets status
- GitHub API → Pull Request: updates