Data source

GitHub repository data model: details, daily stars and contributors

GitHub tells you how many stars a repository has today, not how many it had last month.

  1. Open source. OWOX Data Marts is open source: you can read the code that loads and models your data, and run it yourself.
  2. You own the data. GitHub tables load into your data warehouse, under your account. If you leave OWOX, they stay where they are.
  3. MCP-ready. Once the data is in, Claude or ChatGPT can work from your Data Marts through OWOX MCP.

Hand this to your AI

Don't wire up GitHub by hand. Have your AI assistant load it into your data warehouse.

Your assistant sets up the GitHub connector with you and loads the tables you pick; OWOX keeps them in your data warehouse, ready to use.

The prompt

set up the GitHub connector in OWOX Data Marts, let me pick the tables I need, load them into my data warehouse and show me the first rows

The GitHub data model

The GitHub data model

3 tables54 fields0 joinsView on GitHub

Repository Contributors9 fields0 relationshipsRepository Information42 fields0 relationshipsRepository Statistics3 fields0 relationships

Three tables describe one repository, the one you configure as owner/repo.

  1. Repository Information is a single row of the repository's own facts: language, license, visibility, default branch, flags such as archived and fork, and counters such as stars, forks and open issues as of the run.
  2. Repository Statistics adds one row per run with the date, the stars and the number of contributors that day.
  3. Repository Contributors lists the people and bots GitHub returns, each with a login, a type and a count of contributions.
  4. No table repeats another's key; for several repositories, run one load per repository and union the tables in SQL.
  5. The contributor list is one page of the API, 100 at most, and the daily contributor count stops at 100 for the same reason.

Schedule the load into your data warehouse daily, because the statistics table grows only on the days the connector runs; a Data Mart on top gives dashboards one stable name to read.

Explore on canvas →Import this model

Why OWOX

Why track a GitHub repository in your data warehouse

For an open-source project, a developer tool or an internal library, the question is the trend, and a trend exists only if someone saves the count every day. The connector does that on a schedule, in whichever data warehouse you load it to.

  • A history that starts when you schedule it. The connector reads the counts as they stand on the day it runs and keeps no earlier history, so the daily table begins on the day it first runs. Schedule it before the launch you want to measure, not after.
  • Your repository, not the whole archive. GH Archive, a public dataset you can query in BigQuery, records public events across GitHub. This source records one repository's own counters on your schedule, beside your other data.
  • People and bots told apart. Every contributor row carries a type, User or Bot, so the share of contributions that comes from bots is a filter, not a guess.
  • Engineering next to commercial data. Stars by day beside signups, web traffic or ad spend from other sources lets you check whether a launch moved anything.
  • For the people who watch it. A spreadsheet of stars by week for the maintainers, or a dashboard for the product team, reads the same table.

Endpoints

Repository Contributors schema

GitHub Repository Contributors schema

9 fieldsSchema on GitHubgithub_contributors

Contains list of contributors to the repository with their contribution counts

Questions this table answers

  • Who are the top ten contributors by contributions?
  • What share of contributions comes from bots?
  • How many contributors have made only one contribution?
GitHub Repository Contributors fields
FieldTypeDescription
loginSTRINGContributor login name
idPKSTRINGContributor 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

Questions this table answers

  • What are the repository's language, visibility and default branch?
  • How many stars, forks, watchers and open issues does it have now?
  • When was it created, last updated and last pushed to, and is it archived?
GitHub Repository Information fields
FieldTypeDescription
idPKSTRINGRepository 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

Questions this table answers

  • How many stars did the repository gain per week?
  • On which days did the contributor count change?
  • What is the star growth over the last 90 days?
GitHub Repository Statistics fields
FieldTypeDescription
datePKDATEDate of the data snapshot
starsINTEGERNumber of stars for the repository
contributorsINTEGERNumber of contributors to the repository

What GitHub data answers

What GitHub data answers

Across the tables

  • How have stars and contributors grown, day by day?
  • Who contributes most to the repository, and are they people or bots?
  • Which language and default branch does the repository have, and how active is it (open issues, last push)?

Industry data models that use GitHub

Industry data models that use GitHub

Where GitHub data goes

Recent updates

Other data sources

Trust

The Data Partner You Can Trust

users

166K Source: Internal OWOX data as of 2026-11-15

Executives and data analysts across 20+ industries

G2 rating

4.9★2

“A trusted data analytics partner” — verified review

npm installs

171K3

In Open Source We Trust

Customers