One webpage for every book ever published!
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 57%
internetarchive/openlibrary has a recorded first-timer success rate of 56.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in internetarchive/openlibrary 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 67.1 places internetarchive/openlibrary in the A tier.
The external contributor pull request merge rate for internetarchive/openlibrary is 63.9%, based on public PR activity from non-core contributors.
internetarchive/openlibrary currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in internetarchive/openlibrary. Maintains strict focus on technical quality and test standards.
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/internetarchive/openlibrary?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 18:00 to 22:00 UTC (18:00 - 22:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
This is a good first issue. You don't need to wait to be assigned — just comment that you'd like to work on it, then open a PR referencing this issue. Part of #13846. Problem PR #13839 fixed one dead link but left two related references. The bot review on #13839 flagged both. They are still on master: docs/search/priorities.md:17 and docs/opds/index.md:192 refer to pm/workflows/opds-system.md. That file does not exist in this repo. docs/CONTRIBUTING.md:93 refers to a .pam location. .pam appears nowhere else in the repo. Proposal Repoint or remove the two pm/workflows/opds-system.md references. docs/opds/README.md exists and may be the right target. Fix or remove the .pam sentence in docs/CONTRIBUTING.md. Either name the real location or drop the reference. Breakdown Related files docs/search/priorities.md, docs/opds/index.md docs/CONTRIBUTING.md docs/opds/README.md (candidate target) Requirements Checklist Repoint or remove both pm/workflows/opds-system.md references. Fix o
This is a good first issue. You don't need to wait to be assigned — just comment that you'd like to work on it, then open a PR referencing this issue. Part of #13846. Problem PR #13820 replaced docs/ai/design.md (592 lines) with docs/frontend/design.md (307 lines). It was a delete and add, not a rename. Many sections have no counterpart anywhere in docs/. .claude/rules/design.md:9 still tells agents that docs/frontend/design.md holds these rules, so the pointer is now wrong. Missing sections: Scope Text-style roles Actions wrap; passive text truncates Breakpoints Right-to-left Components (includes Popover placement, Primary action goes right, Menu rows) Icons Overlays (includes Every floating surface shares one edge, Nested radii are computed) Animations (Motion token selection; Honor prefers-reduced-motion) Fullscreen on mobile is for scrolling content Enforcement Proposal Restore the missing sections into docs/frontend/design.md from 2148484f^:docs/ai/design.md. Keep the current
This is a good first issue. You don't need to wait to be assigned — just comment that you'd like to work on it, then open a PR referencing this issue. Part of #13846. Problem PR #13820 deleted four tag-system pages and added no replacement. The directory docs/tags/ does not exist. Three files still link to it, so those links are dead: docs/README.md:25 — lists a tags/ section. docs/librarians/README.md:8 — links to ../tags/. docs/ai-coding-guide.md:265 — links to tags/index.md. Proposal Restore the four pages from 2148484f^ into docs/tags/: docs/ai/tag-system/index.md (291 lines) docs/ai/tag-system/debugging.md (161 lines) docs/ai/tag-system/dev-setup.md (104 lines) docs/ai/tag-system/known-issues.md (97 lines) Then make the three links above resolve to the restored files. If the maintainers decide the pages should stay deleted, remove the tags/ entry and fix the two links instead. Ask on the epic before you start. Breakdown Related files docs/README.md, docs/librarians/R
This is a good first issue. You don't need to wait to be assigned — just comment that you'd like to work on it, then open a PR referencing this issue. Problem / Opportunity The eslint pre-commit hook is the slowest JS formatter. It installs 7 npm packages and parses each file with Babel. It formats and lints JS and Vue files. CSS formatting already uses oxfmt. JS still uses eslint formatting rules. Each JS-only commit pays the full eslint startup cost. Measurements on a clean checkout (warm cache): npx eslint . takes about 5 seconds. npx oxlint openlibrary takes about 0.7 seconds. npx oxfmt --check on JS takes about 0.4 seconds. npx eslint on Vue files only takes about 2 seconds. Slim Vue-only config without Babel takes about 1.2 seconds. A split setup (oxlint plus oxfmt for JS, slim eslint for Vue) takes about 2.3 seconds. This is about 55 percent faster. JS-only commits skip eslint fully. Proposal Base this work on #13842. That PR starts the oxfmt move. This issue extends it to
This is a good first issue. You don't need to wait to be assigned. Comment that you want to work on it, then open a PR referencing this issue. Problem / opportunity The fast_web container takes about 6.6 seconds from container start to Application startup complete. Roughly 1.2 of those seconds go to the legacy infogami plugin walk, delegate._load(). The registry it builds holds things this container never runs. Web.py route registrations, Templetor templates/macros, and legacy i18n strings sit unused. Requests FastAPI does not handle proxy over HTTP to the web container. Every restart pays for plugin registrations nobody runs. I saw these numbers on one machine. They need reproducing on another machine before a PR. Success: fast_web startup under about 5.5 seconds. Full openlibrary/tests/fastapi/ green. Live endpoints still respond. Proposal In openlibrary/asgi_app.py, _load_legacy_wsgi() calls infogami._setup(), which walks the plugin graph. Replace it with the two parts the containe
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 internetarchive/openlibrary, 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 internetarchive/openlibrary acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.9% were successfully merged into the primary branch.
internetarchive/openlibrary has a recorded first-timer success rate of 56.5%. 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 67.1 places internetarchive/openlibrary in the Welcoming tier.
The external pull request merge rate is 63.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, internetarchive/openlibrary currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for internetarchive/openlibrary 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.