Autonomous software factory. Give it a GitHub issue, a spec or a one-line task; get back a pull request with a signed receipt anyone can re-check offline. Runs on your machine with your own keys: Claude, Codex, OpenCode.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 44%
Response Time: -
First Timer Success: 50%
asklokesh/loki-mode has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in asklokesh/loki-mode 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 51.3 places asklokesh/loki-mode in the B tier.
The external contributor pull request merge rate for asklokesh/loki-mode is 43.8%, based on public PR activity from non-core contributors.
asklokesh/loki-mode currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Autonomous software factory. Give it a GitHub issue, a spec or a one-line task; get back a pull request with a signed receipt anyone can re-check offline. Runs on your machine with your own keys: Claude, Codex, OpenCode.
Balanced & professional review environment in asklokesh/loki-mode. Maintains strict focus on technical quality and test standards.
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/asklokesh/loki-mode?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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (55% approval). Large PRs (>500 lines) take ~115 hours (20% approval). Keep your diff compact for rapid review.
Spun off from #197, which is closed as a research record. One item in that backlog is a real measurement rather than an observation, and it cannot be taken on the machine where the audit ran because the prerequisite is missing. What to measure: the codex approvals axis (how the Codex CLI's approval modes behave against our provider integration). Prerequisite, stated plainly so nobody burns time discovering it: the codex CLI must be installed and on PATH. It is NOT present on the audit host. loki doctor --json reports it as a warn there, alongside Cline. Why it was not simply left inside #197: that issue is a research backlog whose other findings are landscape observations with no change to make in this repository. Keeping one actionable measurement buried inside it made the open-issue count a poor signal of what actually needs doing. Filed under standing autonomous authority.
Four shell suites pass in isolation but fail when the gate runs them under load. This is documented in scripts/local-ci.sh:72-79 with measurements taken 2026-07-30: tests/cli/test-alias-forwarding.sh FAIL under load -> 213 passed, 0 failed alone tests/test-plan-command.sh FAIL under load -> 27 passed, 0 failed alone tests/test-proven-pr-receipt.sh FAIL under load -> 14 passed, 0 failed alone tests/test-heal-assess-readiness.sh FAIL under load -> 8 passed, 0 failed alone Why this matters more than it looks. A phantom failure trains everyone to distrust the gate, and that is exactly how a REAL failure gets waved through. This repo shipped three consecutive releases over a red CI that was reporting a genuine bug, partly because red had stopped meaning anything. Current mitigation, not a fix. local-ci.sh refuses to start a second concurrent run (single-instance lock). That stops the gate from starving itself, but the underlying timing sensitivity remains. Scope for o
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 asklokesh/loki-mode, 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 asklokesh/loki-mode acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 43.8% were successfully merged into the primary branch.
asklokesh/loki-mode has a recorded first-timer success rate of 50.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 51.3 places asklokesh/loki-mode in the Solid tier.
The external pull request merge rate is 43.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, asklokesh/loki-mode currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for asklokesh/loki-mode 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.