MetaCall: The ultimate polyglot programming experience.
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 12%
Response Time: 9h
First Timer Success: -
metacall/core has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in metacall/core respond to incoming external pull requests in approximately 8.6 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 51.4 places metacall/core in the B tier.
The external contributor pull request merge rate for metacall/core is 11.8%, based on public PR activity from non-core contributors.
metacall/core currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in metacall/core 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/metacall/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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~6 hours (15% approval). Large PRs (>500 lines) take ~41 hours (15% approval). Keep your diff compact for rapid review.
Goal Record exact docs debt. Freeze baseline so later diffs stay reviewable. Tasks List all files under docs/ with line counts and status: active, stub, stale. Record empty headings in docs/README.md: section 6 API, 5.3.1.1-5.3.1.7, 5.3.2.1-5.3.2.2, 5.3.3.1, 5.5 Serialization, 5.6 Memory Layout. Record TOC bug: 4.2 and 4.3 nested under 4.1 though headings are level 3 siblings. Record branch mix: docs/README.md uses master image links, README.md uses develop. Record broken ref: .github/PULL_REQUEST_TEMPLATE.md links to docs/README.md#63-debugging, actual section is 7.3. Inventory loaders: 21 wired in source/loaders/CMakeLists.txt plus orphans source/loaders/deno_loader/ and source/loaders/kind_loader/ with no CMake entry. Inventory ports: 15 wired in source/ports/CMakeLists.txt, plus nim_port/ and scala_port/ unwired. Note anomaly: OPTION_BUILD_PORTS_TS exists but source/ports/ts_port/ dir is absent. Inventory tests: ~175 targets in source/tests/CMakeLists.txt (verify exact act
Goal Overhaul MetaCall documentation and governance. Make docs correct, complete, and maintainable. Add clear support tiers for OS, language, port, and loader. Add roadmap and security policy. Improve contributor and agent guides. Why Docs live in one large file docs/README.md (~1212 lines). Many sections are empty. Version tables list EOL runtimes. Loader and port tables miss real targets and list future targets that already exist. Governance files are missing at root. Contributors and agents lack clear build and test rules and even project aim or future tasks. Scope Restructure docs/ with Diataxis layout and docs-as-code checks. Refresh reference content for core, reflect, loaders, ports, serials, detours, CLI. Define Tier 1, 2, 3 for OS x arch x loader x port. Update all runtime version data and platform tables. Add ROADMAP.md and SECURITY.md. Improve CONTRIBUTING.md, CODE_OF_CONDUCT.md, SUPPORT.md, AGENTS.md. Modernize C, C++, Clang and toolchain baselines. Fix links, images, TOC,
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 metacall/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 metacall/core acknowledge new external contributions in approximately 8 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 11.8% were successfully merged into the primary branch.
metacall/core has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~8 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 51.4 places metacall/core in the Solid tier.
The external pull request merge rate is 11.8%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, metacall/core 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 metacall/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.