Repository reports run security analysis against one or more GitHub repositories. Results can include vulnerabilities, weak configurations, and issues that surface as findings for triage.

Creating a repository report

1. Open Reports and click Create report, or go to /app/reports/new.
2. Choose Repository.
3. Select one or more repositories from repos where Superagent Security is installed.
4. Submit to start the scan.

Private repositories require the security app with repository contents access. Public repo scans may be limited to admin users depending on your deployment.

Report detail page

Repository reports open at /app/red-team/repositories/[id]. The detail view includes:

• Scan status and progress
• Sandbox or log access when your deployment provides it
• Linked findings and advisories discovered during the run
• Assignees and status updates for your team's workflow

Relationship to Repository settings

Repository reports use the same GitHub App installation as PR security scans. Configure per-repo checks on the repository detail page; reports are separate long-running analyses.

Scheduled reports

Some deployments support scheduled repository reports via organization configuration. Check with your admin if scans should run on a cadence without manual creation.

Legacy path

/app/red-team/repositories shows the same data as filtering Reports by repository type.

Next steps

• Running reports
• Findings
• Repository