Parker is a self‑hosted comic server where the filesystem is the source of truth
C-Rank Grade: B (Solid) - 67/100
External PR Merge Rate: 98%
Response Time: 19d
First Timer Success: 100%
parker-server/parker has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in parker-server/parker respond to incoming external pull requests in approximately 453.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 66.8 places parker-server/parker in the B tier.
The external contributor pull request merge rate for parker-server/parker is 97.5%, based on public PR activity from non-core contributors.
parker-server/parker currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in parker-server/parker. 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/parker-server/parker?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 Monday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~295 hours (96% approval). Large PRs (>500 lines) take ~2177 hours (44% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Python.
LeetCode Daily Challenge Solutions
The official deployment of the Digital Slide Archive and HistomicsTK.
Python toolkit, MCP server, and agent skills for reproducible, auditable clickstream and event log analytics. Helps AI agents, data scientists and analysts build, validate, and cross-check product analytics, quantitative UX, customer journeys, graph-based user flows, behavioral segmentation, A/B tests, process mining models, Markov chain simulation
Hey all! Currently in Parker I have an Reading List 'enrichment process' that introduced a system to automatically populate descriptions for major storylines (e.g., "Crisis on Infinite Earths", "Civil War") using a local curated seed file. I filed in a few to get myself started and test, but there are still a ton of major story arcs that aren't represented yet. During a scan when a reading list has to be be created, the system attempts to match the value of the <AlternateSeries> attribute in ComicInfo.xml to one of the names in the local events.json file. If a match is found that description is put into the database along with the rest of the reading list data. There is also a maintenance task that can be manually run in the admin section to attempt to backfill any missing descriptions if matches are found. I plan on expanding this file myself over time as the descriptions give great context to the read when they click on one of these reading lists to get a quick summary of what t
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 parker-server/parker, 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 parker-server/parker acknowledge new external contributions in approximately 18 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 97.5% were successfully merged into the primary branch.
parker-server/parker has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~18 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 66.8 places parker-server/parker in the Solid tier.
The external pull request merge rate is 97.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, parker-server/parker currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for parker-server/parker 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.