tutti-os/tutti
Where people and agents build in tune.
Reliability breakdown
What drives the reliability score
Component scores measured daily from GitHub activity (2026-07-19).
Activity on 37 of 39 tracked days in the last 90 and 28 of 30 in the last 30.
Merged 991 of 1,181 PRs opened and closed 112 of 153 issues opened over the last 90 tracked days — PR flow carries 55% of this component, issue flow 45%.
25 releases in the last 180 days, 25 in the last 90 and 22 in the last 30 — a steady cadence scores highest.
Last push 0 days ago — freshness decays as pushes age (roughly halves every 83 days without a push).
43 open issues against 2,452 stars — about 18 open issues per 1,000 stars. Lighter backlogs score higher.
Modeled — lower is better; concentration of commits in few maintainers. Contributors graph
Join the conversation
Reviews · Questions · Posts
Share what you know about tutti — write a review from your real experience, ask an implementation question, or publish a post about how you use it.
Share your experience
Write or update your review
Explain what worked, what broke down, and what another team should know before adopting tutti.
Project Q&A
Questions and answers
Browse implementation threads tied directly to tutti-os/tutti. Each question links through to the full answer page.
Be the first to ask how teams run tutti in production. Every question you post becomes a durable, searchable answer page other developers can find.
Ask the first questionRelated posts
Posts tagged with the same topics
These posts come from the same topic surface as this repo, so readers can move from project evaluation into practical writeups and migration notes without leaving context.
Share how your team uses tutti — a migration note, an architecture writeup, or a comparison. Your post reaches everyone browsing these same topics.
Write the first post