The AI notebook that checks its own citations. Ask your PDFs, Word files, slides and spreadsheets; answers cite the exact page. Open-source desktop app.
C-Rank Grade: B (Solid) - 50/100
External PR Merge Rate: 20%
Response Time: <1h
First Timer Success: -
junruxiong/IncarnaMind has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in junruxiong/IncarnaMind respond to incoming external pull requests in approximately 0.6 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 50.2 places junruxiong/IncarnaMind in the B tier.
The external contributor pull request merge rate for junruxiong/IncarnaMind is 20.0%, based on public PR activity from non-core contributors.
junruxiong/IncarnaMind currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The AI notebook that checks its own citations. Ask your PDFs, Word files, slides and spreadsheets; answers cite the exact page. Open-source desktop app.
Strict review standards in junruxiong/IncarnaMind. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in junruxiong/IncarnaMind 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/junruxiong/IncarnaMind?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (25% approval). Large PRs (>500 lines) take ~3 hours (15% approval). Keep your diff compact for rapid review.
Parent #74 What to build Two small things the UI audit (e2e/audit/) still finds: Error notices. An error notice shows the raw IPC error text (for example "Error invoking remote method …"). Show the message the core gives in plain words, in English and Chinese, and keep the technical detail behind a "Details" disclosure or in the log. An error stays where it happened until the User dismisses it or fixes it, and never closes itself; only a non-error confirmation ("Copied", "Added to note") closes itself after a few seconds. Either kind can be closed by hand and by Escape. Menu items' focus. Menu items (src/renderer/src/ui.ts, the class with outline-none) show keyboard focus only as a faint fill. Give them the same visible focus treatment as other controls in DESIGN.md. Acceptance criteria No notice shows "Error invoking remote method" or a stack; a test triggers a core error and checks the plain message and the Details disclosure. An error notice stays until it is dismissed or its
Parent #74 What to build Style. The Mind's ⋯ menu › Style offers any installed font (each name drawn in its own face, with search) and a text size (Small, Default, Large), plus "Make this the default for new Minds". Missing fonts. A missing font falls back to the default, and Style says "Not installed on this computer". Export. Word export writes the Mind's font; Markdown drops it. Acceptance criteria The font persists per Mind, across restarts and through sync. Fallback is tested. Word export keeps the font (test). The definition of done in #74 holds. Blocked by None (can start immediately).
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 junruxiong/IncarnaMind, 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 junruxiong/IncarnaMind acknowledge new external contributions in approximately <1 hour. 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.
junruxiong/IncarnaMind has a recorded first-timer success rate of 0.0%. Repositories ranked Solid 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 50.2 places junruxiong/IncarnaMind 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, junruxiong/IncarnaMind 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 junruxiong/IncarnaMind 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.