Drone Log analyzer: A high-performance universal dashboard application for organizing and analyzing DJI/Litchi flight logs privately in one place. Supports plugin for custom flight log formats. Built with Tauri v2, DuckDB, and React.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 67%
Response Time: 2h
First Timer Success: 100%
arpanghosh8453/open-dronelog 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 arpanghosh8453/open-dronelog respond to incoming external pull requests in approximately 1.8 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 47.9 places arpanghosh8453/open-dronelog in the B tier.
The external contributor pull request merge rate for arpanghosh8453/open-dronelog is 66.7%, based on public PR activity from non-core contributors.
arpanghosh8453/open-dronelog currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Drone Log analyzer: A high-performance universal dashboard application for organizing and analyzing DJI/Litchi flight logs privately in one place. Supports plugin for custom flight log formats. Built with Tauri v2, DuckDB, and React.
Collaborative maintainer environment in arpanghosh8453/open-dronelog. Reviews community pull requests with focus on project quality.
Discussions in arpanghosh8453/open-dronelog 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/arpanghosh8453/open-dronelog?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 17:00 UTC (17:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (83% approval). Large PRs (>500 lines) take ~9 hours (30% approval). Keep your diff compact for rapid review.
Is your feature request related to a problem? Please describe. I just thought of this feature, that you guys fly 100s of flights and probably can't check back each one for problematic behavior. We have all the data locally, so why not add some simple deviation check in the data wrt file? Like sudden change in voltage, sudden change in current, sudden drop in battery % (relative to the overall rate of falling) - and make a section under the maintenance, called Warning, and list the flights (as links) with the observed problem. The user can scroll through the list and can check the original data to confirm if there is an actual issue or it was just because of some activity (like full speed sport mode change etc) - it's not a definite problem, just an indication for the user to look through. Which area of the app does this relate to? Flight log importing / parsing Flight map / 3D path visualization Telemetry charts Overview dashboard / statistics Flight list (filtering, searching,
Is your feature request related to a problem? Please describe. Title says it all. Which area of the app does this relate to? Flight log importing / parsing Flight map / 3D path visualization Telemetry charts Overview dashboard / statistics Flight list (filtering, searching, sorting) Battery health insights Data export (CSV, JSON, GPX, KML) Settings / configuration Docker / web deployment Desktop app Other Describe the solution you'd like I would like to have an opt in feature that let users sync their DJI clouds saving them from the hassle of manual upload if they chooses so. This is completely optional and just a add-on. Describe alternatives you've considered Manual upload is time consuming and hard to keep up. Drone model(s) All DJI models Additional context This is possible as other providers does so, but I am not sure how it is done. DJI does not provide an API endpoint for getting the flight logs for logged in users. There is no official documentation how this works.
Would you bei willing to Support Betaflight (and Ardupilot) logs?
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 arpanghosh8453/open-dronelog, 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 arpanghosh8453/open-dronelog acknowledge new external contributions in approximately 1 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
arpanghosh8453/open-dronelog 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 ~1 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 47.9 places arpanghosh8453/open-dronelog in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, arpanghosh8453/open-dronelog currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for arpanghosh8453/open-dronelog 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.