A reactive notebook for Python — run reproducible experiments, query with SQL, execute as a script, deploy as an app, and version with git. Stored as pure Python. All in a modern, AI-native editor.
C-Rank Grade: A (Welcoming) - 67/100
External PR Merge Rate: 73%
Response Time: 2d
First Timer Success: 53%
marimo-team/marimo has a recorded first-timer success rate of 52.9%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in marimo-team/marimo respond to incoming external pull requests in approximately 39.3 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 67.0 places marimo-team/marimo in the A tier.
The external contributor pull request merge rate for marimo-team/marimo is 73.3%, based on public PR activity from non-core contributors.
marimo-team/marimo currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in marimo-team/marimo. Prompt code reviews with positive guidance for new contributors.
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/marimo-team/marimo?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 15:00 to 19:00 UTC (15:00 - 19:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~30 hours (92% approval). Large PRs (>500 lines) take ~225 hours (33% approval). Keep your diff compact for rapid review.
Description Marimo command mode supports Esc, then b to create a new Python cell below the focused cell. Creating a SQL cell requires an additional conversion step: Esc b Cmd/Ctrl + Shift + L It would be useful to have a command-mode shortcut such as Esc, then q that directly creates and focuses a new SQL cell below the current cell. Hex supports this interaction pattern: in command mode, q creates a SQL cell. Its keyboard-shortcut documentation describes command mode and notes that its Add Cell menu exposes shortcuts for creating specific cell types. Suggested solution Add a configurable action such as command.createSQLCellAfter, with q as its default command-mode binding. Expected behavior: Press Esc to enter command mode. Press q. Create a new SQL cell immediately below the selected cell. Focus the new SQL editor. Do not execute the currently selected cell. Continue using the existing default SQL engine and output settings. Expose the action in the keyboard-shortcut settings so u
Describe the bug The integrated terminal doesn't show up anywhere in the editor — not in the Developer Panel, and not in the Sidebar either. I don't see any config option disabling the terminal (e.g. no enable_terminal = false), so this doesn't seem to be a configuration issue. Will you submit a PR? Yes Environment Environment { "marimo": "0.23.15", "editable": false, "location": "~/PycharmProjects/DashFisioanimal/.venv/Lib/site-packages/marimo", "OS": "Windows", "OS Version": "11", "Processor": "Intel64 Family 6 Model 141 Stepping 1, GenuineIntel", "Python Version": "3.12.13", "Locale": "pt_BR", "Binaries": { "Browser": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/151.0.0.0 Safari/537.36", "Node": "v24.11.0", "uv": "0.11.26 (x86_64-pc-windows-msvc)" }, "Dependencies": { "click": "8.4.2", "docutils": "0.23", "itsdangerous": "2.2.0", "jedi": "0.19.2", "markdown": "3.10.2", "narw
Summary quack is a new protocol that allows a duckdb instance to connect to a duckdb server. This is currently not supported in the Data source viewer Details when using quack, the duckdb client attaches to the server. It then becomes available as an attached database to the client. As seen in the screenshot, the server remote can be accessed by the client in the query FROM remote.hello Full notebook import marimo __generated_with = "0.23.6" app = marimo.App(width="medium") @app.cell def _(): import marimo as mo import duckdb import dlt return (duckdb,) @app.cell def _(duckdb): server_con = duckdb.connect("quack.duckdb") return (server_con,) @app.cell def _(duckdb): client_con = duckdb.connect(":memory:") return (client_con,) @app.cell def _(server_con): server_con.execute("INSTALL quack FROM core_nightly;LOAD quack;") server_con.execute("CALL quack_serve('quack:localhost', token='fooz');") return @app.cell def _(server_con):
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 marimo-team/marimo, 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 marimo-team/marimo acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 73.3% were successfully merged into the primary branch.
marimo-team/marimo has a recorded first-timer success rate of 52.9%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 67.0 places marimo-team/marimo in the Welcoming tier.
The external pull request merge rate is 73.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, marimo-team/marimo 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 marimo-team/marimo 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.