Self-hosted AI agent OS. Your memory, chat, agents, and files stay on hardware you own, offline by default, cloud by choice. Offline AI memory (taOSmd), self-hosted multi-framework group chat, a full web desktop + app store, and auto-clustering across the consumer hardware you already have (Orange/Raspberry Pi, Mac mini, gaming PC).
C-Rank Grade: S (Elite) - 72/100
External PR Merge Rate: 83%
Response Time: 5d
First Timer Success: 100%
jaylfc/taOS has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in jaylfc/taOS respond to incoming external pull requests in approximately 121.3 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 71.7 places jaylfc/taOS in the S tier.
The external contributor pull request merge rate for jaylfc/taOS is 83.4%, based on public PR activity from non-core contributors.
jaylfc/taOS currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Self-hosted AI agent OS. Your memory, chat, agents, and files stay on hardware you own, offline by default, cloud by choice. Offline AI memory (taOSmd), self-hosted multi-framework group chat, a full web desktop + app store, and auto-clustering across the consumer hardware you already have (Orange/Raspberry Pi, Mac mini, gaming PC).
Strict review standards in jaylfc/taOS. Ensure PR scope matches issue requirements closely before requesting review.
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/jaylfc/taOS?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 21:00 UTC (21:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~79 hours (96% approval). Large PRs (>500 lines) take ~582 hours (38% approval). Keep your diff compact for rapid review.
Two MINOR findings from CodeRabbit on #2097 (merged clean; these are non-blocking polish): Broken thumbnail fails silently (LibraryItemCard.tsx). When a thumbnail artifact exists but the image fails to load, onError hides the <img>, leaving blank space. Prefer showing the same placeholder used when no thumbnail exists. source option declared but never sent (lib/library.ts). IngestLibraryOptions.source is defined but not serialized into the request body. Either wire it into the POST body or drop the option. Good first task for a fleet lane.
S7 Ready to Test Checklist (Hailo-10H Backend) This is the checklist for the community tester to verify the Hailo-10H NPU backend integration. Please execute these steps and provide feedback. Prerequisite You must have: Raspberry Pi 5 with AI HAT+2 (Hailo-10H, 40 TOPS) HailoRT + hailo-genai installed and working All slices S1-S6 installed and in place 1. Install the new Hailo backend # from anywhere, no checkout needed (recommended) curl -sSL https://raw.githubusercontent.com/jaylfc/taOS/master/scripts/install-hailo.sh \ | TAOS_HAILO_SETUP=1 sudo bash # or, if you have a taOS checkout, cd into it FIRST (the path is repo-relative) cd /opt/taos sudo TAOS_HAILO_SETUP=1 bash scripts/install-hailo.sh Please paste the complete banner + summary output. 2. Verify service is running systemctl status hailo-ollama curl -s http://localhost:7836/api/tags Run each of the two commands above on its OWN line (do not paste the prose with them). Confirm: service shows "active" and the curl output sh
Background security review (MEDIUM). is_safe_public_url (tinyagentos/userspace/url_guard.py) resolves + validates a hostname's IPs, but install_app then re-resolves the hostname when httpx connects, leaving a DNS-rebinding / TOCTOU window where the connected IP can differ from the validated one (and bounce to an internal address). Fix Resolve once in is_safe_public_url, return the validated IP(s), and pin the httpx connection to that IP (a custom transport / pinned resolver) while preserving the original Host header and SNI for TLS. Scheduling This lives in install_app's source_url fetch, which the P2 distribution phase rebuilds into a proper download broker (signed-bundle fetch + sha256 + signature + min_os verification). The DNS-pinned fetch belongs there, so it is folded into P2 rather than fixed in isolation, and to avoid colliding with the in-flight P3b branch that edits the same install_app function. Note: is_safe_public_url already blocks the obvious case (private / loopback / r
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 jaylfc/taOS, 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 jaylfc/taOS acknowledge new external contributions in approximately 5 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 83.4% were successfully merged into the primary branch.
jaylfc/taOS has a recorded first-timer success rate of 100.0%. Repositories ranked Elite 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 71.7 places jaylfc/taOS in the Elite tier.
The external pull request merge rate is 83.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, jaylfc/taOS 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 jaylfc/taOS 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.