A TYPO3 extension that integrates the Apache Solr search server with TYPO3 CMS. dkd Internet Service GmbH is developing the extension. Community contributions are welcome. See CONTRIBUTING.md for details.
C-Rank Grade: A (Welcoming) - 58/100
External PR Merge Rate: 63%
Response Time: 7h
First Timer Success: 100%
TYPO3-Solr/ext-solr has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in TYPO3-Solr/ext-solr respond to incoming external pull requests in approximately 7.5 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 58.0 places TYPO3-Solr/ext-solr in the A tier.
The external contributor pull request merge rate for TYPO3-Solr/ext-solr is 63.0%, based on public PR activity from non-core contributors.
TYPO3-Solr/ext-solr currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in TYPO3-Solr/ext-solr. Prompt code reviews with positive guidance for new contributors.
Discussions in TYPO3-Solr/ext-solr 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/TYPO3-Solr/ext-solr?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 06:00 to 10:00 UTC (06:00 - 10:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~5 hours (79% approval). Large PRs (>500 lines) take ~36 hours (28% approval). Keep your diff compact for rapid review.
#2589 #4464 #4696 #4097 #3993 #4490 ... Please help to connect all the SOLR_RELATION related issues here.
Summary Since EXT:solr 8.0, options facets use the JSON Facet API (PR #1764). All other facet types still use the legacy Solr faceting APIs (facet.field, facet.query, facet.range). This blocks advanced features — most notably domain modifications (e.g. making facet counts independent of the active search term) — for the majority of facet types. The OptionsFacetQueryBuilder already contains a related @Todo: "When we use JSON faceting for other facets some logic of this class can be moved to the base class." Affected facet types Facet type Current API JSON Facet equivalent Issue hierarchy facet.field type: terms #4636 queryGroup facet.query type: query #4640 dateRange facet.range type: range #4638 numericRange facet.range type: range #4639 Motivation Without JSON Facet API support, the following is impossible for the above types: domain.query / domain.filter — computing facet counts against a different document set (e.g. independent of the search term q) domain.e
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 TYPO3-Solr/ext-solr, 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 TYPO3-Solr/ext-solr acknowledge new external contributions in approximately 7 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 63.0% were successfully merged into the primary branch.
TYPO3-Solr/ext-solr has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~7 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 58.0 places TYPO3-Solr/ext-solr in the Welcoming tier.
The external pull request merge rate is 63.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, TYPO3-Solr/ext-solr currently has 2 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for TYPO3-Solr/ext-solr 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.