🚀 One-stop solution for creating your AI twin from chat history 💡 Fine-tune LLMs with your chat logs to capture your unique style, then bind to a chatbot to bring your digital self to life.
C-Rank Grade: B (Solid) - 46/100
External PR Merge Rate: 10%
Response Time: 6d
First Timer Success: -
xming521/WeClone has a recorded first-timer success rate of 0.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in xming521/WeClone respond to incoming external pull requests in approximately 147.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 45.9 places xming521/WeClone in the B tier.
The external contributor pull request merge rate for xming521/WeClone is 10.0%, based on public PR activity from non-core contributors.
xming521/WeClone currently has 2 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in xming521/WeClone. Reviews community pull requests with focus on project quality.
Discussions in xming521/WeClone 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/xming521/WeClone?utm_source=github&utm_medium=badge)
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 02:00 UTC (02:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~96 hours (12% approval). Large PRs (>500 lines) take ~709 hours (15% approval). Keep your diff compact for rapid review.
Hey — building Neural Nexus (https://neuralnexus.site), a consent-first living personal avatar. WeClone's end-to-end chat-history avatar workflow and localized privacy filtering hit the same problem. Curious what you'd never let run unsupervised, and whether a managed consent/export path would be useful vs pure DIY.
你好，我们正在开发 Yance：一个由多个 MCP 连接器驱动的、本地优先的个人关系与沟通智能大脑。 它不是另一个聊天记录导出器或单平台机器人。微信、小红书、闲鱼、钉钉、飞书等连接器只负责在授权范围内提供消息，并明确“使用者是谁、对方是谁”；Yance 负责把使用者在不同场景中的多个身份，以及同一个人的多个账号、平台身份和关系关联起来，从长期聊天中学习双方的沟通特征。 早期系统只提供推荐回复，由人选择、修改和确认；积累足够反馈后，用户才可以按身份、账号、对象和场景开启受限、可审计、可暂停的自动回复。长期还会探索操控性沟通信号（包括通常所说的 PUA 模式）、话外意图、机会识别和多方关系策略，但所有判断都必须保留证据、反证、替代解释和不确定性。 WeClone 已经把聊天历史、表达风格学习、模型微调和聊
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 xming521/WeClone, 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 xming521/WeClone acknowledge new external contributions in approximately 6 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 10.0% were successfully merged into the primary branch.
xming521/WeClone has a recorded first-timer success rate of 0.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~6 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 45.9 places xming521/WeClone in the Solid tier.
The external pull request merge rate is 10.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, xming521/WeClone 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 xming521/WeClone 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.