Embeddable spreadsheet engine - parse, evaluate & mutate Excel workbooks from Rust, Python, or the browser. Arrow-powered, 400+ functions.
C-Rank Grade: S (Elite) - 76/100
External PR Merge Rate: 90%
Response Time: 16h
First Timer Success: 64%
PSU3D0/formualizer has a recorded first-timer success rate of 63.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PSU3D0/formualizer respond to incoming external pull requests in approximately 15.8 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 75.8 places PSU3D0/formualizer in the S tier.
The external contributor pull request merge rate for PSU3D0/formualizer is 90.3%, based on public PR activity from non-core contributors.
PSU3D0/formualizer currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in PSU3D0/formualizer. Reviews community pull requests with focus on project quality.
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/PSU3D0/formualizer?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 16:00 UTC (16:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 14:00 to 18:00 UTC (14:00 - 18:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~10 hours (96% approval). Large PRs (>500 lines) take ~76 hours (41% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Rust.
CLI and Rust libraries for low-level manipulation of WebAssembly modules
Eloquence in Messaging
Open source math and physics engine that executes MATLAB-syntax code. Features a modern compiler, automatic GPU acceleration for large calculations, and support for math on geometry / FEA calculations.
Context We now have CONTRIBUTING.md, but once the docs site scaffold lands we should mirror a concise contributor onboarding page there. Acceptance criteria Add a Contributing page in docs site scaffold (or placeholder docs structure) Include build/test commands for Rust, Python, WASM Link to CONTRIBUTING.md as source of truth Add page to docs nav
Context The Python stubs file (bindings/python/formualizer/__init__.pyi) is generated by cargo run --bin stub_gen and can drift from Rust bindings. Proposal Add a CI job that regenerates stubs and fails if there is a diff. Acceptance criteria Add a CI step that runs stub generation in bindings/python If generated stubs differ, CI fails with a clear message Document local command needed to refresh stubs Ensure workflow works with current Python runtime setup in CI
Context Ticket: 702-github-repo-housekeeping GitHub social previews currently use a generic card. We should upload a project-branded social preview image (1280x640) to improve link previews on Slack/X/Discord/Reddit. Acceptance criteria Create a 1280x640 social preview image for Formualizer Include concise value props (e.g. Rust + Python + WASM, 320+ functions, Arrow-powered) Upload it in repository settings so link cards render the new preview Add source assets to the repo assets directory (PNG + editable source if available)
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 PSU3D0/formualizer, 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 PSU3D0/formualizer acknowledge new external contributions in approximately 15 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.3% were successfully merged into the primary branch.
PSU3D0/formualizer has a recorded first-timer success rate of 63.6%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~15 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 75.8 places PSU3D0/formualizer in the Elite tier.
The external pull request merge rate is 90.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PSU3D0/formualizer currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PSU3D0/formualizer 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.