Scraper for downloading the entire ebooks repository of project Gutenberg
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 56%
Response Time: 9h
First Timer Success: -
openzim/gutenberg has a recorded first-timer success rate of 0.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in openzim/gutenberg respond to incoming external pull requests in approximately 9.4 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 56.9 places openzim/gutenberg in the A tier.
The external contributor pull request merge rate for openzim/gutenberg is 56.3%, based on public PR activity from non-core contributors.
openzim/gutenberg does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Highly welcoming maintainers in openzim/gutenberg. Prompt code reviews with positive guidance for new contributors.
Discussions in openzim/gutenberg 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/openzim/gutenberg?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (70% approval). Large PRs (>500 lines) take ~45 hours (25% approval). Keep your diff compact for rapid review.
Add the number of books the author has in current archive, to avoid clicking on the name only to realize the author has only one book... kinda deceiving ^^ Use same colors than number of books on shelves: (without #592 obviously)
In the left part of the shelves display, We have a very small glitch: The underline is covering the space where we would like to have no underline on the space: Clearly a very small visual glitch, but since we saw it, I fill the issue
As the architecture has grown up with time we added another source ingestion which is open textbook library (OTL). With this architecture it has become easier to add a new source ingestion, for example here's a new candidate #527. We need clear instructions how to add another source to the architecture in the same manner how OTL was added. See #525 for reference and how to connect a new ingestion while using all the core engine resources whatever it exposes, those core engine methods should be described properly. It should contain clear instructions, as in how and where to derive CLI args, image optimization, use of concurrency, adding new source-agnostic keys (works or collection) in en.json and qqq.json locales, or whatever resource there is to use for us, while not touching core engine unless there is still anything left coupled to the source.
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/gutenberg, 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/gutenberg acknowledge new external contributions in approximately 9 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 56.3% were successfully merged into the primary branch.
openzim/gutenberg has a recorded first-timer success rate of 0.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~9 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 56.9 places openzim/gutenberg in the Welcoming tier.
The external pull request merge rate is 56.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
openzim/gutenberg does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for openzim/gutenberg 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.