Open-source, self-hosted file-processing tool. Convert, compress, OCR, transcribe & run local AI across image, video, audio, PDF & documents, via UI, REST API & pipelines. Your files never leave your network.
C-Rank Grade: B (Solid) - 61/100
External PR Merge Rate: 92%
Response Time: 13d
First Timer Success: 80%
snapotter-hq/SnapOtter has a recorded first-timer success rate of 80.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in snapotter-hq/SnapOtter respond to incoming external pull requests in approximately 300.8 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 snapotter-hq/SnapOtter in the B tier.
The external contributor pull request merge rate for snapotter-hq/SnapOtter is 91.6%, based on public PR activity from non-core contributors.
snapotter-hq/SnapOtter currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open-source, self-hosted file-processing tool. Convert, compress, OCR, transcribe & run local AI across image, video, audio, PDF & documents, via UI, REST API & pipelines. Your files never leave your network.
Highly welcoming maintainers in snapotter-hq/SnapOtter. 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/snapotter-hq/SnapOtter?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 19:00 UTC (19:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 17:00 to 21:00 UTC (17:00 - 21: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 ~196 hours (96% approval). Large PRs (>500 lines) take ~1444 hours (41% 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 TypeScript.
Real-time code feedback for pi — LSP, linters, formatters, structural analysis
A simple, yet effective Personal Relationship Manager
ZoneMinder client for iOS, Android, Windows, macOS, Linux and web. Live camera view, event review, montage, timeline, push notifications. Rewrite of zmNinja.
Summary pdf-to-text returns no output for an Arabic-language PDF. Expected Arabic text is extracted, or for image-only PDFs it is handed to OCR with Arabic support. Actual No text comes out. Notes #589 (image-only PDFs returning empty, plus missing charset=utf-8) is fixed, but Arabic-specific extraction may be a separate gap. Two candidates, and a sample PDF would tell them apart: a text-layer PDF whose embedded encoding / RTL text isn't pulled, or an image-only PDF where the OCR language set omits Arabic. Confirm the OCR language packs include ara and that RTL ordering survives extraction. Context Reported via in-app feedback on 2.1.0.
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 snapotter-hq/SnapOtter, 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 snapotter-hq/SnapOtter acknowledge new external contributions in approximately 12 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 91.6% were successfully merged into the primary branch.
snapotter-hq/SnapOtter has a recorded first-timer success rate of 80.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~12 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 61.2 places snapotter-hq/SnapOtter in the Solid tier.
The external pull request merge rate is 91.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, snapotter-hq/SnapOtter 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 snapotter-hq/SnapOtter 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.