A next.js web application that integrates AI capabilities with draw.io diagrams. This app allows you to create, modify, and enhance diagrams through natural language commands and AI-assisted visualization.
C-Rank Grade: A (Welcoming) - 66/100
External PR Merge Rate: 65%
Response Time: 23h
First Timer Success: 67%
DayuanJiang/next-ai-draw-io has a recorded first-timer success rate of 66.7%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in DayuanJiang/next-ai-draw-io respond to incoming external pull requests in approximately 22.7 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 65.7 places DayuanJiang/next-ai-draw-io in the A tier.
The external contributor pull request merge rate for DayuanJiang/next-ai-draw-io is 64.7%, based on public PR activity from non-core contributors.
DayuanJiang/next-ai-draw-io currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
A next.js web application that integrates AI capabilities with draw.io diagrams. This app allows you to create, modify, and enhance diagrams through natural language commands and AI-assisted visualization.
Balanced & professional review environment in DayuanJiang/next-ai-draw-io. 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/DayuanJiang/next-ai-draw-io?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 03:00 UTC (03:00 UTC in your timezone). Recommended submission window is Monday - Wednesday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~15 hours (81% approval). Large PRs (>500 lines) take ~109 hours (29% approval). Keep your diff compact for rapid review.
Note: This template is just a guide. Feel free to ignore the format entirely - any feedback is welcome! Don't let the template stop you from sharing your ideas. Current Behavior Describe how the feature currently works. Proposed Enhancement How you'd like this to be improved. Motivation 有OLLAMA本地输入，用LM Studio的也不少，能增加这个本地模型接入方式嘛？ Screenshots / Mockups If applicable, add screenshots or mockups to illustrate the proposed changes. Additional Context Any other information about the enhancement request.
Note: This template is just a guide. Feel free to ignore the format entirely - any feedback is welcome! Don't let the template stop you from sharing your ideas. Feature Description Add automatic update functionality to the Electron desktop app so users are notified when new versions are available and can update without manually downloading from GitHub releases. Problem Context Currently, the Electron app has no auto-update mechanism: Users must manually check GitHub releases for new versions Users need to download and install updates manually There's no in-app notification when updates are available This creates friction for users who may not know a new version exists or may be running outdated versions with bugs that have been fixed. Proposed Solution Implement auto-update using electron-updater: Install electron-updater package Add auto-update initialization in electron/main/index.ts: import { autoUpdater } from 'electron-updater'; app.whenReady().then(() => { autoUpdater.chec
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 DayuanJiang/next-ai-draw-io, 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 DayuanJiang/next-ai-draw-io acknowledge new external contributions in approximately 22 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 64.7% were successfully merged into the primary branch.
DayuanJiang/next-ai-draw-io has a recorded first-timer success rate of 66.7%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~22 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 65.7 places DayuanJiang/next-ai-draw-io in the Welcoming tier.
The external pull request merge rate is 64.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, DayuanJiang/next-ai-draw-io 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 DayuanJiang/next-ai-draw-io 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.