MediaWiki scraper: all your wiki articles in one highly compressed ZIM file
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 88%
Response Time: -
First Timer Success: 100%
openzim/mwoffliner has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openzim/mwoffliner 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 64.1 places openzim/mwoffliner in the A tier.
The external contributor pull request merge rate for openzim/mwoffliner is 87.5%, based on public PR activity from non-core contributors.
openzim/mwoffliner currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
MediaWiki scraper: all your wiki articles in one highly compressed ZIM file
Strict review standards in openzim/mwoffliner. 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/openzim/mwoffliner?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11: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 (39% approval). Keep your diff compact for rapid review.
Following openzim/cms#472 (comment) conclusion, we must always set a flavour in mwoffliner. When no flavour is selected, default value must be full.
While tracking down something odd in an Amharic Wikipedia ZIM, I noticed that the images in it all have the title "null". I then checked a batch of other recent mwoffliner ZIMs, and it turns out this happens everywhere, not just in Amharic. In wikipedia_en_all_maxi_2026-02, 8,217,604 of the 8,217,605 image entries have "null" as their title, and it's the same for the CSS, JS and other mw/ entries. Only the metadata and index entries that libzim writes itself still have empty titles. As I understand it, these non-article entries should have an empty title, so that readers fall back to the URL. The ZIMs I have from May 2025 and earlier are fine, and every one I've checked from July 2025 onwards is affected (English, German, Greek, Amharic and Pwn Wikipedias, Wiktionary, and Japanese Wikivoyage). That lines up with mwoffliner 1.15.0, which moved from node-libzim 2.4.4 to 3.3.0. As far as I can tell, mwoffliner has always passed null as the title when it adds these files (e.g. new StringIt
Bouncing off openzim/zim-requests#1885, I suspect there is no easy way of knowing which namespaces are active. Would it be possible to enter the namespace's name as a text string instead of its number, and have mwoffliner identify that thesaurus is 106 in French and 110 in English and act accordingly?
I'm using docker version and I'm trying to get the Satisfactory wiki and I'm getting errors on videos: [warn] [2026-06-05T15:58:23.282Z] Deleting audio/video HTML node missing an appropriate source in article 'Jetpack': <video poster="/images/thumb/Jetpack_pre-alpha_clip.mp4/160px--Jetpack_pre-alpha_clip.mp4.jpg?e53469" controls="40" preload="none" width="160" height="120" data-durationhint="5" data-mwtitle="Jetpack_pre-alpha_clip.mp4" data-mwprovider="local" style="max-width:100%;max-height:100%;height:100%"></video> [warn] [2026-06-05T15:58:32.991Z] Deleting audio/video HTML node missing an appropriate source in article 'Quantum_Encoder': <video poster="/images/thumb/Teaser_1.0_Quantum_Building.webm/120px--Teaser_1.0_Quantum_Building.webm.jpg?87ebbd" controls="40" preload="none" width="120" height="68" data-durationhint="4" data-mwtitle="Teaser_1.0_Quantum_Building.webm" data-mwprovider="local" style="max-width:100%;max-height:100%;height:100%"></video> [warn] [2026-06-05T15:58:32.99
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 openzim/mwoffliner, 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 openzim/mwoffliner acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 87.5% were successfully merged into the primary branch.
openzim/mwoffliner has a recorded first-timer success rate of 100.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 64.1 places openzim/mwoffliner in the Welcoming tier.
The external pull request merge rate is 87.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openzim/mwoffliner currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for openzim/mwoffliner 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.