Open-source response intelligence · Evidence-first

RAMGPT Tools · Open-source accountability

OSS Response Radar.

Stars tell you who's watching. Responses tell you who's listening.

Analyze a public GitHub repository or revisit our real Round Robin contributions. First human reply and first maintainer reply are measured separately, from the original Issue or PR creation time.

01 · Public repository

Measure a project

Repository mode samples up to 12 external contributions among the latest 100 submissions. You can also paste a single Issue or PR URL.

02 · Our own evidence

Round Robin watchlist

Follow seven real upstream PRs across seven maintainers and communities. Each result links back to GitHub.

Read-only. No synthetic issues, no test comments, no GitHub login.

Live public evidence

Response measurements

Choose a repository or load our Round Robin watchlist to begin.

Methodology · v0.1

What the measurements mean

First human response

First GitHub Issue comment or submitted PR review from someone other than the author, excluding accounts identified as bots. A reply from another community member counts, even if not from the maintainer.

Maintainer response

First such response whose GitHub author association is OWNER, MEMBER, or COLLABORATOR. Contributor replies and automated labeling do not count as maintainer acknowledgements.

Response within seven days

Only submissions at least seven days old enter the denominator. Median times are calculated among replied-to submissions, not across those still waiting. Small samples are not ranked.

Limits and privacy

Timeline history is fetched in up to three pages of 100 events per item. Longer histories are marked incomplete, and missing replies are not counted as confirmed no-reply. No tokens, user profiles, or API data are stored on RAMGPT. The browser contacts GitHub directly, subject to public rate limits.

This measures public responsiveness, not patch quality, project security, or the intentions of maintainers. A response is not necessarily an acceptance. We never create throwaway Issues or PRs just to test response speed. GitHub Timeline API ↗