warpchart: Track GitHub Repository Growth and Rankings

Overview

Warpchart is a GitHub repository growth dashboard that adds context to star counts. It combines historical and hourly telemetry with worldwide rankings, nearby repositories, and estimated milestones, helping maintainers see how their project is changing and what may be driving spikes.

Use the hosted explorer to scan a repository without setup, or use the project as a template to run a tracker for a selected repository. Its data is also available through REST, MCP, and CLI interfaces, as well as embeddable SVG charts and badges.

Key Features

• Tracks stars, worldwide rank, recent velocity, milestones, and ranking neighbors.
• Provides charts for daily growth, cumulative stars, heatmaps, and rank history, plus a replay of the repository’s growth.
• Correlates star spikes with Hacker News posts, Reddit posts, and repository releases.
• Offers an optional synthesized soundscape, alerts through Discord or Slack webhooks, and an RSS mission log.
• Publishes cached REST API endpoints and an MCP server for querying rankings and comparing repositories.
• Includes an npx warpchart CLI for repository stats, rankings, comparisons, and embed snippets.
• Generates SVG badges and animated charts for README files.

Use Cases

• A maintainer wants to understand whether a project’s star growth is steady, accelerating, or tied to a specific event.
• A team wants to monitor ranking neighbors and estimate when its repository may pass another project or reach a milestone.
• A developer wants a live chart or rank badge to embed in a repository README.
• An agent or automation workflow needs cached repository ranking and velocity data through REST, MCP, or the CLI.
• A self-hosting maintainer wants an hourly GitHub Actions collector and a dashboard for a chosen repository.

Getting Started

For a no-setup scan, open https://warpchart.dev/r/owner/name, replacing the path with the repository owner and name. To run your own instance, use the repository as a template and follow the setup instructions in the README.

Considerations

The hosted explorer and public ranking APIs rely on collected data for repositories in the worldwide top 1,000. Repositories outside that set return 404 from the documented API rather than triggering a live GitHub fetch. Self-hosting requires setting up GitHub Actions and deploying the Next.js project to Vercel; live routes use a GitHub token with read-only access to public repositories. The repository is relatively small, with 17 stars and 1 fork, so adopters should review its setup and collector workflows before relying on it for monitoring.