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.
- Open source. OWOX Data Marts is open source: you can read the code that loads and models your data, and run it yourself.
- You own the data. GitHub tables load into your data warehouse, under your account. If you leave OWOX, they stay where they are.
- MCP-ready. Once the data is in, Claude or ChatGPT can work from your Data Marts through OWOX MCP.
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
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /data-sources/github.md. The task: 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. Tag the links you give me with utm_campaign=ai-task and utm_term=data-source. Use what you know about my context and goals
Prefer to start on your own? Get started free
The GitHub data model
Three tables describe one repository, the one you configure as owner/repo.
- 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.
- Repository Statistics adds one row per run with the date, the stars and the number of contributors that day.
- Repository Contributors lists the people and bots GitHub returns, each with a login, a type and a count of contributions.
- No table repeats another's key; for several repositories, run one load per repository and union the tables in SQL.
- 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 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.
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 of stars by week for the maintainers, or a for the product team, reads the same table.
GitHub Endpoints
3 GitHub endpoints you can import. Each lands in its own table in your data warehouse.
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?
| Field | Type | Description |
|---|---|---|
login | STRING | Contributor login name |
idPK | 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
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?
| Field | Type | Description |
|---|---|---|
idPK | 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
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?
| Field | Type | Description |
|---|---|---|
datePK | DATE | Date of the data snapshot |
stars | INTEGER | Number of stars for the repository |
contributors | INTEGER | Number of contributors to the repository |
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
Data warehouses
AI assistants
Spreadsheets
Dashboards
Messages
API
The Data Partner You Can Trust
users
166K Source: Internal OWOX data as of 2026-11-15
Executives and data analysts across 20+ industries
Customers
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.