RIMES — modern macOS IME (rime-scholay): librime + buffer workbench
C-Rank Grade: B (Solid) - 42/100
External PR Merge Rate: 15%
Response Time: 16d
First Timer Success: 100%
scholay/rimes has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in scholay/rimes respond to incoming external pull requests in approximately 393.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 41.8 places scholay/rimes in the B tier.
The external contributor pull request merge rate for scholay/rimes is 15.4%, based on public PR activity from non-core contributors.
scholay/rimes currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in scholay/rimes. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in scholay/rimes focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/scholay/rimes?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 ~256 hours (23% approval). Large PRs (>500 lines) take ~1890 hours (15% approval). Keep your diff compact for rapid review.
当前里程碑 2026-08-16，主分支完成原生 Windows commit-only 基础： x64 / Win32 Release `/W4 /WX` 构建； 两个架构各 6 项 CTest； TSF → Broker → librime → UTF-16 上屏链路； Windows 11 实机 `nihao` + Space → `你好`； x64 / x86 注册同时验证，且不改变默认输入法； GitHub Actions 构建并上传明确标注 `UNSIGNED`、14 天有效的工程 Artifact。 实现：4c20c39、2209b09、cfcd830 CI：https://github.com/scholay/rimes/actions/runs/31946051204 设计边界：https://github.com/scholay/rimes/blob/main/platforms/windows/native/README.md 发布边界 当前 Artifact 仅供工程验证，不是普通用户可安装版本，也不应作为完整 Windows 产品发布。它尚未实现预编辑/候选窗、Broker 登录启动、自包含运行时、安装升级流程和 macOS 功能对等。 社区预览版前的工作 实现预编辑、候选列表、翻页、选择与取消交互； 实现 Broker 登录启动、单实例
Note本 issue 由维护者根据 Linux.do 公开讨论 整理，并非原反馈者直接提交。 当前是待复现的兼容性调查；记录不代表已经承诺实现兼容层或排期。 用户场景 部分用户依赖 Typinator 等文本扩展工具，通过短缩写插入常用文本或代码片段，希望启用 RIMES 后仍能维持原有工作流。 当前需要确认 RIMES 使用 InputMethodKit marked text 管理组字；缓冲开启时，文字先留在工作台，用户确认后才通过统一的 Delivery.insert 路径投递给宿主。依赖逐键监听，或在宿主中回删、替换缩写的文本扩展工具，可能因此出现不触发、重复、丢字或触发时机变化。 需要先区分： 缓冲关闭时，ASCII / 英文输入是否能正常触发 Typinator。 缓冲开启时，扩展应在进入缓冲前发生，还是在显式投递后由宿主侧发生。 中文组字、英文方案和 ASCII 直通是否表现一致。 原生 App、浏览器和 Electron
Note本 issue 记录维护者整理的社区需求；记录不代表承诺排期，也不表示 RIMES 将支持任意第三方方案。 当前基线（2026-09-17） RIMES 当前维护五套核心方案：雾凇全拼、自然码双拼、小鹤双拼、五笔 86、英文。可选并击扩展有自己受维护的 schema/keymap 路径。 RIMES 数据位于 ~/Library/RIMES，与鼠须管的 ~/Library/Rime 隔离；活跃引擎不得共享 userdb/LevelDB。产品尚未实现通用、受支持的任意第三方 Rime 方案导入流程。 目标 提供可理解、可验证、可恢复的第三方 Rime 方案导入与启用流程，而不是为每种方案增加硬编码实现。 范围 定义至少一种受支持来源，例如本地方案目录或方案包。 导入前检查 schema 文件、依赖、schema ID、来源与许可证信息。 安装到隔离的 RIMES 用户数据目录，绝不修改 App bundle。 部署后可发现、选择并持久保留导入方案。 支持更新、移除
Note本 issue 跟踪已发布 Data / Input-Schemes Preview 的真实桌面验收，不承诺完整的 Windows 或 Linux 原生 RIMES 产品。 当前基线（2026-09-17） Windows 与 Linux 的 Data / Input-Schemes Preview 复用五套受维护核心方案： rime_ice double_pinyin double_pinyin_flypy wubi86 english 可选并击数据也随包提供，但跨批分离击键配对仍是 macOS 前端行为。Windows 依赖既有 Weasel；Linux 依赖 Fcitx5 Rime 或 IBus Rime。CI 已覆盖审计后的数据闭包、包完整性与安装事务，但这不是真实桌面打字验收。 独立的 Windows 原生 TSF 基础层由 #8 跟踪；其工程测试不能替代本 issue 的 Weasel/Fcitx5/IBus 验收。 目标 建立可复现的真实桌面验收矩阵，再把具体失败拆成独立 issue。 范围 Windows 10/11 + 官方 Weasel。 Linux 桌面 + Fcitx5 Rime、IBus Rime；有条件时覆盖 X11 与 Wayland。 物理机或可交互桌面虚拟机；只运行 CI 脚本不计入验
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 scholay/rimes, 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 scholay/rimes acknowledge new external contributions in approximately 16 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 15.4% were successfully merged into the primary branch.
scholay/rimes has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~16 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 41.8 places scholay/rimes in the Solid tier.
The external pull request merge rate is 15.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, scholay/rimes 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 scholay/rimes 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.