Get the main content of any page as Markdown.
C-Rank Grade: B (Solid) - 44/100
External PR Merge Rate: 33%
Response Time: 6d
First Timer Success: -
kepano/defuddle has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kepano/defuddle respond to incoming external pull requests in approximately 146.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 43.9 places kepano/defuddle in the B tier.
The external contributor pull request merge rate for kepano/defuddle is 33.3%, based on public PR activity from non-core contributors.
kepano/defuddle currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Get the main content of any page as Markdown.
Active maintainer team in kepano/defuddle 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/kepano/defuddle?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 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~95 hours (42% approval). Large PRs (>500 lines) take ~705 hours (15% approval). Keep your diff compact for rapid review.
I think that they virtualize long chats so a naive non-js solution probably won't work that well. I usually use the site's built-in markdown export but i get rate limited after a couple of exports which is super annoying. I basically want to export most of my perplexity threads because I'm moving off of it, and yeah the built-in markdown export is rate limited, and the current defuddle extractor leaves in a bunch of noise like "Prepared by GPT-5.4 Thinking" at the end of each message. As a side-note, before requesting this, I tried writing a node script which pings the exporter API with my browsers' cookies but i couldn't figure it out due the threads being represented by some UUID that's not always in the url.
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 kepano/defuddle, 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 kepano/defuddle acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 33.3% were successfully merged into the primary branch.
kepano/defuddle has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 43.9 places kepano/defuddle in the Solid tier.
The external pull request merge rate is 33.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kepano/defuddle 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 kepano/defuddle 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.