Git. Ship. Done - Core
C-Rank Grade: A (Welcoming) - 69/100
External PR Merge Rate: 85%
Response Time: 23h
First Timer Success: 39%
open-gsd/gsd-core has a recorded first-timer success rate of 39.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in open-gsd/gsd-core respond to incoming external pull requests in approximately 22.9 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 68.7 places open-gsd/gsd-core in the A tier.
The external contributor pull request merge rate for open-gsd/gsd-core is 85.4%, based on public PR activity from non-core contributors.
open-gsd/gsd-core does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
Strict review standards in open-gsd/gsd-core. Ensure PR scope matches issue requirements closely before requesting review.
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/open-gsd/gsd-core?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 01:00 UTC (01:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~15 hours (96% approval). Large PRs (>500 lines) take ~110 hours (38% approval). Keep your diff compact for rapid review.
Drafted with AI assistance during a full-repo audit; approved and authored by the maintainer. An approved epic does not approve its children — each child is its own issue before code. Security routing note: all three items were assessed for exploitability and are hardening / defense-in-depth on a first-party, consented, local surface — none is a live exploitable vector, so they are filed publicly (precedents #751 / #1406 / #116), not as private advisories. Justifications are in each child. Epic: Capability + hook security hardening (ADR-1244 edges) Problem The ADR-1244 capability trust pipeline (descriptor → source-resolve → integrity → tar-slip guard → trust eval → consent → ledger → load-gate) is mature and largely fail-closed. The findings are at the edges — places where a safe posture the pipeline applies elsewhere isn't applied consistently. Verified live at next @ 3c13903d: # Finding file:line Nature F20 MCP server config (command/args/env/cwd) is writ
Drafted with AI assistance during a full-repo audit; approved and authored by the maintainer. An approved epic does not approve its children — each child is its own issue before code. Epic: Prompt-layer single-source-of-truth — kill orphaned workflows and silent enforcement drift Problem The workflow/agent instruction layer has accumulated two kinds of debt that make it no longer a single source of truth. Every item verified live at next @ 3c13903d: (1) Provably-orphaned files still shipped + test-pinned: # File file:line Status F7 gsd-core/workflows/verify-phase.md (~40 KB) no @~/ include anywhere; pinned by tests/verifier-deferred-items.test.cjs:117-151 dead prose shipped to every runtime; PRs to gsd-verifier.md must mirror its dead twin to keep the lockstep test green F12 scan.md, plan-milestone-gaps.md, discovery-phase.md (~27 KB) no command entry; plan-milestone-gaps "deleted by #2790" per commands/gsd/ns-project.md:12; discovery-phase.md claims a plan-phase.md calle
Drafted with AI assistance during a full-repo audit; approved and authored by the maintainer. An approved epic does not approve its children — each child is its own issue + its own confirmed-bug before code. Epic: Install-path write durability — apply the safe primitives that already exist in-repo Problem The installer has four write paths to high-blast-radius, user-owned, or machine-global files that bypass durability primitives this repo already ships and uses elsewhere. Each is a silent-data-loss window, and in every case the fix is to route through an existing helper, not to invent one: # Finding file:line The safe primitive that already exists F5 writeSettings() is a naked fs.writeFileSync for settings.json/settings.local.json (sole writer for claude/gemini/antigravity/qwen/hermes/codebuddy) bin/install.js:960 atomicWriteFileSync (temp+rename) at src/runtime-hooks-surface.cts:107, already used for Codex/Cursor hooks.json F6 #338 migration coerces readSettings()===nul
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 open-gsd/gsd-core, 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 open-gsd/gsd-core acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 85.4% were successfully merged into the primary branch.
open-gsd/gsd-core has a recorded first-timer success rate of 39.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 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 68.7 places open-gsd/gsd-core in the Welcoming tier.
The external pull request merge rate is 85.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
open-gsd/gsd-core does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for open-gsd/gsd-core 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.