A privacy-preserving Raspberry Pi home security camera that uses advanced end-to-end encryption.
C-Rank Grade: D (Risky) - 16/100
External PR Merge Rate: -
Response Time: -
First Timer Success: -
secluso/core has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in secluso/core 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 15.7 places secluso/core in the D tier.
The external contributor pull request merge rate for secluso/core is 0.0%, based on public PR activity from non-core contributors.
secluso/core currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in secluso/core. Reviews community pull requests with focus on project quality.
Discussions in secluso/core 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/secluso/core?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 06:00 UTC (06:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 03:00 to 07:00 UTC (03:00 - 07: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.
Delivery monitor keeps event videos around until they are acked by the app (via a heartbeat). Heartbeat is scheduled to be sent at most every 6 hours but the app might not send the heartbeat in a timely fashion. Moreover, there could be a lot of unacked videos and the microsd card could run out of free space (especially if it has a small storage capacity). If that happens, the camera won't be able to recover and it must be reset and paired again. To avoid this, the delivery monitor can keep track of the free space on the microsd card and possibly delete older unacked videos if necessary.
Currently, the host computer attempting to check reproducibility for macOS with the deploy tool must match all enforced toolchain versions (e.g. rustc, Node, Cargo...) against the digest lock file in their local environment. This works, but it is not the best practice. We should instead use Darwin Containers to decouple host and build environments similar to how we currently handle Windows and Linux.
We should replace ssh2 with the russh crate in the deploy tool for server provisioning. This is the last thing required to replace OpenSSL usage with rustls project-wide.
The deploy tool currently enables the update service on both the server and the RPi by default. This works fine when both devices are in sync, but if one has auto-update on and the other doesn't, they'll constantly clash. Additionally, something to consider is that if the user is running one of our relays, auto-update must be on.
We currently support audio in our mp4 writer, but not our fmp4 writer.
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 secluso/core, 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 secluso/core acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
secluso/core has a recorded first-timer success rate of 0.0%. Repositories ranked Risky 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 15.7 places secluso/core in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, secluso/core currently has 6 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for secluso/core 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.