Absurdly smart (and personal) autocomplete
C-Rank Grade: D (Risky) - 13/100
External PR Merge Rate: -
Response Time: 15d
First Timer Success: -
crafter-station/text0 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 crafter-station/text0 respond to incoming external pull requests in approximately 365.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 12.5 places crafter-station/text0 in the D tier.
The external contributor pull request merge rate for crafter-station/text0 is 0.0%, based on public PR activity from non-core contributors.
crafter-station/text0 currently has 4 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Absurdly smart (and personal) autocomplete
Collaborative maintainer environment in crafter-station/text0. Reviews community pull requests with focus on project quality.
Discussions in crafter-station/text0 focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/crafter-station/text0?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~238 hours (81% approval). Large PRs (>500 lines) take ~1756 hours (29% approval). Keep your diff compact for rapid review.
Context The core product surface (app/api/chat/route.ts, app/api/completion/route.ts) has no test coverage. Recent PRs (#49, #51) modified both routes; regressions there would ship silently. Task Add integration tests that mock the AI SDK providers and exercise one happy path plus model-routing branches (anthropic, google, xai, MiniMax) per route. Acceptance criteria bun test covers at least one happy path per route and one unknown-model fallback case.
Context The repo has no .github/ISSUE_TEMPLATE/, so bug reports arrive unstructured. Task Add bug_report.yml and feature_request.yml templates (YAML forms), modeled on the ones in crafter-station/pawboard. Acceptance criteria Both templates appear in the New Issue chooser.
Context The README invites contributions but there is no CONTRIBUTING.md, and the repo has no .github/ directory at all. Task Add CONTRIBUTING.md covering: bun install, bun dev, Biome lint/format (biome check --write .), the husky pre-commit hook expectations, and conventional commits. Acceptance criteria Doc merged and linked from the README.
Context .env.example lists the variables but the README's Getting Started does not say which are mandatory vs optional, or where to get each key. Clerk, Upstash Redis/Vector, UploadThing, and Trigger.dev are all required for the app to boot. Task Add a table to the README: variable, required/optional, where to obtain it, what breaks without it. Acceptance criteria A new contributor can go from clone to a working bun dev following only the README.
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 crafter-station/text0, 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 crafter-station/text0 acknowledge new external contributions in approximately 15 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.
crafter-station/text0 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 ~15 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 12.5 places crafter-station/text0 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, crafter-station/text0 currently has 4 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for crafter-station/text0 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.