Skip to main content
Connect Odin to GitHub to push security findings directly to your repository’s issue tracker.

Connecting

1

Open Integrations

Go to Management > Integrations in the sidebar.
2

Connect GitHub

Click Connect next to GitHub and authorise the Borg Security GitHub App.
3

Select your organisation

Choose the GitHub organisation or account that owns your repositories.
4

Choose a repository

Select the repository where issues should be created.
Odin integrations page showing the GitHub connect flow

Pushing a finding

On any finding, click Push to GitHub. Odin creates a GitHub issue with:
  • Finding title as the issue title
  • Severity label (Critical, High, Medium, Low)
  • Full description, reproduction steps, and suggested fix in the issue body
You can push multiple findings at once using the bulk action toolbar on the Findings page.

Auto-ticketing

Auto-ticketing creates GitHub issues automatically when new findings are reported, without any manual action from your team. From the integration settings panel:
  • Issue tracking — toggle on to enable vulnerability tracking via GitHub Issues. When disabled, GitHub is used only for repository access.
  • Auto-create tickets — toggle on to create issues automatically when new findings are reported. When disabled, you can still create issues manually from each finding.
  • Minimum severity — only findings at or above this severity trigger automatic issue creation. Defaults to Medium.
  • Automatic retests — optionally trigger Mjolnir retests when pull requests are merged, to verify that fixes are effective.
Set the minimum severity to High or Critical if you want to keep your GitHub Issues focused on the most urgent findings and handle lower-severity issues manually.

Notes

  • Issues are created in the repository you selected during setup
  • Odin does not update or close GitHub issues automatically. Status management stays in Odin.
  • You can reconnect to a different repository at any time from the Integrations page