Skip to main content
GitHub repository Insights provides a suite of data-driven tools that help you monitor project activity, repository health, and community engagement. This guide walks through the Insights available on the Blockbuster repository and highlights the most useful views for maintainers and contributors. To open Repository Insights, go to your repository and click Insights. The Insights page gives you an overview of activity and history at a glance.
You may need repository read access (or higher) to view some Insights details. Organization-level settings can also restrict certain Analytics views.

​
Key Insights views

Below is a concise overview of the principal Insights tabs and what you can discover in each one.

​
Pulse — activity summary

The Pulse tab summarizes recent repository activity for a selectable timeframe (for example, last week or last month). It highlights:
  • Active and closed pull requests
  • Open and closed issues
  • Recent commit activity and top committers
  • Commit counts excluding merges, by default branch and all branches
Entries in the Pulse view are often clickable so you can jump directly to the related PR, issue, or commit for deeper investigation.
This image shows a GitHub repository insights page displaying activity statistics for a specific week, including pull requests and issues. It features an overview, summary, and top committers for that period.

​
Contributors — who’s doing the work

The Contributors view displays a graph and contributor list showing when and how much people commit. For single-contributor projects the graph will reflect that; for large projects it’s a quick way to spot active contributors and seasonal patterns.
The image shows a GitHub repository's contributor graph, highlighting commit activity over time, with a focus on contributions made by a user named "sid-gh900."

​
Community — engagement and standards

Community Insights aggregate signals from Discussions, issues, and pull requests. If Discussions are disabled, community metrics will be limited until you enable them. Once enabled, Insights can surface:
  • Discussion page views
  • Daily contributors and new contributors
  • Issue and PR engagement over time
Enable Discussions (if applicable) to include discussion activity in Community Insights. This provides a fuller picture of contributor engagement.
The image shows a GitHub Community Insights page for the repository "block-buster," featuring graphs of contribution activity, discussion page views, daily contributors, and new contributors over time.

​
Community standards checklist

A healthy repository is welcoming and easy to understand. GitHub’s Community Standards provide a checklist of recommended files and settings:
  • License file (e.g., LICENSE) — clarifies permitted use.
  • Contribution guidelines (CONTRIBUTING.md) — explains how to contribute.
  • Issue and pull request templates — standardize incoming reports and changes.
  • Code of conduct — sets expected community behavior.
These items improve discoverability and lower friction for new contributors.

​
Traffic — how people find your project

Traffic shows repository access metrics such as:
  • Git clones and unique cloners
  • Visitors and unique visitors
  • Referring sites
  • Popular content (most-viewed files/pages)
Use this data to understand how users discover and interact with your repo over a selectable time window (commonly the last 14 days).
The image shows a GitHub repository's insights page, displaying traffic statistics including graphs for git clones and visitors over the last 14 days.

​
Commits and code frequency

  • Commits: visualized as a calendar heatmap for the past year. You can view commits as a table and export the data as an image or CSV.
  • Code frequency: shows additions and deletions over time to indicate development intensity; may take time to populate.

​
Dependency Graph — parsed from your manifests

GitHub builds a dependency graph from language-specific manifest files (for example package.json for Node, requirements.txt for Python). It lists detected dependencies, shows their relationships, and surfaces known vulnerabilities via Dependabot integration. Example: a trimmed Node.js package.json that GitHub would read to build a dependency graph:
When you open the Dependency Graph, GitHub lists dependencies detected from manifests and shows dependency relationships and potential dependents.

​
Network — branch and merge timeline

Network shows a visual timeline of branches, commits, and merges—helpful for quickly inspecting branching strategies and merge points across the project history.
The image displays a GitHub network graph showing recent commits to a repository "block-buster" by the user "sid-gh900," with various branches and commit timelines.

​
Forks — who forked your repo

Forks lists who has forked the repository and whether the forks have activity. Use filters to sort by recent push activity or view large numbers of forks in a tree view.

​
Actions — usage and performance

Actions usage metrics summarize how GitHub Actions workflows are being used:
  • Total minutes used
  • Number of job runs
  • Runner types and operating systems
These metrics help budget CI minutes and identify heavy usage patterns.
The image shows the "Actions Usage Metrics" page from a GitHub repository, displaying total minutes and job runs for workflows during the current week. The metrics indicate 24 total minutes and 20 total job runs across workflows.
Performance metrics drill down further with average job run time, queue time, failure rate, and workflow-specific job usage. These insights assist in optimizing CI/CD and diagnosing flaky or slow jobs.
The image shows a GitHub Actions Performance Metrics dashboard with statistics such as average job run time, queue time, job failure rate, and details of different workflows.

​
Summary

Using the Insights tab gives maintainers and stakeholders a fast, data-driven view of repository health, contribution patterns, community engagement, dependency status, and CI/CD usage. Regularly review these views to:
  • Spot active contributors and gaps in activity
  • Monitor community growth and engagement
  • Track how users discover and use your project
  • Identify dependency risks and CI performance bottlenecks

Watch Video