Open Source Field Notes

Read a GitHub repository like an investment memo.

RepoLens turns issues, pull requests, maintainer behavior, and contribution signals into a crisp editorial dashboard for engineers, founders, and developer-relations teams.

3 views

Health, activity, contribution

Rule-based

No black-box scoring

Real repos

Live GitHub analysis

Sample Board

Repository Health

82

Verdict

Active

Issue Response

17h

Merge Rate

68%

Contributor Signals

Welcoming

Good first issues12
Maintainer activityHigh

Analyze a repository

Paste any public GitHub repository URL to generate the report.

Popular:

What the dashboard reads

Repository signals at a glance

Editor's Summary

Healthy, selective, actively maintained.

Score 84

Review how a project responds to the outside world: whether maintainers answer issues, merge work, and keep obvious contributor on-ramps open.

Response time

18h

Merge rate

71%

Good first issues

9

Signal balance

Live
Maintainer activity92%
Newcomer readiness63%
Review consistency78%

Why teams use this

Compare repositories before integrating them, contributing to them, or betting your roadmap on them.

Context, not raw logs

See maintainership and issue hygiene organized into readable editorial blocks instead of noisy API dumps.

Contribution posture

Spot whether external pull requests are likely to land before a new contributor wastes effort.

Repository pulse

Track response time, merge rate, maintainer attention, and beginner-friendly labels in one place.

Designed for decisions

Deep repository context without the dashboard clutter.

Instead of flooding you with graphs, RepoLens organizes GitHub data into a reading experience that helps you answer practical questions quickly: Is this repo alive, welcoming, and worth depending on?

1 report

One concise view

4 signals

Health, PRs, maintainers, onboarding

Repository memo

A cleaner answer to should we trust this project?

Every section is written to support a real engineering decision, not just to show off metrics.

repository-notes.json
01"issue_response_hours": 17.4,
02"merge_rate": 0.71,
03"maintainer_activity": "high",
04"good_first_issue_count": 9,
05"health_summary": "active but selective"