Quick Start
Add to.gitlab-ci.yml:
SAST Integration
GitLab displays SARIF results in the Security Dashboard and merge request widgets when you upload findings as SAST artifacts.Basic SAST job
With severity threshold
allow_failure: true to report findings without blocking the pipeline.
Using Docker
Use the official Aguara Docker image to avoid installation steps:--changed mode works:
Scanning specific paths
.claude/skills/ are modified.
Multiple output formats
Generate both SARIF (for GitLab) and JSON (for custom processing):Custom rules
./custom-rules/.
Pin a specific version
Merge request comments
Post findings as a merge request comment:CI_JOB_TOKEN to have API access (GitLab 14.0+).
Complete pipeline example
- Runs a medium+ scan on merge requests and main (fails on high+)
- Runs a full info-level scan weekly (scheduled)
- Runs an incremental scan on other branches (non-blocking)
Viewing results
Security Dashboard
Findings appear in:- Security & Compliance → Vulnerability Report
- Merge Requests → Security widget
- Pipeline → Security tab
Download SARIF artifact
Troubleshooting
SAST report not appearing
Ensure:- Artifact name is exactly
gl-sast-report.sarif - SARIF file is valid JSON (test:
jq . gl-sast-report.sarif) artifacts.reports.sastis set (not justartifacts.paths)
Job fails with “command not found”
Add install directory to PATH:Large repositories timeout
Increase job timeout or use--changed mode:
Next Steps
GitHub Actions
Integrate with GitHub Actions workflows
Docker
Run Aguara in Docker containers
