Reference

Troubleshooting

Common issues with GitHub Apps, pull request scans, reports, findings, and CLA checks.

GitHub / repositories

Repositories missing after install

  • Confirm the correct app is installed on the right GitHub org or user:
    Superagent Security for scans and repository reports, or
    Open CLA for CLA.
  • Re-select repository access in the GitHub App settings.
  • Open Integrations and verify connection status.
  • Refresh Repository — repos only appear after the app can access them.

No pull request data

  • Ensure Superagent Security has pull request and contents permissions.
  • Open or update a PR on a connected repo to trigger webhooks.
  • Check Pull requests after a few minutes for webhook delivery.

CLA

Check fails for a signed contributor

  • Verify the signature matches the current template version hash on that repository.
  • For org contributions, confirm corporate CLA and org membership read permission on Open CLA.

“Repository not seen by CLA app”

  • Open or update a pull request on the repository first.
  • Confirm Open CLA is installed on that repo and a template is assigned on the repository detail page.

Reports

Repository report not starting

  • Confirm Superagent Security is installed on the target repo with contents access.
  • For private repos, verify the repo appears under Repository with the security capability.

Agent report missing from list

  • Open Reports and search by name; legacy URLs under /app/red-team/agents should still work.

Findings

No findings after a report

  • Not every report produces findings immediately; check report status on the detail page.
  • GitHub advisories require advisory webhook permissions on Superagent Security.

Getting help

  • Review Integrations and the relevant feature doc
  • Use Support in the sidebar footer when available

Next steps