Lookyloo is a web interface that allows users to capture a website page and then display a tree of domains that call each other.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 75%
Response Time: 21d
First Timer Success: 100%
Lookyloo/lookyloo has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Lookyloo/lookyloo respond to incoming external pull requests in approximately 494.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 51.0 places Lookyloo/lookyloo in the B tier.
The external contributor pull request merge rate for Lookyloo/lookyloo is 75.0%, based on public PR activity from non-core contributors.
Lookyloo/lookyloo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Python project in Lookyloo/lookyloo 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/Lookyloo/lookyloo?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~322 hours (94% approval). Large PRs (>500 lines) take ~2376 hours (34% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. Downloading a whois entry from a hostnode popup works but doesn't give any feedback. Describe the solution you'd like Add a "successfully downloaded in your dl directory" tooltip on click. Describe alternatives you've considered No response Additional context No response
Notes https://github.com/user-attachments/assets/98cc6c07-ebee-46ce-bd67-5df3f3475aac[](url)
Is your feature request related to a problem? Please describe. Some user need that information to know where the request comes from. Describe the solution you'd like Add an option in the config file to require the email address (false by default). Describe alternatives you've considered No response Additional context No response
Is your feature request related to a problem? Please describe. If the same capture (same URL and same settings) is submitted multiple times within 5 min, lookyloo returns the same UUID and doesn't re-trigger a capture. Lacus supports a force key which isn't exposed in lookyloo. Describe the solution you'd like Expose the setting in lookyloo (capture page and API), but only for admins (logged-in users). Describe alternatives you've considered No response Additional context No response
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 Lookyloo/lookyloo, 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 Lookyloo/lookyloo acknowledge new external contributions in approximately 20 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 75.0% were successfully merged into the primary branch.
Lookyloo/lookyloo has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~20 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 51.0 places Lookyloo/lookyloo in the Solid tier.
The external pull request merge rate is 75.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Lookyloo/lookyloo 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 Lookyloo/lookyloo 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.