Repository Insights
Paste a repo URL or owner/repo pair; after an honest wait, a 24-hour × 7-day commit heatmap, half-year volume shift and the quietest six-hour stretch.
Paste a GitHub repository link and read its commit rhythm: a 24-hour weekly heatmap, first-half versus second-half activity, and its quietest six hours.
Adds a horizontal bar chart of the repository's main languages beside the commit heatmap and the half-year comparison, so the technical makeup of the project is visible at a glance.
Try Kimi BuildBuild a statistics page for GitHub repositories. An input box accepts either a full repository URL or a plain owner/repo pair, with an optional field for an access token to raise the API rate limit. After submitting, the page waits on GitHub's background statistics with an honest notice — this can take from tens of seconds to a few minutes — and a waiting animation, so a long pause never reads as a crash. Once the data is ready, show the commit time distribution as a heatmap across the twenty-four hours of a day and the seven days of a week, a comparison of commit volume between the first and the second half of the past year, and the quietest stretch of six consecutive hours in the project's rhythm. If the repository cannot be found or is private, say so with a clear, specific error message instead of a generic failure. Ship the page with built-in sample data, so the whole experience can also be demonstrated offline. Single-file static page.
Adds a second-repository comparison: after the first report loads, another repo can be added and the two commit-time distributions sit side by side for a direct rhythm comparison.
Try Kimi BuildBuild a statistics page for GitHub repositories. An input box accepts either a full repository URL or a plain owner/repo pair, with an optional field for an access token to raise the API rate limit. After submitting, the page waits on GitHub's background statistics with an honest notice — this can take from tens of seconds to a few minutes — and a waiting animation, so a long pause never reads as a crash. Once the data is ready, show the commit time distribution as a heatmap across the twenty-four hours of a day and the seven days of a week, a comparison of commit volume between the first and the second half of the past year, and the quietest stretch of six consecutive hours in the project's rhythm. If the repository cannot be found or is private, say so with a clear, specific error message instead of a generic failure. Ship the page with built-in sample data, so the whole experience can also be demonstrated offline. Single-file static page.
Adds one-click export of the finished statistics as an image report, bundling the commit heatmap and the half-year comparison into a single picture that is easy to save and share.
Try Kimi BuildBuild a statistics page for GitHub repositories. An input box accepts either a full repository URL or a plain owner/repo pair, with an optional field for an access token to raise the API rate limit. After submitting, the page waits on GitHub's background statistics with an honest notice — this can take from tens of seconds to a few minutes — and a waiting animation, so a long pause never reads as a crash. Once the data is ready, show the commit time distribution as a heatmap across the twenty-four hours of a day and the seven days of a week, a comparison of commit volume between the first and the second half of the past year, and the quietest stretch of six consecutive hours in the project's rhythm. If the repository cannot be found or is private, say so with a clear, specific error message instead of a generic failure. Ship the page with built-in sample data, so the whole experience can also be demonstrated offline. Single-file static page.
