LeafWiki - Self-hosted wiki. Single Go binary, SQLite, Markdown on disk. No external database required.
C-Rank Grade: S (Elite) - 73/100
External PR Merge Rate: 84%
Response Time: 1d
First Timer Success: 38%
perber/leafwiki has a recorded first-timer success rate of 37.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in perber/leafwiki respond to incoming external pull requests in approximately 26.7 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 73.3 places perber/leafwiki in the S tier.
The external contributor pull request merge rate for perber/leafwiki is 84.3%, based on public PR activity from non-core contributors.
perber/leafwiki currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in perber/leafwiki. Prompt code reviews with positive guidance for new contributors.
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/perber/leafwiki?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 18:00 UTC (18:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (96% approval). Large PRs (>500 lines) take ~128 hours (38% approval). Keep your diff compact for rapid review.
Use case I'd like to host a wiki on an old low-consumption machine, it is running with an Intel Atom N270 @ 1.60 GHz (2 threads, i686, 32-bit only, PAE). It runs on Alpine Linux, 32b like a charm 🧚🏼 LeafWiki is portable (single binary), memory-efficient and leightweight, so it's the perfect candidate to run on this machine, unfortunately the release does not ship with any compatible binary Proposed behavior Can you add in ci cross-compiling for x86 (specifically i686 or IA-32) for the next releases?
Bug Report What happened? Version Version v0.13.0 Platform Desktop Web Mobile Web Browser Chrome Firefox Safari Edge Other (please specify): Vivaldi (Chromium) Client OS Windows MacOS Linux iOS Android Other (please specify): Server OS Docker linux amd64 windows amd64 linux arm64 MacOS Steps to reproduce Open the asset (image) preview by double-click. Expected behavior The label will not be cut. Screenshots / recording One from my custom theme And one from original Possible fix Define the line-height for header (h2) element, in case with Tailwind CSS - replace the leading-* class, that is currently leading-none. I've set line-height: 1.2em; for a screenshot in "Expected behavior".
Bug Report What happened? Submitting the Create Section form with the Enter key behaves differently from clicking the Create button. When I click Create, the section is created in the sidebar and I stay on the page I am currently viewing. When I press Enter while the section name field is focused, the section is created, but LeafWiki navigates to the newly created section/editor. Both submission methods should behave consistently. Version v0.13.0 Platform Desktop Web Mobile Web Running on Docker linux amd64 windows amd64 linux arm64 MacOS Steps to reproduce Open the sidebar and click Create Section. Enter a name for the new section. Press Enter to submit the form. Notice that the section is created and LeafWiki navigates to the new section/editor. Repeat the same process, but click the Create button instead of pressing Enter. Notice that the section is created, but the currently viewed page remains open. Expected behavior Submitting the form with Enter should behave the sa
Bug Report What happened? The issue described here: #1378 is still an issue. Version This is (was) prevalent in versions: v0.12.1 & v0.13.0 Platform Desktop Web Mobile Web Running on Docker linux amd64 windows amd64 linux arm64 MacOS Steps to reproduce Using Safari Create a page that does not display 'on this page' Create a page that displays 'on this page' Navigate (back and forth) between these pages - observe the page/breadcrumb alignment This only occurs when the 'on this page' switches between being visible/hidden. At the point of the mis-alignment, when hovering over the 'favourites star', the page slides to align correctly. The mis-alignment does not occur when using the Chrome browser. Expected behaviour The breadcrumbs and the page margin should align vertically They should both be left-aligned (no left margin) On a desktop, always display the 'on this page' - even when it is empty (perhaps, hide it on a mobile, when it is empty) Screenshots / recording See: #13
Problem / use case I would love to install it as a TrueNAS app (or rather HexOS app, which is built on TrueNAS). Any chance of that happening any time soon? Cheers!
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 perber/leafwiki, 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 perber/leafwiki acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 84.3% were successfully merged into the primary branch.
perber/leafwiki has a recorded first-timer success rate of 37.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 days+. 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 73.3 places perber/leafwiki in the Elite tier.
The external pull request merge rate is 84.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, perber/leafwiki currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for perber/leafwiki 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.