A markdown editor — and the bridge to your LLM. Local-first, MIT, ~15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.
C-Rank Grade: B (Solid) - 49/100
External PR Merge Rate: 73%
Response Time: 13d
First Timer Success: 67%
zhitongblog/solomd has a recorded first-timer success rate of 66.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in zhitongblog/solomd respond to incoming external pull requests in approximately 313.5 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 49.0 places zhitongblog/solomd in the B tier.
The external contributor pull request merge rate for zhitongblog/solomd is 72.7%, based on public PR activity from non-core contributors.
zhitongblog/solomd currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A markdown editor — and the bridge to your LLM. Local-first, MIT, ~15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.
Balanced & professional review environment in zhitongblog/solomd. Maintains strict focus on technical quality and test standards.
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/zhitongblog/solomd?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 12:00 UTC (12:00 UTC in your timezone). Recommended submission window is Monday - Thursday from 10:00 to 14:00 UTC (10:00 - 14: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 ~204 hours (91% approval). Large PRs (>500 lines) take ~1505 hours (33% 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 TypeScript.
Angular markdown component/directive/pipe/service to parse static, dynamic or remote content to HTML with syntax highlight and more...
Real-time Web Dashboard for Optuna.
No repository description available.
Hi! I noticed you have aur-solomd-bin/ ready in the repo but it hasn't been pushed to AUR yet, so I went ahead and submitted it: AUR: https://aur.archlinux.org/packages/solomd-bin Version: 4.10.2 (updated from the 4.1.0 in your aur-solomd-bin/) PKGBUILD: based on yours, with minimal changes A few things: Would you like to be added as co-maintainer? Happy to add you. If you plan to maintain it yourself in the future, I can transfer ownership — just let me know. I've also set up auto-update (checks GitHub releases daily), so it should stay current. Great editor by the way — using it daily!
Receive this error when trying to run the latest AppImage (4.10.1) in Arch Linux and Debian 13: Could not create default EGL display: EGL_BAD_PARAMETER. Aborting... Thinkpad T480, T490, and Lenovo Legion 11 Pro. This issue was reported previously on a prior AppImage version and was closed as "fixed" but does not appear to have been fixed.
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 zhitongblog/solomd, 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 zhitongblog/solomd acknowledge new external contributions in approximately 13 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 72.7% were successfully merged into the primary branch.
zhitongblog/solomd has a recorded first-timer success rate of 66.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~13 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 49.0 places zhitongblog/solomd in the Solid tier.
The external pull request merge rate is 72.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, zhitongblog/solomd 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 zhitongblog/solomd 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.