Various ZIM command line tools
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 50%
Response Time: 4h
First Timer Success: 50%
openzim/zim-tools 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 openzim/zim-tools respond to incoming external pull requests in approximately 3.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 61.2 places openzim/zim-tools in the A tier.
The external contributor pull request merge rate for openzim/zim-tools is 50.0%, based on public PR activity from non-core contributors.
openzim/zim-tools currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing C++ project in openzim/zim-tools welcoming community pull requests and bug fixes.
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/zim-tools?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 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (62% approval). Large PRs (>500 lines) take ~17 hours (22% approval). Keep your diff compact for rapid review.
Currently only amd64 Docker image of zim-tools is published. We need the arm64 version as well.
The current check will happily accept 1 byte parts. This is not feasible and zimsplit should complain accordingly. This is a follow-up of #537 (comment)
Currently AFAIK there is no tool to get "general" information about a ZIM: ZIM id article count media count list of metadata (including illustrations in base64 format) parsed counter data (this metadata has a specific format which would be interesting to parse it "as-libzim-understood-it-when-writing") This data must be output in JSON format and (optionally, not mandatory in my use-case) in a human-readable format.
Steps: Download Wikipedia Top 100 Mini Zim Dump with zimdump: zimdump dump --dir=./zim/ wikipedia_en_100_mini_2026-04.zim Try to rewrite with zimwriterfs: zimwriterfs \ -w "index" \ -I "_res_/favicon.png" \ -l eng \ -n "test" \ -t "test" \ -d "test" \ -c "test" \ -p "test" \ "zim/" test.zim Output: zimwriterfs: 'Birth_of_Elizabeth_II' HTML redirection target path 'zim/'./Elizabeth_II#Early_life'' doesn't exist. The file zim/Elizabeth_II exists but the section #Early_life doesn't exist (because mini flavor). I assumed this was related to zimcheck not zimwriterfs, but the zim file passes zimcheck: ~> zimcheck wikipedia_en_100_mini_2026-04.zim [INFO] Checking zim file wikipedia_en_100_mini_2026-04.zim [INFO] Zimcheck version is 3.6.0 [INFO] Verifying ZIM-archive structure integrity... [INFO] Avoiding redundant checksum test (already performed by the integrity check). [INFO] Checking metadata... [INFO] Searching for Favicon... [INFO] Searching for main page... [IN
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/zim-tools, 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/zim-tools acknowledge new external contributions in approximately 3 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 50.0% were successfully merged into the primary branch.
openzim/zim-tools 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 ~3 hours. 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 61.2 places openzim/zim-tools in the Welcoming tier.
The external pull request merge rate is 50.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, openzim/zim-tools currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for openzim/zim-tools 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.