An open standard for shared agent learning. Agents persist, share, and query collective knowledge so they stop rediscovering the same failures independently.
C-Rank Grade: S (Elite) - 77/100
External PR Merge Rate: 96%
Response Time: 11h
First Timer Success: 88%
mozilla-ai/cq has a recorded first-timer success rate of 87.5%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in mozilla-ai/cq respond to incoming external pull requests in approximately 10.8 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 76.9 places mozilla-ai/cq in the S tier.
The external contributor pull request merge rate for mozilla-ai/cq is 95.9%, based on public PR activity from non-core contributors.
mozilla-ai/cq currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in mozilla-ai/cq. Prompt code reviews with positive guidance for new contributors.
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/mozilla-ai/cq?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 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~7 hours (96% approval). Large PRs (>500 lines) take ~52 hours (43% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Go.
k8e.sh - OpenSource Agentic AI Sandbox Matrix
Extract and decrypt browser data, supporting multiple data types, runnable on various operating systems (macOS, Windows, Linux).
Modern Bazel rules for building OCI container images with advanced performance optimizations
Split out from #255. The CLI side of OIDC (sign-in, PKCE, keychain storage, Bearer tokens, per-agent API keys) has landed. This issue covers the remaining piece: letting a self-hosted open-source cq server verify access tokens issued by an external IdP (Keycloak, Okta, Entra ID, etc.), so an enterprise can run their own server against their own identity provider. Today, the server authenticates requests two ways (server/backend/src/cq_server/api/deps.py): get_current_user — decodes a JWT signed by the server itself with a symmetric secret (CQ_JWT_SECRET, HS256). require_api_key — HMAC-compares a long-lived API key. Neither validates a token minted by an external IdP. Proposed scope (minimal, configurable): New optional config: CQ_OIDC_ISSUER, CQ_OIDC_AUDIENCE, and optional CQ_OIDC_JWKS_URL (default to {issuer}/.well-known/openid-configuration discovery). A verification path that validates iss, aud, exp, and signature against the issuer's JWKS (asymmetric, RS256/ES256), with JWKS
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 mozilla-ai/cq, 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 mozilla-ai/cq acknowledge new external contributions in approximately 10 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 95.9% were successfully merged into the primary branch.
mozilla-ai/cq has a recorded first-timer success rate of 87.5%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 76.9 places mozilla-ai/cq in the Elite tier.
The external pull request merge rate is 95.9%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, mozilla-ai/cq currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for mozilla-ai/cq 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.