DROOdotFOO/raxol - Open Source PR Review Scorecard

Write one app, render it to a terminal, a browser, or as agent tools. The terminal for your Gundam.

C-Rank Grade: A (Welcoming) - 65/100

External PR Merge Rate: 89%

Response Time: 7d

First Timer Success: 50%

Frequently Asked Questions

Is DROOdotFOO/raxol welcoming to first-time open-source contributors?

DROOdotFOO/raxol has a recorded first-timer success rate of 50.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.

How fast can I expect code review feedback on my pull request?

Maintainers in DROOdotFOO/raxol respond to incoming external pull requests in approximately 159.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.

What does the 65.2 C-Rank™ score (A Tier) represent?

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 65.2 places DROOdotFOO/raxol in the A tier.

What is the external contributor pull request merge rate for DROOdotFOO/raxol?

The external contributor pull request merge rate for DROOdotFOO/raxol is 89.3%, based on public PR activity from non-core contributors.

Are there Good First Issues available in DROOdotFOO/raxol?

DROOdotFOO/raxol currently has 15 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".

DROOdotFOO
DROOdotFOO/raxolA•Welcoming73
GitHub
Back to Explorer
DROOdotFOO

DROOdotFOO/raxol

73
Active (30d)A•Welcoming(65/100)Elixir

Write one app, render it to a terminal, a browser, or as agent tools. The terminal for your Gundam.

GitHub
Compare••
Jump to:

AI Maintainer Review Guidelines

Review Persona

Welcoming Community Builder

Warmth Score
8.5/10
Patience Score
8.6/10
Nitpick Rate
30%

Highly welcoming maintainers in DROOdotFOO/raxol. Prompt code reviews with positive guidance for new contributors.

Top PR Submission Do's

  • •Ensure code complies with the project coding style
  • •Keep PRs scoped to a single concern
  • •Include context and link to the related issue

