The unified repository containing the Neos core packages, used for Neos development.
C-Rank Grade: A (Welcoming) - 64/100
External PR Merge Rate: 64%
Response Time: -
First Timer Success: 53%
neos/neos-development-collection has a recorded first-timer success rate of 53.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in neos/neos-development-collection 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 63.9 places neos/neos-development-collection in the A tier.
The external contributor pull request merge rate for neos/neos-development-collection is 63.6%, based on public PR activity from non-core contributors.
neos/neos-development-collection currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Responsive & active maintainer team in neos/neos-development-collection. Reviews pull requests with focus on project architectural goals.
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/neos/neos-development-collection?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 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (80% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Is there an existing issue for this? I have searched the existing issues Current Behavior Create multiple dimensions with at least one mapping having not been initialized correctly Run ./flow timeablenodevisibility:execute Throws Expected Behavior Does not throw and actually handles the visibility changes for the working dimensions correctly. Steps To Reproduce Create multiple dimensions with at least one mapping having not been initialized correctly Run ./flow timeablenodevisibility:execute Throws Environment - Flow: 9.1.0 - Neos: 9.1.3 - PHP: 8.3 Anything else? Is this intended? In my opinion it could be beneficial to just log and continue so that the service works for the initialized dimensions. Suggestion for reference: VolkerLieber@5ff9751
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 neos/neos-development-collection, 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 neos/neos-development-collection acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.6% were successfully merged into the primary branch.
neos/neos-development-collection has a recorded first-timer success rate of 53.3%. 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 63.9 places neos/neos-development-collection in the Welcoming tier.
The external pull request merge rate is 63.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, neos/neos-development-collection 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 neos/neos-development-collection 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.