Unified realtime agent trace database & search MCP
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 96%
Response Time: -
First Timer Success: 50%
eric-tramel/moraine has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in eric-tramel/moraine 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 65.4 places eric-tramel/moraine in the A tier.
The external contributor pull request merge rate for eric-tramel/moraine is 95.8%, based on public PR activity from non-core contributors.
eric-tramel/moraine currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in eric-tramel/moraine. Ensure PR scope matches issue requirements closely before requesting review.
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/eric-tramel/moraine?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 Wednesday - Friday from 01:00 to 05:00 UTC (01:00 - 05:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (43% approval). Keep your diff compact for rapid review.
Gap The Kimi reasoning branch in normalize_kimi_cli_wire_event maps ContentPart(type="think") to event_kind=reasoning / payload_type=thinking / has_reasoning=1. The in-tree fixture fixtures/kimi-cli/wire.jsonl exercises this path, and the unit test asserts the shape. But in the e2e run behind #268 against 6 real ~/.kimi/sessions, zero ContentPart records had type="think" — the reasoning path ran zero times against real data. This is plausible (the real sessions were short / didn't exercise Kimi's thinking mode), but it means: We've never verified end-to-end that reasoning rows render correctly in the monitor detail timeline for a Kimi session. If Kimi's ThinkPart payload shape diverges from what the fixture captures, we'd miss it until a user ingests a thinking-mode session. What to check Find or synthesize a Kimi session that actually uses thinking mode (enable it in Kimi CLI config; do a non-trivial coding task). Ingest through the sandbox e2e path. Verify in the monitor UI: ses
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 eric-tramel/moraine, 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 eric-tramel/moraine acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.8% were successfully merged into the primary branch.
eric-tramel/moraine has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming 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 65.4 places eric-tramel/moraine in the Welcoming tier.
The external pull request merge rate is 95.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, eric-tramel/moraine currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for eric-tramel/moraine 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.