A coding agent: give it a prompt and it reads, writes, runs commands, and searches code in a loop until the work is done, using native tool-calling across OpenAI, Anthropic, and Google models.
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 52%
Response Time: <1h
First Timer Success: 50%
prime-radiant-inc/evener has a recorded first-timer success rate of 50.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in prime-radiant-inc/evener respond to incoming external pull requests in approximately 0.8 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 74.1 places prime-radiant-inc/evener in the S tier.
The external contributor pull request merge rate for prime-radiant-inc/evener is 51.9%, based on public PR activity from non-core contributors.
prime-radiant-inc/evener currently has 13 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in prime-radiant-inc/evener. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in prime-radiant-inc/evener 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/prime-radiant-inc/evener?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (65% approval). Large PRs (>500 lines) take ~4 hours (23% approval). Keep your diff compact for rapid review.
The demo fleet (mobile-native/src/dev/demoFleet.ts) names its sessions with short slugs like s-gateway, so this hub's rows carry the ref local:s-gateway. The Board's archiveTarget (mobile-native/src/board/rowActions.ts) accepts this hub's session only when localSessionId(ref) matches, and that check wants a 22-character alphanumeric id (/^local:([A-Za-z0-9]{22})$/, mobile-native/src/sessionDeletionResult.ts). As a result, no local demo row offers Archive: not on the swipe, not in the long-press menu, and not in select mode, where Archive stays disabled. The phase 2 screenshots and simulator checks therefore can't show archive and Undo. Fix: give the fleet's sessions ids with the real shape, for example 22-character alphanumeric ids derived deterministically from each slug. Keep the slugs readable wherever tests name them, and update the fleet's tests. (The demo hub answers no mutations, so the archive itself would still fail. It would then need an evener/archive/set answer too, which i
useSettledList in mobile-native/src/board/useSettledList.ts never disposes its SettledList. Nothing else calls SettledList.dispose() either (mobile-native/src/board/settledList.ts), in production or in tests, so its timer cleanup never runs. A Board that unmounts in the middle of a wash or a settle leaves timers that then fire into a disposed list. Either dispose in the hook's effect cleanup, with a test that unmounts mid-wash, or delete the method. Found by review on the settled-list fast-follow to #2768.
evener/search can return one live session twice: once in live, and again in past with state "ended". Why it happens hubSearch (cmd/evener-hub/app_search.go) builds live from the roster and past from cfg.Past.Search(q, ...). Nothing leaves the roster's sessions out of past. The past index holds live sessions' records too. PastIndex.scanAll (cmd/evener-hub/internal/hubcore/past.go) indexes every <project>/sessions/*.meta.json on disk, and a live session writes its meta file soon after it starts. liveTitle (cmd/evener-hub/web_format.go) relies on this: it looks live sessions up in that same index for their titles. Both copies carry the same ref, because hubRefFromTreeNodeID derives the ref from the session id alone. What users see Web command palette (cmd/evener-hub/frontend/src/shell/palette/CommandPalette.tsx, the search branch around line 764): a live session that matches the query shows under "Live" with its status dot, and again under "Past · N" as ended. iPhone Board search: thi
When the first read on the Pin session screen fails, the screen tells you to confirm a "previous change", even if you never made one. Where. NavigationActions.reconcileRecovery in mobile-native/src/navigationActions.ts (the catch that sets uncertain: true) always sets the error "Could not confirm current navigation for the previous change. Refresh before trying again." That happens even when the hub's journal holds no checkpoint (this.state.recovery is null), so the only thing that failed was the screen's own readback. PinAssignmentEditor.tsx then shows "Refresh to confirm the previous pin change before editing it." Seen. Open Pin session with nothing pending while the location read fails. The demo hub triggers this every time (see the demo fleet location issue). A real hub triggers it whenever that read fails, for example when the connection drops mid-read. Fix. When there was no checkpoint, word the error as a failed load, something like "Couldn't load this session's pins. Refresh to
With the demo hub (EVENER_DEMO_FLEET=1 npx tsx scripts/demo-hub.mts in mobile-native), the Pin session screen never loads. Opening it for any Board row shows "Could not confirm current navigation for the previous change. Refresh before trying again." and every control stays disabled. Cause. readPinLocation in mobile-native/src/pinNavigation.ts sends evener/navigation/read with resource: "location". answerNavigationRead in mobile-native/src/dev/demoFleet.ts has no location case, so the read ends in its default branch and throws Navigation resource not served by the demo fleet: location. The Board's archive check in mobile-native/src/organizationNavigation.ts reads the same resource, so it fails the same way against the demo hub. Fix. Add a location case to answerNavigationRead that answers from the fleet's own rows (the row, its pin section and its archived state), in the shape the real hub returns (cmd/evener-hub/app_navigation.go, the case "location": branch). Cover it in mobile-nativ
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 prime-radiant-inc/evener, 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 prime-radiant-inc/evener acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 51.9% were successfully merged into the primary branch.
prime-radiant-inc/evener has a recorded first-timer success rate of 50.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 74.1 places prime-radiant-inc/evener in the Elite tier.
The external pull request merge rate is 51.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, prime-radiant-inc/evener currently has 13 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for prime-radiant-inc/evener 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.