The PHP Interpreter
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 40%
Response Time: 3h
First Timer Success: 30%
php/php-src has a recorded first-timer success rate of 29.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in php/php-src respond to incoming external pull requests in approximately 2.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 65.9 places php/php-src in the A tier.
The external contributor pull request merge rate for php/php-src is 40.5%, based on public PR activity from non-core contributors.
php/php-src currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in php/php-src. Prompt code reviews with positive guidance for new contributors.
Discussions in php/php-src 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/php/php-src?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (51% approval). Large PRs (>500 lines) take ~13 hours (18% approval). Keep your diff compact for rapid review.
Description PNG files exported from some applications, most notably Photoshop, are written with an sRGB profile that libpng sees as invalid. Any attempt to load a file like this using the GD library causes a warning to be written to the PHP error log. It is not possible to suppress this warning. The following code: <?php $image = imagecreatefrompng('clouds.png'); Results in this warning: Warning: imagecreatefrompng(): gd-png: libpng warning: iCCP: known incorrect sRGB profile Please see the attached file as an example of one that has the issue. The only solution I have found so far is to post-process the PNG to remove the sRGB profile. This is not ideal for workflow with large numbers of files. Whilst it is possible to disable all warnings, they are often on in production so this is not a desirable solution. I would like a method to suppress all libpng warnings. This could be implemented as a gd_ prefixed method that takes an optional bool parameter to toggle warnings on or off. If no
Description These have no unit tests, but we aren't even doing a smoke test for builds. Apache should be easy since it's in repo on Linux (Windows, unsure how annoying), LiteSpeed is another thing to download.
Effectively continuing the work started in #23192. This is a good first issues for newcomers. The missing specifiers are: Z_PARAM_ENUM(dest, _ce) old "a" Z_PARAM_ARRAY_EX2(dest, check_null, deref, separate) Z_PARAM_ARRAY_EX(dest, check_null, separate) Z_PARAM_ARRAY(dest) Z_PARAM_ARRAY_OR_NULL(dest) old "A" Z_PARAM_ARRAY_OR_OBJECT_EX2(dest, check_null, deref, separate) Z_PARAM_ARRAY_OR_OBJECT_EX(dest, check_null, separate) Z_PARAM_ARRAY_OR_OBJECT(dest) old "h" Z_PARAM_ARRAY_HT_EX2(dest, check_null, deref, separate) Z_PARAM_ARRAY_HT_EX(dest, check_null, separate) Z_PARAM_ARRAY_HT(dest) Z_PARAM_ARRAY_HT_OR_NULL(dest) array|int: Z_PARAM_ARRAY_HT_OR_LONG_EX(dest_ht, dest_long, is_null, allow_null) Z_PARAM_ARRAY_HT_OR_LONG(dest_ht, dest_long) Z_PARAM_ARRAY_HT_OR_LONG_OR_NULL(dest_ht, dest_long, is_null) array|string: Z_PARAM_ARRAY_HT_OR_STR_EX(dest_ht, dest_str, allow_null) Z_PARAM_ARRAY_HT_OR_STR(dest_ht, dest_str) Z_PARAM_ARRAY_HT_OR_STR_OR_NULL(dest_ht
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 php/php-src, 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 php/php-src acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 40.5% were successfully merged into the primary branch.
php/php-src has a recorded first-timer success rate of 29.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 hours. 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 65.9 places php/php-src in the Welcoming tier.
The external pull request merge rate is 40.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, php/php-src 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 php/php-src 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.