Cameradar hacks its way into RTSP videosurveillance cameras
C-Rank Grade: B (Solid) - 52/100
External PR Merge Rate: 90%
Response Time: 6d
First Timer Success: 100%
Ullaakut/cameradar 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 Ullaakut/cameradar respond to incoming external pull requests in approximately 134.7 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 52.2 places Ullaakut/cameradar in the B tier.
The external contributor pull request merge rate for Ullaakut/cameradar is 90.0%, based on public PR activity from non-core contributors.
Ullaakut/cameradar currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Established Go ecosystem in Ullaakut/cameradar. Maintains structured code review standards for external contributors.
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/Ullaakut/cameradar?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~88 hours (96% approval). Large PRs (>500 lines) take ~647 hours (40% approval). Keep your diff compact for rapid review.
Description As described in #481, a flag to allow cameradar to attack all routes instead of stopping at the first successful one could be a useful feature. Especially when a custom dictionary is given. Additional Info No response Code of Conduct I agree to follow this project's Code of Conduct
Description I do have some brandless Xiongmai camera, which perfectly streams as rtsp://192.168.11.10:554/user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream and is reported by 'nmap -p1-9999 -sV -v' as PORT STATE SERVICE VERSION 80/tcp open http 554/tcp open rtsp 8000/tcp open http-alt? 8899/tcp open soap gSOAP 2.7 I have created myroutes file live/ch01_0 user=admin_password=tlJwpbo6_channel=1_stream=0.sdp?real_stream and mycreds.json { "usernames": [ "", "admin" ], "passwords": [ "", "admin" ] } yet camradar can not cope with this particular camera at all Cameradar version Version: vdev Commit: unknown Build date: unknown Nmap: unknown (built just now from fresh github sources) Environment Custom binary build Operating system Win10 x64 Command cameradar.exe -t 192.168.11.10 -p 80,554,8000,8899 -c mycreds.json -r myroutes --ui plain -d --skip-scan Output logs 2026-07-08T00:07:12+03:00 [INFO] Startup: Running cameradar versio
Description Now that we are using gortsplib, adding RTSPS support should be relatively easy. Detect if a port is RTSP or RTSPS (not 100% sure if nmap makes a difference at the moment) If an RTSP stream answers with a 301 and a Location we can follow that location and update the Stream on our end New default ports: 322 and 8322 New RTSP url generation depending on whether it's secured or not Change RTSP client to have a TLS config Additional Info No response Code of Conduct I agree to follow this project's Code of Conduct
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 Ullaakut/cameradar, 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 Ullaakut/cameradar acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.0% were successfully merged into the primary branch.
Ullaakut/cameradar 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 ~5 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 52.2 places Ullaakut/cameradar in the Solid tier.
The external pull request merge rate is 90.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Ullaakut/cameradar 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 Ullaakut/cameradar 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.