⚡ Fast, async, stream-based link checker written in Rust. Finds broken URLs and mail addresses inside Markdown, HTML, reStructuredText, websites and more!
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 65%
Response Time: -
First Timer Success: 60%
lycheeverse/lychee has a recorded first-timer success rate of 60.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in lycheeverse/lychee 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 61.3 places lycheeverse/lychee in the A tier.
The external contributor pull request merge rate for lycheeverse/lychee is 65.1%, based on public PR activity from non-core contributors.
lycheeverse/lychee currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Balanced & professional review environment in lycheeverse/lychee. Maintains strict focus on technical quality and test standards.
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/lycheeverse/lychee?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 Wednesday - Friday from 05:00 to 09:00 UTC (05:00 - 09:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (81% approval). Large PRs (>500 lines) take ~115 hours (29% approval). Keep your diff compact for rapid review.
Summary lychee consistently fails on https://ampcode.com/ with an HTTP/2 stream error, while the site is demonstrably alive. There is currently no flag to force HTTP/1.1, so the only workaround is excluding the domain. Reproduction $ lychee --no-progress https://ampcode.com/ 0: error sending request for url (https://ampcode.com/) 1: client error (SendRequest) 2: http2 error 3: stream error detected: unspecific protocol error detected Reproduced in two environments: lychee 0.24.2 via Homebrew on macOS (Darwin 25.5.0) lycheeverse/lychee-action@v2 on ubuntu-latest GitHub runners (multiple runs over several hours, so not transient) The site is fine curl succeeds from the same machines over both protocols: $ curl -s -o /dev/null -w '%{http_code}\n' https://ampcode.com/ # negotiates h2 200 $ curl -s -o /dev/null -w '%{http_code}\n' --http1.1 https://ampcode.com/ 200 ALPN negotiation itself succeeds for curl (server accepts h2, cert from Google Trust Services).
It would be nice to be allowed to override the accept config in the per host settings. I am running into a situation where an external site I don't control (but link to a bunch) is blocking crawlers. I am getting 403 from it, which is fine and probably as long as it's not a 404 I don't care. I fixed it by adding 403, to my accept, but I don't want to accidentally allow 403s on my own website.
Use case Lychee currently retries every 5xx code (per RetryExt for StatusCode). For some 5xx codes, notably Cloudflare's CDN-specific ones like 521 Web Server Down, 523 Origin Unreachable, 525 SSL Handshake Failed, and 530 Origin DNS Error / bot block, the underlying condition is typically on a minutes-to-hours scale. A within-seconds exponential-backoff retry has near-zero chance of changing the outcome but consumes the retry budget anyway. accept is a partial workaround but conflates "transient, pass silently" with "non-retriable, fail fast". Many users want the latter without the former: the URL should still appear in the error report so the operator can investigate, but lychee shouldn't waste the retry budget on it. Proposal A subtractive config option that removes codes from the built-in retry classification: # Status codes to skip retrying (subtracted from built-in retry defaults). # Useful for codes whose recovery time exceeds typical retry windows # (e.g., Cloudflare 521/523/52
> lychee --format markdown fixtures/TEST_HTML5_MALFORMED_LINKS.html ... * [ERROR] <error:> (at 6:14) | Cannot parse 'https://example]org/malformed_two' into a URL: invalid international domain name
I think these are the remaining cases for client-side github fragments, and they can be emulated using the GITHUB_TOKEN and API calls. #readme fragment going to implicit readme file - api (thanks @mre!) fragments in implicit readme files (within a directory view) - api (thanks @mre!) issue comment numbers - use api pr comment numbers - use api Originally posted by @katrinafyi in #1729. See that thread for earlier context. Closes #1729
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 lycheeverse/lychee, 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 lycheeverse/lychee acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.1% were successfully merged into the primary branch.
lycheeverse/lychee has a recorded first-timer success rate of 60.0%. 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 61.3 places lycheeverse/lychee in the Welcoming tier.
The external pull request merge rate is 65.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, lycheeverse/lychee currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for lycheeverse/lychee 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.