#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 63%
Response Time: -
First Timer Success: 46%
Stirling-Tools/Stirling-PDF has a recorded first-timer success rate of 45.8%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Stirling-Tools/Stirling-PDF 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 64.6 places Stirling-Tools/Stirling-PDF in the A tier.
The external contributor pull request merge rate for Stirling-Tools/Stirling-PDF is 63.1%, based on public PR activity from non-core contributors.
Stirling-Tools/Stirling-PDF currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
#1 PDF Application on GitHub that lets you edit PDFs on any device anywhere
Rigorous architecture standards (66% critical review signals). Ensure PRs strictly follow guidelines before requesting review in Stirling-Tools/Stirling-PDF.
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/Stirling-Tools/Stirling-PDF?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 11:00 UTC (11:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (79% approval). Large PRs (>500 lines) take ~115 hours (28% approval). Keep your diff compact for rapid review.
Feature Description No, instead I will start with the problem: instead of finishing everything in 1 step, I have to perform 2 steps Timestamp PDF can an optional part of Sign with Certificate Enable Timestamp PDF by default as some less savvy users may not be aware that it is a thing Why is this feature valuable? A digital signature is important, but when it was applied to the PDF is just as important Suggested Implementation Sign with Certificate can have an additional timestamp section and its UI can re-use the current one in Timestamp PDF Additional Information No Example Files N/A No Duplicate of the Feature I have verified that there are no existing features requests similar to my request.
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 Stirling-Tools/Stirling-PDF, 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 Stirling-Tools/Stirling-PDF acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.1% were successfully merged into the primary branch.
Stirling-Tools/Stirling-PDF has a recorded first-timer success rate of 45.8%. 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 64.6 places Stirling-Tools/Stirling-PDF in the Welcoming tier.
The external pull request merge rate is 63.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Stirling-Tools/Stirling-PDF 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 Stirling-Tools/Stirling-PDF 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.