Connect your people, tools and data with your custom AI agents. ZAQ is an open source collaborative and sovereign agentic operating system
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 85%
Response Time: 23h
First Timer Success: 57%
www-zaq-ai/zaq has a recorded first-timer success rate of 57.1%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in www-zaq-ai/zaq respond to incoming external pull requests in approximately 23.1 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 70.4 places www-zaq-ai/zaq in the S tier.
The external contributor pull request merge rate for www-zaq-ai/zaq is 85.1%, based on public PR activity from non-core contributors.
www-zaq-ai/zaq currently has 6 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
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/www-zaq-ai/zaq?utm_source=github&utm_medium=badge)
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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
To avoid race conditions due to config/modules selection based on environment variable manipulation we should add a Config module that will be in charge of loading values from environment IF they haven't been provided when calling it That middleware will then replace all application env calls so they safely be overriden by async tests We should probably phase this migration by starting with code implementation that are covered by async tests
If we update the volumes declaration on the docker container level, the path are being updated and this breaks the document reference. Consequently, the documents and chunks are still in the DB but they are being orphaned and unaccessible. When retrieving data these chunks can popup with broken source links and no way to clean them up. I suggest two things: have a way to review DB entries for documents and chunks (attached to documents whether they are in the filesystem or in an external data source) have an option to edit source fields for documents to fix them in batches
We should find an alternative for crawler ingest functionality and stop maintaining it: Excel to md Powerpoint to md Word to md PDF to md Image to md Web crawling
When we want to inform the admin of a certain event, for example: Related to #394, if the agent stops thinking after max_iterations and fails to respond, the admin should get notified So the user will see the number of notifications that were unread
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 www-zaq-ai/zaq, 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 www-zaq-ai/zaq acknowledge new external contributions in approximately 23 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.1% were successfully merged into the primary branch.
www-zaq-ai/zaq has a recorded first-timer success rate of 57.1%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~23 hours. 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 70.4 places www-zaq-ai/zaq in the Elite tier.
The external pull request merge rate is 85.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, www-zaq-ai/zaq 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 www-zaq-ai/zaq 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.