A Simple and Universal Swarm Intelligence Engine, Predicting Anything. 简洁通用的群体智能引擎，预测万物
C-Rank Grade: B (Solid) - 51/100
External PR Merge Rate: 16%
Response Time: 11d
First Timer Success: 7%
666ghj/MiroFish has a recorded first-timer success rate of 6.7%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in 666ghj/MiroFish respond to incoming external pull requests in approximately 253.4 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 50.8 places 666ghj/MiroFish in the B tier.
The external contributor pull request merge rate for 666ghj/MiroFish is 16.3%, based on public PR activity from non-core contributors.
666ghj/MiroFish currently has 5 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (75% critical review signals). Ensure PRs strictly follow guidelines before requesting review in 666ghj/MiroFish.
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/666ghj/MiroFish?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 Tuesday - Thursday from 09:00 to 13:00 UTC (09:00 - 13:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~165 hours (20% approval). Large PRs (>500 lines) take ~1216 hours (15% approval). Keep your diff compact for rapid review.
项目 proj_80099492c72d 在“图谱构建”阶段停在 55%，页面显示 Error 和“图谱构建失败”。后端最终报错为httpx.ConnectError: [SSL: UNEXPECTED_EOF_WHILE_READING] 排查结论，日志显示，本体生成已成功，得到 10 个实体类型、9 个关系类型。随后 MiroFish 创建了 Zep 图谱并提交文本。查询批次状态时，连接先后出现 RemoteProtocolError、ConnectError；程序重试后仍收到 SSL 连接提前断开的错误，便将项目标记为失败。我随后直接查询了同一个 Zep 批次：状态是 succeeded，6/6 条处理成功，失败 0 条。因此，页面上的“构建失败”并不代表 Zep 没有建好图谱。日志中也没有额度不足的响应；这次故障不能归因于 token 余额不足。
Thanks for #798 — it fixed the failure I hit second. This is the one I hit first, and I believe it is a different bug that #798 does not cover. The difference from #795 Both end with runner_status: stopping and a report that can never be generated, but the cause is opposite: #795 / #798 this runner process alive, hard-waiting on episode.processed exited fix by shortening the wait yes no — there is no loop left to shorten recovery after restart resolves once the wait ends never, the state is on disk What happened A 40-round, 2-world run completed cleanly — both platforms reported done, 71 actions. During the shutdown wait the runner process died (in my case while Zep polling was flapping with ReadTimeout / ConnectError / RemoteProtocolError). It never wrote its terminal status. run_state.json was left as: { "runner_status": "stopping", "completed_at": null, "current_round": 40, "total_rounds": 40, "twitter_completed": true, "reddit_completed": true, "proce
Three reproducible bugs found while running self-referential simulations (MiroFish analyzing its own launch/reception) Setup: Local Docker deployment (ghcr.io/666ghj/mirofish:latest), LLM backend = openai/gpt-oss-20b via NVIDIA API (OpenAI-SDK-compatible endpoint), Zep Cloud free tier for memory. Bug 1: LLMClient.chat() crashes on content=None from reasoning models Error: 报告生成失败: expected string or bytes-like object, got 'NoneType' When it happens: Deterministically during Step 4/5 (report generation), right after the SECTION START log of the first outline section (reproduced on two independent runs, different seeds/outlines, identical failure point). Root cause (verified in shipped image code, backend/app/utils/llm_client.py, chat()): content = response.choices[0].message.content content = re.sub(r'<think>[\s\S]*?</think>', '', content).strip() Reasoning models served through OpenAI-compatible endpoints (observed: gpt-oss-20b via NVIDIA) sometimes return the output in re
Summary meta.title and meta.description are translated in every locale file but are never read anywhere in the codebase. frontend/index.html hardcodes the Chinese <title> and <meta name="description">, so the browser tab and the SEO description stay Chinese no matter which language the user selects. Evidence The keys exist and are translated in every locale: en {'title': 'MiroFish - Predict Everything', 'description': 'MiroFish - Social Media Opinion Simulation System'} zh {'title': 'MiroFish - 预测万物', 'description': 'MiroFish - 社交媒体舆论模拟系统'} But nothing consumes them. Grepping the whole repo for meta.title, meta.description, t('meta, document.title, useHead and titleTemplate across frontend/ and backend/ returns no hits — the only meta. matches are Vite's own import.meta.glob (frontend/src/i18n/index.js:4) and import.meta.env (frontend/src/api/index.js:6). Meanwhile frontend/index.html hardcodes both: <meta name="description" content="MiroFish
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 666ghj/MiroFish, 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 666ghj/MiroFish acknowledge new external contributions in approximately 10 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 16.3% were successfully merged into the primary branch.
666ghj/MiroFish has a recorded first-timer success rate of 6.7%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~10 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 50.8 places 666ghj/MiroFish in the Solid tier.
The external pull request merge rate is 16.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, 666ghj/MiroFish currently has 5 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for 666ghj/MiroFish 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.