The minimalistic document archiving platform.
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 49%
Response Time: -
First Timer Success: 33%
papra-hq/papra has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in papra-hq/papra 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 61.3 places papra-hq/papra in the A tier.
The external contributor pull request merge rate for papra-hq/papra is 48.7%, based on public PR activity from non-core contributors.
papra-hq/papra currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
The minimalistic document archiving platform.
Strict review standards in papra-hq/papra. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in papra-hq/papra 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/papra-hq/papra?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 21:00 to 01:00 UTC (21:00 - 01:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (61% approval). Large PRs (>500 lines) take ~115 hours (22% approval). Keep your diff compact for rapid review.
I'm looking for design help, or a designer, to help me improve the design of Papra. Color scheme/branding/fonts: main color scheme feels a bit too tech/crypto and doesn't feel like a document management platform. Plus the light theme accent is unrelated to the main color scheme. I'm also open to drop the dark-first approach and have a light theme as the main theme. Logo: The current logo is just an opensource icon. I'm open to any ideas and can be contacted on Discord or email at [email protected] I have some ideas and drafts, but as I'm no designer, I think that if I'm going to change everything, it might as well be done right the first time Also open to a paid one-off for the right person
Currently the server code is bundle using esbuild with dependencies external, which mean only the source code is bundled/minified, and the dependencies as keep as they are in the node_modules, with all their noise (readmes, changelog, package.json, ...) and unnecessary/unused/not-tree-shacked away code making the image unnecessarily large Idealy we would just make esbuild bundle the deps by removing --packages=external but some dependencies relies on binary bindings, like sharp which cannot be bundled, ideal we would have them marked as external, like : esbuild --bundle src/index.ts --platform=node --format=esm --external=sharp --outfile=dist/index.js But what about the installation of such externalized deps? Mark only the externalized deps as dependencies and all the bundled ones as devDependencies and continue to use pnpm deploy? Not really ideal... I've made some quick and dirty test to get view on the numbers, the actual situation: ~275Mo deps + 0.2Mo bundled sources with sharp ex
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 papra-hq/papra, 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 papra-hq/papra acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 48.7% were successfully merged into the primary branch.
papra-hq/papra has a recorded first-timer success rate of 33.3%. 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 61.3 places papra-hq/papra in the Welcoming tier.
The external pull request merge rate is 48.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, papra-hq/papra currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for papra-hq/papra 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.