A Symfony Bundle for interacting with Gotenberg. Integrates natively with twig, router, PHPStorm and more !
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 33%
Response Time: <1h
First Timer Success: 100%
sensiolabs/GotenbergBundle 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 sensiolabs/GotenbergBundle 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 54.2 places sensiolabs/GotenbergBundle in the B tier.
The external contributor pull request merge rate for sensiolabs/GotenbergBundle is 33.3%, based on public PR activity from non-core contributors.
sensiolabs/GotenbergBundle currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in sensiolabs/GotenbergBundle. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in sensiolabs/GotenbergBundle 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/sensiolabs/GotenbergBundle?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 07:00 UTC (07:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 07:00 to 11:00 UTC (07:00 - 11:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (42% approval). Large PRs (>500 lines) take ~0 hours (15% approval). Keep your diff compact for rapid review.
Follow-up on #286 #286 fixes GotenbergFileResult::stream() forwarding stale content-encoding/content-length (and drops transfer-encoding/connection) when an external reverse proxy sits in front of the Gotenberg server and gzip-compresses the response. Symfony HttpClient decompresses the body transparently but intentionally leaves the original headers untouched — this is confirmed as expected behavior by a core maintainer on symfony/symfony#64869, so the responsibility to sanitize headers before re-emitting a response sits with the consumer (us), not with HttpClient. That raises a few open questions: RFC 7230 §6.1 lists eight hop-by-hop headers (Connection, Keep-Alive, Proxy-Authenticate, Proxy-Authorization, TE, Trailer, Transfer-Encoding, Upgrade). #286 only strips two of them (Connection, Transfer-Encoding). Should the remaining ones (Keep-Alive, Trailer, TE, Upgrade, Proxy-Authenticate, Proxy-Authorization) also be stripped, given that any reverse proxy sitting in front of Got
According to the documentation, both URL, HTML and Markdown needs HTML for their header and footer. On the other hand, content* methods should not be present in the URL builder (Markdown still need it as a wrapper for md files). Originally posted by @Jean-Beru in #251 (comment)
ATM https://github.com/sensiolabs/GotenbergBundle/blob/1.x/docs/processing.md#custom-processor only provides how to create a custom processor. it would be nice to also show how to " decorate" another existing processor.
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 sensiolabs/GotenbergBundle, 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 sensiolabs/GotenbergBundle acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
sensiolabs/GotenbergBundle 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 ~<1 hour. 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 54.2 places sensiolabs/GotenbergBundle in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, sensiolabs/GotenbergBundle currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for sensiolabs/GotenbergBundle 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.