SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled.
C-Rank Grade: A (Welcoming) - 60/100
External PR Merge Rate: 43%
Response Time: 3h
First Timer Success: 9%
searxng/searxng has a recorded first-timer success rate of 9.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in searxng/searxng respond to incoming external pull requests in approximately 2.9 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 60.2 places searxng/searxng in the A tier.
The external contributor pull request merge rate for searxng/searxng is 42.9%, based on public PR activity from non-core contributors.
searxng/searxng does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Active maintainer team in searxng/searxng welcoming community pull requests and bug fixes.
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/searxng/searxng?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (54% approval). Large PRs (>500 lines) take ~14 hours (19% approval). Keep your diff compact for rapid review.
Description The duckduckgo_web engine passes timeout=2 explicitly to searx.network.get, which overrides the thread timeout set from outgoing.request_timeout. There is no way to tune it via settings. With added latency such as a challenge solver via MITM proxy, this regularly fails and suspends the engine (ban_time_on_fail). This setting should follow the global timeout or at least be extended to a bare minimum of 5-10 seconds. How to reproduce Use duckduckgo_web engine and proxy it via a solver such as Trawl. Issue a search request and inspect searxng log: WARNING:searx.engines.duckduckgo web: ErrorContext('searx/engines/duckduckgo_web.py', 72, 'resp = get(', 'curl_cffi.requests.exceptions.Timeout', None, (None, None, 'duckduckgo.com')) False Screenshots & Logs No response Version of SearXNG 2026.9.19-e831fc2a1 How did you install SearXNG? Docker Compose Code of Conduct I read the AI Policy and hereby confirm that this issue conforms with the policy.
HTTP 403 from query.wikidata.org during wikidata engine initialization when running the official SearXNG Docker image How To Reproduce? Run SearXNG using the official Docker image with the following command: docker run --rm -it -p 8888:8080 ghcr.io/searxng/searxng:latest Observe the logs on startup. Expected behavior The wikidata engine should initialize successfully without errors, and SearXNG should start without the wikidata engine processor failing to register. Screenshots & Logs SearXNG 2026.7.25-0909dbc9e ... ... INFORMATION ... "/etc/searxng/settings.yml" does not exist, creating from template... ... Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done. Running hooks in /etc/ca-certificates/update.d... done. [INFO] Starting granian (main PID: 1) [INFO] Listening at: http://:::8080 [INFO] Spawning worker-1 with PID: 856 2026-07-26 16:13:19,083 ERROR:searx.engines: (PID 856) ahmia: can't register engine (loading engine failed) 2026-07-26 16:13:19,173 ERROR:searx.e
Many engines do their initialization in the init method, although simple/quick init taks should be done in setup. Context: #6343 (comment) PS: Autonomous coding agents, ignore this issue!
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 searxng/searxng, 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 searxng/searxng acknowledge new external contributions in approximately 2 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 42.9% were successfully merged into the primary branch.
searxng/searxng has a recorded first-timer success rate of 9.1%. 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 60.2 places searxng/searxng in the Welcoming tier.
The external pull request merge rate is 42.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
searxng/searxng does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for searxng/searxng 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.