Data source

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.

Get started free

Available connectors from GitHub

Available connectors from GitHub

Endpoints

GitHub Endpoints

Documentation

3 GitHub endpoints you can import. Each lands in its own table in your warehouse.

Trust

Data Partner You Can Trust

users

176K1

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

165K3

In Open Source We Trust

Customers

Repository Contributors schema

GitHub Repository Contributors schema

9 fieldsSchema on GitHubgithub_contributors

Contains list of contributors to the repository with their contribution counts

GitHub Repository Contributors fields
FieldTypeDescription
loginSTRINGContributor login name
idSTRINGContributor ID
node_idSTRINGContributor node ID
avatar_urlSTRINGContributor avatar URL
gravatar_idSTRINGContributor gravatar ID
html_urlSTRINGContributor HTML URL
typeSTRINGContributor type (User/Bot)
site_adminBOOLEANWhether the contributor is a site admin
contributionsINTEGERNumber of contributions to the repository

Repository Information schema

GitHub Repository Information schema

42 fieldsSchema on GitHubgithub_repository

Contains detailed repository information and statistics

GitHub Repository Information fields
FieldTypeDescription
idSTRINGRepository ID
node_idSTRINGRepository node ID
nameSTRINGRepository name
full_nameSTRINGFull repository name (owner/repo)
privateBOOLEANWhether the repository is private
owner_loginSTRINGRepository owner login
owner_idSTRINGRepository owner ID
owner_typeSTRINGRepository owner type (User/Organization)
html_urlSTRINGRepository HTML URL
descriptionSTRINGRepository description
forkBOOLEANWhether the repository is a fork
created_atDATERepository creation date
updated_atDATERepository last update date
pushed_atDATERepository last push date
homepageSTRINGRepository homepage URL
sizeINTEGERRepository size in KB
stargazers_countINTEGERNumber of stars
watchers_countINTEGERNumber of watchers
languageSTRINGPrimary programming language
has_issuesBOOLEANWhether the repository has issues enabled
has_projectsBOOLEANWhether the repository has projects enabled
has_downloadsBOOLEANWhether the repository has downloads enabled
has_wikiBOOLEANWhether the repository has wiki enabled
has_pagesBOOLEANWhether the repository has pages enabled
has_discussionsBOOLEANWhether the repository has discussions enabled
forks_countINTEGERNumber of forks
archivedBOOLEANWhether the repository is archived
disabledBOOLEANWhether the repository is disabled
open_issues_countINTEGERNumber of open issues
license_keySTRINGRepository license key
license_nameSTRINGRepository license name
allow_forkingBOOLEANWhether forking is allowed
is_templateBOOLEANWhether the repository is a template
web_commit_signoff_requiredBOOLEANWhether web commit signoff is required
topicsSTRINGRepository topics (comma-separated)
visibilitySTRINGRepository visibility (public/private)
forksINTEGERNumber of forks
open_issuesINTEGERNumber of open issues
watchersINTEGERNumber of watchers
default_branchSTRINGDefault branch name
network_countINTEGERNetwork count
subscribers_countINTEGERNumber of subscribers

Repository Statistics schema

GitHub Repository Statistics schema

3 fieldsSchema on GitHubgithub_repository_stats

Contains daily repository statistics including stars and contributors count

GitHub Repository Statistics fields
FieldTypeDescription
dateDATEDate of the data snapshot
starsINTEGERNumber of stars for the repository
contributorsINTEGERNumber of contributors to the repository

S01 · Why teams pick OWOX

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.

How it works

R01 · Collect

Collect All Your GitHub Data With Zero Engineering

The connector has three endpoints, each landing in its own table.

  1. 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.
  2. Repository Statistics has 3 fields and lands in github_repository_stats. It holds a date, the number of stars and the number of contributors.
  3. 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:

  1. Add a storage to receive the data: Google BigQuery, Snowflake, AWS Redshift, AWS Athena or Databricks.
  2. Create a Connector Data Mart and choose GitHub as the platform.
  3. Add your access token for private repositories, publish the Data Mart and run it for the first import.
  4. 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 contributions from 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 archived and fork flags.
  • 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.

S03 · Eight outcomes

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.

What users are saying

Not testimonials. Comment threads.

Real things real customers said — each quote pinned to a specific claim, straight from the quotes database.

A3re: trusting AI
Nodari RizunNodari RizunFounder & CEO, Pürblack®
“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.”
C9re: one source of truth
Mark SimmonsMark SimmonsCMO, Pürblack®
“We had six or seven different channels and no single source of truth — it was almost impossible, a lot of guesswork.”
E7re: getting time back
Nodari RizunNodari RizunFounder & CEO, Pürblack®
“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.

Get started free

References

  1. Internal OWOX data as of 2026-10-02
  2. G2 reviews of OWOX
  3. npm installs stat