Self-hosted AI visibility tracking (AEO / GEO / LLMO). Track how ChatGPT, Claude, Perplexity, Gemini and Google AI Overviews mention and cite your brand. One Go binary, SQLite, MCP-first, bring your own keys.
C-Rank Grade: B (Solid) - 47/100
External PR Merge Rate: 20%
Response Time: -
First Timer Success: 100%
limelit-co/open has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in limelit-co/open respond to incoming external pull requests in approximately 0.0 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 47.0 places limelit-co/open in the B tier.
The external contributor pull request merge rate for limelit-co/open is 20.0%, based on public PR activity from non-core contributors.
limelit-co/open currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in limelit-co/open. Reviews community pull requests with focus on project quality.
Discussions in limelit-co/open focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/limelit-co/open?utm_source=github&utm_medium=badge)
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 05:00 UTC (05:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (25% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
Goal olostep provider, access scraped. Engine list from public docs, to be corrected against fixtures: chatgpt, ai_mode, perplexity. This is a good first contribution. It is one HTTP call, one response parse, and a fixture, written to the interface in docs/providers.md. Expect about 150 lines. Scope Implements Provider; credentials from the env var named in docs/providers.md Calls counts billed requests; no currency ErrNoAnswerSurface for Google surfaces that did not render Recorded fixtures under testdata/, offline tests, optional live test behind //go:build live Acceptance limelit run --target chatgpt:olostep stores an answer with citations Offline tests cover a normal answer, a missing surface where applicable, an auth failure docs/providers.md engine list for olostep corrected to what the fixtures prove Docs: README.md, docs/tools.md, docs/providers.md
Goal oxylabs provider, access scraped. Engine list from public docs, to be corrected against fixtures: chatgpt, ai_mode, ai_overview, perplexity. This is a good first contribution. It is one HTTP call, one response parse, and a fixture, written to the interface in docs/providers.md. Expect about 150 lines. Scope Implements Provider; credentials from the env var named in docs/providers.md Calls counts billed requests; no currency ErrNoAnswerSurface for Google surfaces that did not render Recorded fixtures under testdata/, offline tests, optional live test behind //go:build live Acceptance limelit run --target chatgpt:oxylabs stores an answer with citations Offline tests cover a normal answer, a missing surface where applicable, an auth failure docs/providers.md engine list for oxylabs corrected to what the fixtures prove Docs: README.md, docs/tools.md, docs/providers.md
Goal brightdata provider, access scraped. Engine list from public docs, to be corrected against fixtures: chatgpt, ai_mode, ai_overview, perplexity, gemini, bing_copilot. This is a good first contribution. It is one HTTP call, one response parse, and a fixture, written to the interface in docs/providers.md. Expect about 150 lines. Scope Implements Provider; credentials from the env var named in docs/providers.md Calls counts billed requests; no currency ErrNoAnswerSurface for Google surfaces that did not render Recorded fixtures under testdata/, offline tests, optional live test behind //go:build live Acceptance limelit run --target chatgpt:brightdata stores an answer with citations Offline tests cover a normal answer, a missing surface where applicable, an auth failure docs/providers.md engine list for brightdata corrected to what the fixtures prove Docs: README.md, docs/tools.md, docs/providers.md
Goal cloro provider, access scraped. Engine list from public docs, to be corrected against fixtures: chatgpt, ai_mode, perplexity, gemini. This is a good first contribution. It is one HTTP call, one response parse, and a fixture, written to the interface in docs/providers.md. Expect about 150 lines. Scope Implements Provider; credentials from the env var named in docs/providers.md Calls counts billed requests; no currency ErrNoAnswerSurface for Google surfaces that did not render Recorded fixtures under testdata/, offline tests, optional live test behind //go:build live Acceptance limelit run --target chatgpt:cloro stores an answer with citations Offline tests cover a normal answer, a missing surface where applicable, an auth failure docs/providers.md engine list for cloro corrected to what the fixtures prove Docs: README.md, docs/tools.md, docs/providers.md
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 limelit-co/open, 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 limelit-co/open acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 20.0% were successfully merged into the primary branch.
limelit-co/open has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 47.0 places limelit-co/open in the Solid tier.
The external pull request merge rate is 20.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, limelit-co/open 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 limelit-co/open 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.