Open Brain — The infrastructure layer for your thinking. One database, one AI gateway, one chat channel — any AI plugs in. No middleware, no SaaS.
C-Rank Grade: A (Welcoming) - 57/100
External PR Merge Rate: 32%
Response Time: -
First Timer Success: 33%
NateBJones-Projects/OB1 has a recorded first-timer success rate of 33.3%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in NateBJones-Projects/OB1 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 57.3 places NateBJones-Projects/OB1 in the A tier.
The external contributor pull request merge rate for NateBJones-Projects/OB1 is 31.5%, based on public PR activity from non-core contributors.
NateBJones-Projects/OB1 currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Open Brain — The infrastructure layer for your thinking. One database, one AI gateway, one chat channel — any AI plugs in. No middleware, no SaaS.
Balanced & professional review environment in NateBJones-Projects/OB1. Maintains strict focus on technical quality and test standards.
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/NateBJones-Projects/OB1?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 04:00 UTC (04:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 02:00 to 06:00 UTC (02:00 - 06:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (39% approval). Large PRs (>500 lines) take ~115 hours (15% approval). Keep your diff compact for rapid review.
What A database schema extension that adds a reading list to Open Brain — books, articles, podcasts with ratings, review notes, and status tracking (want to read, reading, finished). Why This is listed in the README as a planned schema but doesn't exist yet. It's a clean, self-contained table extension. What's needed SQL file with CREATE TABLE, indexes, and any RLS policies README with setup instructions metadata.json following the repo schema Recommended fields: title, author, type (book/article/podcast/video), status, rating (1-5), review_notes, url, started_date, finished_date, tags Difficulty Beginner — straightforward SQL table design.
What Complete the existing daily-digest recipe stub (recipes/daily-digest/) with real code and instructions. Current state The stub has a README with TODO placeholders and a metadata.json, but no actual code or step-by-step instructions. What's needed Edge function or script that queries recent thoughts from Supabase Formats them into a readable digest (grouped by date, with summaries) Sends via email (Resend, SendGrid, or similar) or posts to Slack Step-by-step setup instructions in the README Troubleshooting section Difficulty Beginner — mostly connecting existing APIs.
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 NateBJones-Projects/OB1, 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 NateBJones-Projects/OB1 acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 31.5% were successfully merged into the primary branch.
NateBJones-Projects/OB1 has a recorded first-timer success rate of 33.3%. Repositories ranked Welcoming 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 57.3 places NateBJones-Projects/OB1 in the Welcoming tier.
The external pull request merge rate is 31.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, NateBJones-Projects/OB1 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 NateBJones-Projects/OB1 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.