GitHub
Code & SDLC · GitHub App · Daily
GitHub App auth. Pulls default-branch protection, required PR reviews, CODEOWNERS coverage, plus open Dependabot and secret-scanning alerts at the org level.
- Authentication
- GitHub App
- Sync cadence
- Daily
- Stale threshold
- Every 2 days
- Category
- Code & SDLC
Evidence this connector produces
Every sync writes typed evidence rows linked to the controls below. Evidence is immutable once attached to an approved assessment, fingerprinted for de-dup, and surfaced in the control coverage calculation on your dashboard.
How to connect
Install the ThirdSentry GitHub App in your org, then paste your installation ID + org login.
- 1Install the App
Open the ThirdSentry GitHub App install page (link in our docs) and grant access to the repos you want monitored. We recommend 'All repositories' for full coverage.
- 2Find your installation ID
After installing, GitHub redirects you to a URL containing /installations/<NUMBER>. That number is your installation ID. Copy it.
- 3Note your org login
Your GitHub org's URL slug (e.g. github.com/acme-co → 'acme-co'). Used for org-level Dependabot + secret-scanning queries.
Security model
Every connector ships behind the same auditor-grade primitives — not just RBAC config, but architectural enforcement.
Tokens, client secrets, and service-account keys are encrypted under a per-tenant AWS KMS data key. The plaintext is never persisted, never logged, and never leaves the FastAPI process boundary.
Every Connection, ConnectorRun, and emitted Evidence row carries an organization ObjectId. The scheduler never iterates without an org-scoped filter; cross-tenant evidence bleed is impossible at the data layer.
Connect, sync, sync-failure, re-auth, and revoke each write a row to the immutable AuditLog. The full lifecycle is reconstructable for any examiner.
Revoking a connection sets deletedAt and clears the encrypted credential blob, but the historical evidence + sync log stays queryable for the retention window. Auditors can still trace what was attested when.
If this connector hasn't synced in Every 2 days, control coverage degrades automatically and an alert fires. Auditors don't trust stale evidence — neither do we.
We request the minimum read-only scopes needed for the listed evidence. No write scopes, no admin scopes, no scopes outside the documented set.
Ready to connect GitHub?
Connect from Settings → Integrations — typically under 5 minutes. Or talk to us first.