Terminal kanban on plain markdown, with optional Today/Tomorrow planner, 24h agenda + calendar, and a live view of your coding agents (Claude Code, Codex, OpenCode, Pi) with herdr integration.
C-Rank Grade: B (Solid) - 48/100
External PR Merge Rate: 17%
Response Time: 2d
First Timer Success: 50%
NazzarenoGiannelli/tuiboard has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in NazzarenoGiannelli/tuiboard respond to incoming external pull requests in approximately 36.5 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.5 places NazzarenoGiannelli/tuiboard in the B tier.
The external contributor pull request merge rate for NazzarenoGiannelli/tuiboard is 16.7%, based on public PR activity from non-core contributors.
NazzarenoGiannelli/tuiboard currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Terminal kanban on plain markdown, with optional Today/Tomorrow planner, 24h agenda + calendar, and a live view of your coding agents (Claude Code, Codex, OpenCode, Pi) with herdr integration.
Collaborative maintainer environment in NazzarenoGiannelli/tuiboard. Reviews community pull requests with focus on project quality.
Discussions in NazzarenoGiannelli/tuiboard 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/NazzarenoGiannelli/tuiboard?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 14:00 UTC (14:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~24 hours (21% approval). Large PRs (>500 lines) take ~175 hours (15% approval). Keep your diff compact for rapid review.
As of v0.8 the agenda can create/edit/delete Google Calendar events inline. Microsoft 365 is still read-only. This tracks bringing the same write support to Microsoft via Graph (Calendars.ReadWrite). Template to follow: Google write lives in src/store/calendar.ts (createGoogleEvent / updateGoogleEvent / deleteGoogleEvent) + the event modal flow in src/ui/Modal.tsx and src/store/index.ts. Microsoft read already exists (fetchMicrosoft). Add Graph create/edit/delete, thread editable + event/calendar ids onto MS events like Google, and gate the UI on a write scope. tuiboard calendar-setup microsoft should request the broader scope as an opt-in, mirroring Google's --write. Help wanted — well-scoped, with a clear Google-shaped template to mirror.
A short recorded demo would do a lot for the README (and the landing page at tuiboard.nazzareno.xyz). Suggested flow: open a board → schedule a task (t) → drop a time block (b) → switch to the agenda (F2) → optionally show the live agents view. Record against the bundled examples/ demo vault so no real data appears. asciinema cast preferred (crisp + tiny); a GIF is fine too. Drop it in docs/ and embed it near the top of the README. Good first issue — docs/marketing, minimal code.
tuiboard is developed on Windows + WezTerm. OpenTUI ships per-platform renderer binaries, so Linux/macOS should work — but it's currently untested. Reports would be hugely helpful. How to help (no code required): Install (bun install -g tuiboard, or run from source — see CONTRIBUTING.md) and launch inside examples/ (the bundled demo vault, no real data). Check: rendering (colors, box-drawing, the boot splash), mouse (click-to-arm in the agenda), keyboard navigation, and the agents view reading ~/.claude. Report your OS, terminal + version, and Bun version. Screenshots of anything that looks off are gold. Good first issue — just a careful look on a platform I can't test.
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 NazzarenoGiannelli/tuiboard, 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 NazzarenoGiannelli/tuiboard acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.7% were successfully merged into the primary branch.
NazzarenoGiannelli/tuiboard has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 47.5 places NazzarenoGiannelli/tuiboard in the Solid tier.
The external pull request merge rate is 16.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, NazzarenoGiannelli/tuiboard 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 NazzarenoGiannelli/tuiboard 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.