Skip to content

Connect

Connect GitHub

Give scans your real route list, point findings at the file to fix, and scan your code.

With a repository connected, scans test the routes that actually exist in your code, and each finding shows the file and handler to change.

Connect a repository#

  1. Open Project settings → Codebase and choose Install.
  2. On GitHub, pick your account or organisation and grant access to the repositories you want scanned. You can limit it to just one.
  3. Back in AuditGate, choose the repository for this project.
  4. Wait for indexing to finish. It shows progress, and you can retry if it fails.

Developer plans include 3 connected repositories and Startup plans 10, counted across all your workspaces. Each project connects to one repository.

What you get#

  • Scans test your real routes instead of guessing common paths.
  • Findings point at the file and handler.
  • Role checks use the roles your code actually requires.
  • Code scanning for hard-coded secrets, unsafe patterns, weak cryptography, infrastructure misconfigurations and vulnerable dependencies.
  • Fix guidance that refers to your actual code.

Staying up to date#

Every push to your default branch re-indexes the repository automatically. Other branches are ignored.

If something's wrong#

  • Repository not listed: grant the AuditGate app access to it in your GitHub settings.
  • Indexing failed: retry from the Codebase card. Large repositories can take a few minutes.
  • Codebase is locked: your plan doesn't include GitHub, or you've used all your repository connections.