Context compression for AI coding agents: compresses tool output before it enters the model, dedups repeats to 13-token refs. Claude Code, Cursor, Codex, Kiro, Zed, any MCP client. Rust, zero LLM calls.
C-Rank Grade: D (Risky) - 15/100
External PR Merge Rate: -
Response Time: 4d
First Timer Success: -
ojuschugh1/sqz has a recorded first-timer success rate of 0.0%. Repositories ranked D typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ojuschugh1/sqz respond to incoming external pull requests in approximately 99.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 14.9 places ojuschugh1/sqz in the D tier.
The external contributor pull request merge rate for ojuschugh1/sqz is 0.0%, based on public PR activity from non-core contributors.
ojuschugh1/sqz currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in ojuschugh1/sqz welcoming community pull requests and bug fixes.
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/ojuschugh1/sqz?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
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~65 hours (81% approval). Large PRs (>500 lines) take ~477 hours (29% approval). Keep your diff compact for rapid review.
The README and the contributing guide are now in five more languages under i18n/. No native speaker has reviewed them yet, so if one of these is your language, a review would help a lot. Simplified Chinese: README, contributing guide, glossary Japanese: README, contributing guide, glossary Korean: README, contributing guide, glossary Spanish: README, contributing guide, glossary Brazilian Portuguese: README, contributing guide, glossary Read it side by side with the English text and check that the meaning is the same and that it reads naturally. The rules are in the translation guide. Comment here with the language you are taking so two people don't review the same one, then open a PR with your fixes, or list them here if that's easier. To add a new language, open a separate issue with the translation label first.
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 ojuschugh1/sqz, 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 ojuschugh1/sqz acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 0.0% were successfully merged into the primary branch.
ojuschugh1/sqz has a recorded first-timer success rate of 0.0%. Repositories ranked Risky typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~4 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 14.9 places ojuschugh1/sqz in the Risky tier.
The external pull request merge rate is 0.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ojuschugh1/sqz 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 ojuschugh1/sqz 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.