Top PR Friction Pitfalls (Don'ts)

  • •Do not submit PRs without linking an issue
  • •Do not break existing tests without fixing them
  • •Do not mix unrelated refactors in a single PR
Response Velocity
6 days+
Standard maintainer review cycle

Average Response Latency

Tracks hours until a maintainer leaves a review, comment, or PR response.

Merge Efficiency
89.3%
High acceptance rate for external PRs

External Acceptance Rate

Percentage of community pull requests successfully merged into main.

First-Timer Success
50.0%
Accepts new contributor PRs

First PR Conversion

Rate at which developers submitting their first repository PR succeed.

Active Maintainers
2 core
Small core review team
Diagnostic Health HUD
89.3%
Merge Gauge
50.0%
1st-Timer
Community Vibe51/100

Embed C-Rank Badge

Show contributors that your repository actively reviews and merges external pull requests.

GetMerged C-Rank badge for DROOdotFOO/raxol
[![GetMerged C-Rank](https://getmerged.abhishekco.de/api/badge/DROOdotFOO/raxol)](https://getmerged.abhishekco.de/DROOdotFOO/raxol?utm_source=github&utm_medium=badge)

Active Good First Issues (5)

View on GitHub

Part of the Graduations epic. Goal Validate raxol_symphony (pre-alpha) against a real Linear/GitHub repo, then reserve/cut its first Hex release. Context raxol_symphony is an OTP port of OpenAI Symphony: a tracker-driven coding-agent orchestrator (Orchestrator BaseManager polls Memory/Linear/GitHub, claims eligible issues, isolates each in a per-issue workspace, runs a coding agent to terminal state). Two runners (Runners.RaxolAgent, Runners.Codex), six surfaces via PubSub, evidence framework. Full description in CLAUDE.md (Symphony section) + HANDOVER.md. Scope Live validation against a real Linear / GitHub repo (drive real issues through to PRs). Orchestrator integration of the parallel GraphAdapter (workflow_mode: :graph_parallel); per-branch pause + compensate (see TODO.md "Symphony" open items). SSH worker dispatch (worker.ssh_hosts, one-worker-lifetime-per-host). Cache wiring for the Session-backed runner (~30 min, same opt-in pattern). Hex reservation/release once a live r

📅 Opened Jul 13, 2026💬 1 comment
Quality: 80/100Contribute

Part of the Graduations epic. Human-in-the-loop / funds required for the final live step. Goal Take raxol_acp (0.2.0, pre-alpha) to its first live Base-mainnet offering, then cut the first Hex release. Context raxol_acp is code-complete on the v2 hook/event model against the deployed Base contracts (v1 memo model retired). Full state in HANDOVER.md (top ACP entries) and CLAUDE.md. The single mainnet target is xochi_cross_chain_transfer (pure-relay storefront: raxol never touches transfer funds, takes an ACP fee; the buyer signs the Xochi intent, Riddler settles). Scope (an agent prepares; a human executes the funded steps) SCA :live_bundler end-to-end: real EntryPoint, empty-callData deploy sponsorship, installed? getter selector; SolverAgent-vs-Base-staging run (see TODO.md open items). Item-4 A-path live gate Base->Tron (needs funds + Riddler RELAY_GASLESS_PULL_ENABLED; ERC-3009 blocked on Riddler#159); verify checkpoint kill-and-resume. Graduate the offering: live run on Base ma

📅 Opened Jul 13, 2026💬 0 comments
Quality: 80/100Contribute

Part of the Hermes Fast-Follow P1 epic. Tag: Funnel. Small; precondition for the desktop app's attribution. Goal Close out the OpenRouter attribution funnel so Raxol appears on openrouter.ai/rankings and the desktop app can default to it. Design ROADMAP.md P1 "OpenRouter funnel" row + TODO.md (the one remaining #414 task): The :openrouter harness already sends app-attribution headers (HTTP-Referer, X-OpenRouter-Title, X-OpenRouter-Categories) via Backend.Selector / ExecutorConfig auth. Run the #414 live smoke with a real OpenRouter key (human-in-the-loop / key required). Confirm the openrouter.ai/apps?url=https://raxol.io listing appears. Bump raxol.io site copy to v2.6 / 14 packages (the #417 site work already merged as #418). Acceptance criteria :openrouter live smoke passes with a real key (captured as a :live_*-gated test / evidence) the openrouter.ai/apps listing for raxol.io is confirmed live site copy reflects v2.6 / 14 packages Effort: S. Priority: P1. References: Backen

📅 Opened Jul 13, 2026💬 0 comments
Quality: 80/100Contribute

Part of the Hermes Fast-Follow P1 epic. Tag: CATCH-UP. Pairs with the install-funnel PowerShell path. Goal Make native Windows first-class: tune the pure-Elixir driver, add Windows CI, and take the PowerShell installer path out of "preview". Design ROADMAP.md P1 "Windows first-class" row: Tune packages/raxol_terminal/lib/raxol/terminal/io_terminal.ex (the pure-Elixir driver used on Windows in place of the termbox2 NIF). Windows CI: drop the current Windows exclusions where the pure-Elixir path can actually run; keep NIF-only tests tagged. Finish the install.ps1 path from the install-funnel issue (Windows Burrito exe, pure-Elixir driver, %LOCALAPPDATA%\raxol, user PATH, no admin). Known noise to clear Windows undefined variable stdout noise from REPL.Evaluator.base_env/0 during Benchee runs (see TODO.md "Known noise"). Acceptance criteria the pure-Elixir driver renders the playground + a real app correctly on native Windows Windows CI runs the suite (pure-Elixir path) green; NIF-

📅 Opened Jul 13, 2026💬 2 comments
Quality: 80/100Contribute

Part of the Hermes Fast-Follow P1 epic. Tag: CATCH-UP. Small, self-contained. Goal mix raxol.import --from hermes|openclaw: let a user bring an existing agent config into Raxol in one command, lowering the switching cost. Design ROADMAP.md P1 "Migration on-ramp" row: Map SOUL.md -> a Raxol persona/prompt block. Import memories into Memory.Store (the Raxol.Agent.Memory behaviour; reuse Store.Ets / the P0-4 SQLite store). Import skills (the agentskills.io-format bundle from the paid-skills issue). Map allowlists -> PermissionHook (packages/raxol_agent/lib/raxol/agent/ permission hook). Acceptance criteria mix raxol.import --from hermes and --from openclaw parse the respective config layouts memories land in a Memory.Store and are recall-able; skills load; allowlists become PermissionHook rules round-trip tested against fixture configs (real files, no network) Effort: S. Priority: P1. References: packages/raxol_agent/lib/raxol/agent/memory/, permission hook, lib/mix/tasks/. House

📅 Opened Jul 13, 2026💬 0 comments
Quality: 80/100Contribute
Looking for more Elixir beginner tasks?Explore Elixir GFI

Contributor Community Vibe Feedback

Rate what actually matters after opening a pull request here.

Have you contributed to this repo?

Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.

3 ratings required
Maintainer helpfulness
Review speed
Beginner friendliness

Contributor Compatibility & Review Speed Analysis for DROOdotFOO/raxol

When evaluating whether to contribute to DROOdotFOO/raxol, 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 DROOdotFOO/raxol acknowledge new external contributions in approximately 6 days+. 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.

Frequently Asked Questions - Contributing to DROOdotFOO/raxol

01

Is DROOdotFOO/raxol welcoming to first-time open-source contributors?

DROOdotFOO/raxol has a recorded first-timer success rate of 50.0%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.

02

How fast can I expect code review feedback on my pull request?

The initial maintainer response time averages ~6 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.

03

What does the 65.2 C-Rank™ score represent?

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 65.2 places DROOdotFOO/raxol in the Welcoming tier.

04

What is the external contributor pull request merge rate for DROOdotFOO/raxol?

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.

05

Are there beginner Good First Issues open in DROOdotFOO/raxol?

Yes, DROOdotFOO/raxol currently has 15 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.

GetMerged C-Rank™ Indexing Standard

All metrics displayed for DROOdotFOO/raxol 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.