GLPI is a Free Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking and software auditing.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 82%
Response Time: 4d
First Timer Success: 67%
glpi-project/glpi has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in glpi-project/glpi respond to incoming external pull requests in approximately 91.4 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.4 places glpi-project/glpi in the A tier.
The external contributor pull request merge rate for glpi-project/glpi is 81.7%, based on public PR activity from non-core contributors.
glpi-project/glpi currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in glpi-project/glpi. Reviews community pull requests with focus on project quality.
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/glpi-project/glpi?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16: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 ~59 hours (96% approval). Large PRs (>500 lines) take ~439 hours (37% 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 PHP.
PHP Static Analysis Tool - discover bugs in your code without running it!
Reviactyl is a modern and open-source game server management panel built using Laravel, React, FilamentPHP, Vite, and Go. It focuses on security and performance by running every game server inside isolated Docker containers while providing users with a clean and intuitive interface.
The personal, minimalist, super-fast, database free, bookmarking service - community repo
Code of Conduct I agree to follow this project's Code of Conduct Disable plugins I reproduce the issue with all plugins disabled Is there an existing issue for this? I have searched the existing issues Version 11.0/bugfixes Bug description Clicking the "Disassociate" button in the main Network Name form to disconnect the item results in GLPI sending the user to the old item's form instead of back to the Network Name form. Relevant log output Page URL No response Steps To reproduce No response Your GLPI setup information No response Anything else? No response
Code of Conduct I agree to follow this project's Code of Conduct Disable plugins I reproduce the issue with all plugins disabled Is there an existing issue for this? I have searched the existing issues Version 11.0.7 Bug description I have successfully imported Network Names using the Data Injection plugin and I am trying to associate them with Network Devices. The imported Network Names contain a name and an IP address. When I try to associate them with Network Devices I get the alert: "Unable to reaffect given elements!" I also have the OCS Inventory plugin installed, where Network Names are created automatically for some Network Devices and associated correctly. For testing purposes, I removed one Network Name association from a Network Device. However, when I try to associate the same Network Name again manually, the same alert appears. Relevant log output Page URL front/networkname.form.php?id=1126# Steps To reproduce Import Network Names using Data Injection plugin o
Code of Conduct I agree to follow this project's Code of Conduct Disable plugins I reproduce the issue with all plugins disabled Is there an existing issue for this? I have searched the existing issues Version 11.0.7 Bug description When I add a cost in Management -> Financial & Administrative Information and link it to a budget, the costs from other tickets do not appear in that budget. If I do not link a budget in Management -> Financial & Administrative Information, the cost in the ticket is displayed normally in Budget. Relevant log output Page URL No response Steps To reproduce No response Your GLPI setup information No response Anything else? No response
Code of Conduct I agree to follow this project's Code of Conduct Contribution description I have been trying to come up with ideas for specs for context-aware data fetching in the High-Level API for a while now without being able to fully settle on any specifics, so I am looking for other people's opinions/suggestions to try to unblock this as it may be required for an official client using the HLAPI and makes it easier for non-official API uses to submit correct/expected data. A little background, In GLPI we have resource-level permissions like READ for Users. A self-service user has no permission to read users normally, but they are able to see them as options in a dropdown in some circumstances. Additionally, specific contexts like the actor fields in a ticket require additional filtering like only showing users that could be assigned to the ticket. Currently, when calling /Administration/User or GraphQL User query, only the READ permission and entity restrictions are taken into
Code of Conduct I agree to follow this project's Code of Conduct Disable plugins I reproduce the issue with all plugins disabled Is there an existing issue for this? I have searched the existing issues Version 11.0.7 Bug description I can't add a Simcard to a Ticket, I get a "An unexpected error occurred". Relevant log output glpi.CRITICAL: *** Uncaught PHP Exception RuntimeException: "Unable to get itemtype from relation input." at CommonDBRelation.php line 2268 Backtrace : ./src/CommonDBRelation.php:2268 ./src/CommonDBRelation.php:2231 CommonDBRelation->isValueEmpty() ./src/CommonDBRelation.php:2184 CommonDBRelation->validateAttachedItem() ./front/commonitilobject_item.form.php:70 CommonDBRelation->check() ./front/item_ticket.form.php:40 include() ...Glpi/Controller/LegacyFileLoadController.php:64 require() ./vendor/symfony/http-kernel/HttpKernel.php:181 Glpi\Controller
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 glpi-project/glpi, 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 glpi-project/glpi acknowledge new external contributions in approximately 3 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 81.7% were successfully merged into the primary branch.
glpi-project/glpi has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~3 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 65.4 places glpi-project/glpi in the Welcoming tier.
The external pull request merge rate is 81.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, glpi-project/glpi currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for glpi-project/glpi 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.