SigilbaseGitHub audit logs, sealed as they arrive.
Sigilbase will collect audit logs, delivered events and configuration snapshots from GitHub into a chained, signed ledger: every collection receipted, every gap declared, and evidence your auditor verifies offline without an account.
Named connectors ship in waves, and GitHub is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today.
- Status. First wave.
- Collected by. A connector Sigilbase runs.
- Connects with. GitHub App (read-only permissions).
- Category. Code hosting, CI/CD and software supply chain.
What can be ingested from GitHub
Each stream below becomes its own sequence in the ledger, with the record kept exactly as GitHub gives it and a hash of those bytes beside it. Snapshots are read on a cadence and the differences between them dated.
-
Event stream
Org/enterprise audit log.
-
Delivered by the source
Audit log streaming (Enterprise, reconciled).
-
Delivered by the source
Webhooks (push, pull_request, deployment, branch_protection_rule, repository_ruleset, member, team).
-
Snapshot
Repos (visibility), branch protection + rulesets, org members/owners, outside collaborators, 2FA requirement, Actions permissions, deploy keys (metadata), Dependabot/code scanning/secret scanning alerts.
How it will be collected
When its connector ships, a connector Sigilbase runs will read GitHub on a schedule you set.
GitHub keeps this log for a limited time. The connector will collect continuously rather than on request, and warn you while a declared gap can still be backfilled from the source.
Stream and credential names follow the vendor's documentation as read in October 2026; the connector's build confirms them.
The evidence model
What every connector and receiver ships with, whatever the source:
- A receipt per collection: what was asked for, what arrived, the cursor before and after
- A declared gap for any interval nothing covers, never a blank
- A daily settlement once late records can no longer arrive
- The raw record, byte for byte, with its hash
- An evidence bundle anyone can verify offline
What you get
-
Sealed as it arrives
Every record is hashed and chained to the one before; every few minutes the chain is sealed into a signed checkpoint. A changed, deleted or reordered record fails verification at that exact point.
-
Continuity you can show
The receipts chain too, so an auditor sees not only the records but that nothing between them went uncollected, and where a gap was, that it was declared.
-
Verified without us
An export carries the open-source verifier. It runs offline, checks the chain, the receipts and the gaps, and needs no Sigilbase account. How the service is run.
Questions about GitHub
-
Does Sigilbase support GitHub?
Named connectors ship in waves, and GitHub is in the first. Until then, anything that can send JSON reaches Sigilbase through the events API today. Whatever arrives is written to a chained, signed ledger whose evidence anyone can verify offline with the open-source verifier, without a Sigilbase account.
-
What GitHub data can Sigilbase ingest?
Event stream: Org/enterprise audit log. Delivered by the source: Audit log streaming (Enterprise, reconciled). Delivered by the source: Webhooks (push, pull_request, deployment, branch_protection_rule, repository_ruleset, member, team). Snapshot: Repos (visibility), branch protection + rulesets, org members/owners, outside collaborators, 2FA requirement, Actions permissions, deploy keys (metadata), Dependabot/code scanning/secret scanning alerts.
-
How will GitHub evidence be collected and verified?
When its connector ships, a connector Sigilbase runs will read GitHub on a schedule you set. Every collection will be receipted in the connection's own stream: what was asked for, what arrived, and the cursor before and after. An interval nothing covers will be declared as a gap, never left blank. Exports carry the standalone verifier, which checks the chain, the receipts and the gaps offline.
-
How long does GitHub keep this log?
A limited time, which is why the connector will collect continuously rather than on request, and warn you while a declared gap can still be backfilled from the source.
Start recording provable history
Chained, sealed, independently verifiable audit logs, from the first event. Free while Sigilbase is in beta.
Questions first? Write to hello@sigilbase.io.