Skip to content
RepoInsight
For open source contributorsSee an example →

Know a repository before your first pull request.

Where to start, who maintains it, and whether outside contributions actually get merged. Every answer shows its evidence.

What you get

Six questions, answered.

  • How recently were any pull requests merged?The last merge was 2 days ago.
  • Do outside pull requests get merged?29 community pull requests merged in the last 90 days, out of 41 closed; 7 more landed as commits.
  • Do maintainers respond quickly?66 of 69 community threads were answered or closed; a first reply typically takes 26 hours.
  • Is there a contributing guide?No contributing guide in the standard locations.
  • Are there issues marked for newcomers?5 unassigned issues labelled good first issue or help wanted.

Example data for a made-up repository

See the full example →

Evidence first

Every number shows its work.

Observed
What GitHub returned.
Calculated
The formula, written out.
Interpreted
What the number suggests.
Limited
What it cannot prove.

No score, no generated text. Also in every report: activity, maintenance, releases, issues and pull requests.

Top contributor share

Example

52.5%

Of 162 commits, last 90 days

Observed

Most active author
mira-okafor
Their commits
85
Human-authored commits
162
Bot commits excluded
13

Calculation

85 ÷ 162 × 100

Limitation

A concentration signal, not proof of project risk.

Pick a repository. Start contributing.

Public data only. Nothing stored. Methodology and limitations