Collect GitHub repository data into your warehouse
The GitHub connector loads repository details, daily stars and contributors into your own warehouse, so engineering activity can sit next to commercial data.
Available connectors from GitHub
Available connectors from GitHub
- GitHub Connector to ChatGPT3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Claude3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to AWS Athena3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to AWS Redshift3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Databricks3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Google BigQuery3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Snowflake3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to API3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Data Studio3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Google Sheets3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Connector to Microsoft Excel3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Insights to Email3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Insights to Google Chat3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Insights to Microsoft Teams3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
- GitHub Insights to Slack3 endpoints54 fieldsRepository Contributors, Repository Information, Repository Statistics
GitHub Endpoints
3 GitHub endpoints you can import. Each lands in its own table in your warehouse.
Repository Contributors
Contains list of contributors to the repository with their contribution counts
9 fieldsRepository Information
Contains detailed repository information and statistics
42 fieldsRepository Statistics
Contains daily repository statistics including stars and contributors count
3 fields
Repository Contributors schema
GitHub Repository Contributors schema
9 fieldsSchema on GitHubgithub_contributors
Contains list of contributors to the repository with their contribution counts
| Field | Type | Description |
|---|---|---|
login | STRING | Contributor login name |
id | STRING | Contributor ID |
node_id | STRING | Contributor node ID |
avatar_url | STRING | Contributor avatar URL |
gravatar_id | STRING | Contributor gravatar ID |
html_url | STRING | Contributor HTML URL |
type | STRING | Contributor type (User/Bot) |
site_admin | BOOLEAN | Whether the contributor is a site admin |
contributions | INTEGER | Number of contributions to the repository |
GitHub Repository Information schema
42 fieldsSchema on GitHubgithub_repository
Contains detailed repository information and statistics
| Field | Type | Description |
|---|---|---|
id | STRING | Repository ID |
node_id | STRING | Repository node ID |
name | STRING | Repository name |
full_name | STRING | Full repository name (owner/repo) |
private | BOOLEAN | Whether the repository is private |
owner_login | STRING | Repository owner login |
owner_id | STRING | Repository owner ID |
owner_type | STRING | Repository owner type (User/Organization) |
html_url | STRING | Repository HTML URL |
description | STRING | Repository description |
fork | BOOLEAN | Whether the repository is a fork |
created_at | DATE | Repository creation date |
updated_at | DATE | Repository last update date |
pushed_at | DATE | Repository last push date |
homepage | STRING | Repository homepage URL |
size | INTEGER | Repository size in KB |
stargazers_count | INTEGER | Number of stars |
watchers_count | INTEGER | Number of watchers |
language | STRING | Primary programming language |
has_issues | BOOLEAN | Whether the repository has issues enabled |
has_projects | BOOLEAN | Whether the repository has projects enabled |
has_downloads | BOOLEAN | Whether the repository has downloads enabled |
has_wiki | BOOLEAN | Whether the repository has wiki enabled |
has_pages | BOOLEAN | Whether the repository has pages enabled |
has_discussions | BOOLEAN | Whether the repository has discussions enabled |
forks_count | INTEGER | Number of forks |
archived | BOOLEAN | Whether the repository is archived |
disabled | BOOLEAN | Whether the repository is disabled |
open_issues_count | INTEGER | Number of open issues |
license_key | STRING | Repository license key |
license_name | STRING | Repository license name |
allow_forking | BOOLEAN | Whether forking is allowed |
is_template | BOOLEAN | Whether the repository is a template |
web_commit_signoff_required | BOOLEAN | Whether web commit signoff is required |
topics | STRING | Repository topics (comma-separated) |
visibility | STRING | Repository visibility (public/private) |
forks | INTEGER | Number of forks |
open_issues | INTEGER | Number of open issues |
watchers | INTEGER | Number of watchers |
default_branch | STRING | Default branch name |
network_count | INTEGER | Network count |
subscribers_count | INTEGER | Number of subscribers |
GitHub Repository Statistics schema
3 fieldsSchema on GitHubgithub_repository_stats
Contains daily repository statistics including stars and contributors count
| Field | Type | Description |
|---|---|---|
date | DATE | Date of the data snapshot |
stars | INTEGER | Number of stars for the repository |
contributors | INTEGER | Number of contributors to the repository |
Why Collect GitHub Data Into Your Warehouse With OWOX?
Engineering activity usually lives in a separate tool from revenue and marketing. The GitHub connector loads repository data into the same warehouse as your commercial data, so delivery can be reported next to revenue instead of in another dashboard.
Collect to your warehouse
The data lands in your warehouse, not in OWOX, so you own it. Every connector is included in every OWOX Cloud plan, with no per-connector bill.
Zero-maintenance syncs
The connector is open source under the MIT license, so you can read the code. A Connector Trigger runs it on the schedule you set.
Full-funnel joins
Join repository data to your commercial data in a Data Mart. The SQL behind every join stays visible.
R01 · Collect
Collect All Your GitHub Data With Zero Engineering
The connector has three endpoints, each landing in its own table.
- Repository Information has 42 fields and lands in
github_repository. It covers the repository’s name, owner, description, language, license, creation, update and push dates, size, stars, watchers, forks and open issues, and flags such as private, fork, archived and template. - Repository Statistics has 3 fields and lands in
github_repository_stats. It holds a date, the number of stars and the number of contributors. - Repository Contributors has 9 fields and lands in
github_contributors. It lists each contributor’s login, type (user or bot) and number of contributions.
Between them the three tables show how large a repository is, how fast it is growing and who contributes. The contributor type field marks users and bots, so you can leave bots out of a headcount.
Authentication is an access token. Generate a personal access token on GitHub. You need one to read private repositories. To start:
- Add a storage to receive the data: Google BigQuery, Snowflake, AWS Redshift, AWS Athena or Databricks.
- Create a Connector Data Mart and choose GitHub as the platform.
- Add your access token for private repositories, publish the Data Mart and run it for the first import.
- Add a Connector Trigger to schedule recurring imports.
The connector documentation has the full setup guide.
R02 · Report
Build Reports With GitHub Data That Everyone Trusts
Once the data is in your warehouse, it behaves like any other table you own. Analysts define the Data Marts, and business users read the results in the tools they already open.
- Chart stars and contributors over time from the Repository Statistics table.
- Rank contributors by
contributionsfrom the Repository Contributors table. - Track forks, watchers and open issues over refreshes from the Repository Information table.
- Filter out archived repositories and forks with the
archivedandforkflags. - Join repository data to your commercial data in a Data Mart, so delivery sits next to revenue.
- Keep the SQL behind each number one click away.
R03 · Why OWOX
Deliver GitHub Data to the Tools Your Team Uses
A Report delivers one Data Mart to one destination, and each Data Mart can feed many destinations.
- Push mode: OWOX writes the data on a manual or scheduled run. Google Sheets, email, Slack, Microsoft Teams and Google Chat work this way.
- Pull mode: the tool asks OWOX for the data when a user refreshes it. Data Studio and Microsoft Excel work this way.
- AI assistants such as Claude and ChatGPT read the Data Mart, not the raw tables, so answers use your definitions.
Why Use OWOX Connectors to Collect Your GitHub Data?
Engineering next to commerce
Repository activity and commercial data sit in one warehouse, ready to join.
Your data stays yours
The data sits in a warehouse you own. OWOX does not keep a copy.
Private repositories supported
An access token lets the connector read private repositories.
Scheduled, not manual
A Connector Trigger refreshes the tables on your schedule, so nobody exports numbers by hand.
Readable by anyone
The connector code is open source, so you can see exactly what it fetches.
Define once, reuse everywhere
One Data Mart feeds Sheets, Excel, Data Studio and AI assistants.
History you keep
Each refresh lands in your warehouse, so the history is yours rather than a snapshot in someone else’s tool.
Free of per-connector cost
All connectors are included in every OWOX Cloud plan.
Not testimonials. Comment threads.
Real things real customers said — each quote pinned to a specific claim, straight from the quotes database.
“AI, by the nature of the models, will hallucinate. And because of that, you need something which will create guardrails to ensure that there are no hallucinations, that you can trust your data.”
“We had six or seven different channels and no single source of truth — it was almost impossible, a lot of guesswork.”
“We regained time. And time is the one resource that never comes back.”
Start collecting GitHub data
Add the connector with an access token, pick the fields and set a schedule.
- Internal OWOX data as of 2026-10-02
- G2 reviews of OWOX
- npm installs stat


