Grida — Open Canvas
C-Rank Grade: A (Welcoming) - 61/100
External PR Merge Rate: 89%
Response Time: -
First Timer Success: 100%
gridaco/grida has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gridaco/grida respond to incoming external pull requests in approximately 0.0 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 61.4 places gridaco/grida in the A tier.
The external contributor pull request merge rate for gridaco/grida is 89.3%, based on public PR activity from non-core contributors.
gridaco/grida currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in gridaco/grida. Reviews community pull requests with focus on project quality.
Discussions in gridaco/grida 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/gridaco/grida?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 15:00 UTC (15:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 04:00 to 08:00 UTC (04:00 - 08:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (40% approval). Keep your diff compact for rapid review.
Summary Lyria 3 is now available through OpenRouter, so we can move the audio-generation seam off Replicate. https://openrouter.ai/google/lyria-3-pro-preview https://openrouter.ai/google/lyria-3-clip-preview Why Today the Lyria family is the only thing routed through Replicate's prediction API for audio. Consolidating onto OpenRouter (which we already use elsewhere for model routing) would: drop the bespoke Replicate adapter / REPLICATE_API_TOKEN dependency for audio, align audio with how we route other providers, and simplify billing/keying. Current state (Replicate) Catalogue — packages/grida-ai-models/src/models.ts, models.audio namespace: AudioProvider = "replicate" google/lyria-3 — 30s clip, per_run_flat $0.04 (replicate.com/google/lyria-3) google/lyria-3-pro — up to ~3m, per_run_flat $0.08 (replicate.com/google/lyria-3-pro) Server action — editor/lib/ai/actions/audio.ts ("Lyria et al. via Replicate") Implementation — editor/lib/ai/server.ts: methods.generateAudi
Summary When a signed-in user visits grida.co / localhost:3000, /dashboard redirects them to their "last organization." That target is only updated when a document is opened — switching organizations via the WorkspaceMenu / sidebar org switcher does not mutate any state. So a user who switches org and then closes the tab returns to the previous org on next visit. Minor UX bug, but it points at a real modeling gap: the feature is named "last organization" but the schema only tracks "last project." Repro Sign in as a user who belongs to two orgs (A, B). In Org A, open any document at least once (so state is anchored to A). Open the org menu → click Org B. URL becomes /B. Do not open a document. Visit http://localhost:3000/ (or /dashboard) in a new tab. Observed: redirected to /A/<project>. Expected: redirected to /B. Root cause (grounded) "Last org" is inferred from user_project_access_state.project_id (supabase/migrations/20250418155207_user_project_access_state.sql:9) — there
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 gridaco/grida, 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 gridaco/grida acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 89.3% were successfully merged into the primary branch.
gridaco/grida has a recorded first-timer success rate of 100.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 61.4 places gridaco/grida in the Welcoming tier.
The external pull request merge rate is 89.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gridaco/grida 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 gridaco/grida 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.