Growth Chart

"If you really want to hold yourself to a high standard, graph the growth rate of the number you care about instead of the number itself. Then you're winning if you can even keep it flat." — Paul Graham

git clone https://github.com/stevederico/growth-chart.git
cd growth-chart
npm install

Set the repos you want to track in backend/.env:

GITHUB_REPOS=owner/repo,owner/another-repo

Start the dev server:

npm run start

Frontend: http://localhost:5173 | Backend: http://localhost:8000

Automatic snapshots of download counts. The service snapshots on startup (woken by a Railway cron at 6 AM UTC) and runs an in-process hourly self-check that backfills any repo/metric missing today's row — so a long-running instance stays current across midnight. Each snapshot records cumulative downloads per release tag.

Beyond downloads, tracks stars, forks, clones, and views per repo (traffic metrics require GITHUB_TOKEN). Switch metric with the dashboard selector.

• Week-over-Week Growth — 7-day percentage change with trend indicators
• 20% Growth Goal — Shows downloads needed to hit a 20% WoW target
• Downloads Today — Real-time daily delta from the latest snapshot

Toggle between Total (cumulative downloads over time) and Daily (new downloads per day) views. Area chart with gradient fill and custom tooltips.

Sortable table showing download counts per release tag. See which versions are getting the most traction.

Track multiple GitHub repositories from a single dashboard. Switch between repos with the dropdown selector.

Insert historical data for dates before you started tracking. The backfill endpoint distributes totals proportionally across releases.

1. Backend fetches cumulative download counts (Releases API) plus stars/forks/clones/views from GitHub
2. Snapshots run on startup and hourly; a Railway cron wakes the sleeping service daily to trigger one
3. Daily deltas are computed by diffing consecutive snapshots
4. Dashboard shows total/growth chart, stats cards, daily totals, and per-release breakdown

All GitHub-tracking endpoints are unauthenticated (the dashboard reads them without a session).

Auth, user, and payment routes (/api/signup, /api/signin, /api/me, /api/usage, /api/checkout, /api/portal, Stripe webhook) come from the skateboard backend and are documented in docs/API.md.

{
  "appName": "Growth Chart",
  "tagline": "GitHub Release Download Analytics",
  "noLogin": true,
  "sidebarCollapsed": true,
  "pages": [
    { "title": "Downloads", "url": "home", "icon": "download" }
  ]
}

{
  "staticDir": "../dist",
  "database": {
    "db": "GrowthChart",
    "dbType": "sqlite",
    "connectionString": "./backend/databases/GrowthChart.db"
  }
}

SQLite by default. The GitHub-tracking tables are owned by backend/github.ts, which opens its own handle on the configured database file and creates them on boot:

-- Cumulative download counts, one row per (repo, date, release tag)
CREATE TABLE downloads (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  repo TEXT NOT NULL DEFAULT '',
  date TEXT NOT NULL,
  tag TEXT NOT NULL,
  download_count INTEGER NOT NULL,
  created_at TEXT DEFAULT (datetime('now'))
);
CREATE UNIQUE INDEX idx_downloads_repo_date_tag ON downloads(repo, date, tag);

-- Tracked repos (seeded from GITHUB_REPOS, editable via /api/repos)
CREATE TABLE repos (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  repo TEXT NOT NULL UNIQUE,
  created_at TEXT DEFAULT (datetime('now'))
);

-- stars/forks/clones/views, one row per (repo, date, metric)
CREATE TABLE github_metrics (
  id INTEGER PRIMARY KEY AUTOINCREMENT,
  repo TEXT NOT NULL,
  date TEXT NOT NULL,
  metric TEXT NOT NULL,
  count INTEGER NOT NULL DEFAULT 0,
  uniques INTEGER NOT NULL DEFAULT 0,
  created_at TEXT DEFAULT (datetime('now'))
);
CREATE UNIQUE INDEX idx_github_metrics_repo_date_metric ON github_metrics(repo, date, metric);

The skateboard auth/user/payment tables (Users, Auths, WebhookEvents) also support PostgreSQL and MongoDB via the adapter pattern in backend/adapters/; the GitHub-tracking tables are SQLite-only.

growth-chart/
├── src/
│   ├── components/
│   │   ├── HomeView.tsx          # Downloads/metrics dashboard
│   │   ├── SectionCards.tsx      # WoW growth, goal tracker, daily total
│   │   ├── ChartAreaInteractive.tsx  # Total/Daily toggle chart
│   │   ├── DataTable.tsx         # Daily table + per-release breakdown
│   │   └── CommandMenu.tsx       # Cmd+K command palette
│   ├── assets/
│   │   └── styles.css            # Theme overrides
│   ├── main.tsx                  # Route definitions
│   └── constants.json            # App configuration
├── backend/
│   ├── server.ts                 # Skateboard Hono server (auth, users, payments)
│   ├── github.ts                 # GitHub download/metrics tracking (routes + collector)
│   ├── adapters/                 # SQLite, PostgreSQL, MongoDB adapters
│   ├── databases/                # SQLite database files
│   └── config.json               # Backend configuration
├── Dockerfile                    # Multi-stage Node 24 Alpine build
└── vite.config.ts                # Vite configuration

npm run start          # Start frontend + backend concurrently
npm run front          # Frontend only (Vite dev server on :5173)
npm run server         # Backend only (Hono server on :8000)
npm run build          # Production build
npm run test           # Run tests
npm run test:watch     # Watch mode

Growth Chart includes a Dockerfile for deploying to any container host. The server snapshots downloads on startup, so schedule a daily cron job (e.g. 0 6 * * *) to wake the service and capture fresh data.

• Issues: GitHub Issues
• X: @stevederico

MIT License — see LICENSE for details.