Open-source Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) platform. Track how ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, and Google AI Overviews mention and cite your brand in AI search. MIT-licensed, self-hostable, every metric auditable in code.
C-Rank Grade: A (Welcoming) - 68/100
External PR Merge Rate: 79%
Response Time: 4d
First Timer Success: 60%
elmohq/elmo has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in elmohq/elmo respond to incoming external pull requests in approximately 92.9 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 68.2 places elmohq/elmo in the A tier.
The external contributor pull request merge rate for elmohq/elmo is 79.2%, based on public PR activity from non-core contributors.
elmohq/elmo currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source Answer Engine Optimization (AEO) and Generative Engine Optimization (GEO) platform. Track how ChatGPT, Claude, Perplexity, Gemini, Copilot, Grok, and Google AI Overviews mention and cite your brand in AI search. MIT-licensed, self-hostable, every metric auditable in code.
Highly welcoming maintainers in elmohq/elmo. Prompt code reviews with positive guidance for new contributors.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/elmohq/elmo?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 22:00 UTC (22:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~60 hours (96% approval). Large PRs (>500 lines) take ~446 hours (36% approval). Keep your diff compact for rapid review.
use two date pickers as an option instead of just the preset lookbacks? will need to make sure it works with the url params too
This looks pretty cool: https://x.com/agektmr/status/2093179024042602881 Not the most useful thing ever but a good pattern to follow.
I always like to see this sort of thing when logging into a website: https://better-auth.com/docs/plugins/last-login-method
The README has no pointer to CONTRIBUTING.md, so the setup steps, CLA flow, and open issues aren't discoverable from the front page. Add a short ## Contributing section (before ## License) linking CONTRIBUTING.md, the developer guide, and the good first issue list.
GlossaryTerm.seeAlso in apps/www/src/data/glossary.ts renders on the term page, but 15 of 28 terms don't set it: llmo, answer-engine, brand-mention, prompt-volume, visibility-score, entity, retrieval-augmented-generation, grounding, hallucination, ai-crawler, zero-click-search, knowledge-graph, semantic-search, embedding, large-language-model Add one or two relevant deep links each, pointing at existing pages (usually a post under packages/docs/content/blog/). Fine to pick off a handful rather than all 15.
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to elmohq/elmo, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of elmohq/elmo acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 79.2% were successfully merged into the primary branch.
elmohq/elmo has a recorded first-timer success rate of 60.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 68.2 places elmohq/elmo in the Welcoming tier.
The external pull request merge rate is 79.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, elmohq/elmo currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for elmohq/elmo are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.