本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI content discovery agent: understands you, then proactively finds content across Bilibili, Xiaohongshu, Douyin, YouTube, X, Zhihu, Reddit, Weibo and the open web.（support deepseek harness plugin）
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 54%
Response Time: 2d
First Timer Success: 45%
whiteguo233/OpenBiliClaw has a recorded first-timer success rate of 45.5%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in whiteguo233/OpenBiliClaw respond to incoming external pull requests in approximately 43.2 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 55.5 places whiteguo233/OpenBiliClaw in the A tier.
The external contributor pull request merge rate for whiteguo233/OpenBiliClaw is 54.2%, based on public PR activity from non-core contributors.
whiteguo233/OpenBiliClaw does not currently have active "good first issue" tags indexed, but accepts external contributions through standard GitHub issue tracking.
本地私有、开源的自进化跨平台 AI 内容发现 Agent：先理解你，再主动从 B站、小红书、抖音、YouTube、X、知乎、Reddit、微博等平台与开放 Web 寻找内容。（支持 deepseek harness 插件） | Local-first open-source cross-platform AI content discovery agent: understands you, then proactively finds content across Bilibili, Xiaohongshu, Douyin, YouTube, X, Zhihu, Reddit, Weibo and the open web.（support deepseek harness plugin）
Responsive & active maintainer team in whiteguo233/OpenBiliClaw. Reviews pull requests with focus on project architectural goals.
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/whiteguo233/OpenBiliClaw?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 13:00 UTC (13:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 10:00 to 14:00 UTC (10:00 - 14:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~28 hours (68% approval). Large PRs (>500 lines) take ~207 hours (24% approval). Keep your diff compact for rapid review.
背景 openbiliclaw/bilibili/ 是系统访问 B 站 API 的唯一出口，目前接入层已经相当完整（Cookie 认证、WBI 签名搜索、412/v_voucher 分级风控冷却、扩展搜索兜底任务桥、收藏/稍后再看写入、弹幕 outcome、近期供给 lane 等 14+ 项）。这次是想围绕「优化/适配」梳理一下还有哪些值得深挖的方向，先做开放性讨论，具体范围后面再定。 候选优化方向 1. 接口字段与数据覆盖补齐 get_video_info() 目前未填充 B 站 /x/web-interface/view 已返回的 data.tag / data.tname / data.tname_v2 / data.cid，这四块结构化信号被浪费（related: #57） 是否补充 CC 字幕（/x/player/v2）、弹幕、直播、充电等更多信号面 2. 风控 / 限流策略 搜索冷却（base 600s / 180s）、v_voucher 阈值的持续校准与恢复策略 多 client / 多进程共享冷却状态的一致性（当前仅实例内共享） 明确「风控恢复」后的探测节奏，避免长时
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 whiteguo233/OpenBiliClaw, 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 whiteguo233/OpenBiliClaw acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 54.2% were successfully merged into the primary branch.
whiteguo233/OpenBiliClaw has a recorded first-timer success rate of 45.5%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~1 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 55.5 places whiteguo233/OpenBiliClaw in the Welcoming tier.
The external pull request merge rate is 54.2%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
whiteguo233/OpenBiliClaw does not have open beginner labels indexed currently, but external PRs for bugs and documentation improvements are evaluated via normal issue triage.
All metrics displayed for whiteguo233/OpenBiliClaw 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.