Low Code / Visual Scripting log processing software
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 87%
Response Time: 3d
First Timer Success: 80%
link-society/flowg has a recorded first-timer success rate of 80.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in link-society/flowg respond to incoming external pull requests in approximately 66.9 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 70.9 places link-society/flowg in the S tier.
The external contributor pull request merge rate for link-society/flowg is 86.7%, based on public PR activity from non-core contributors.
link-society/flowg currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Go project in link-society/flowg welcoming community pull requests and bug fixes.
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/link-society/flowg?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 Tuesday - Thursday from 13:00 to 17:00 UTC (13:00 - 17:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~43 hours (96% approval). Large PRs (>500 lines) take ~321 hours (39% approval). Keep your diff compact for rapid review.
Context The technical documentation has no troubleshooting guide. To help ops team operate FlowG we need to identify crash scenarios and document a recovery procedure. Crash Scenarios For each scenario, we want to identify the error messages that might appear in the logs. If no log help identify the problem, they should be added. Disk full: Can FlowG starts when the disk is full? What happens if the disk become full while FlowG is running? Can data loss happen? Can it be detected and alerted on? Once the disk is not full anymore, does FlowG keeps running without issues? Does recovery require downtime? High load average: Can FlowG still reliably store logs while the server is under heavy load? Can data loss happen? Can it be detected and alerted on? Once load goes down, does FlowG keeps running without issues? Does recovery require downtime? Network partition in cluster mode: (we rely on FoundationDB here) Do we notice data loss after the network partition is over? Are FlowG
Scope pipelines Desired Behavior Data Model: erDiagram NATS_JETSTREAM_FORWARDER { string_array servers "Required" dynamic_string subject "Required" dynamic_string body "Default: @expr:toJSON(log)" dynamic_string message_id "Optional deduplication ID" string expected_stream "Optional assertion" integer publish_timeout "Default: 5, Unit in seconds" string auth_mode "none, user_password, token, credentials" string username "Required if auth_mode=user_password" string password "Required if auth_mode=user_password" string token "Required if auth_mode=token" string credentials "Required if auth_mode=credentials" string tls_ca "Optional PEM CA bundle" string tls_certificate "Optional PEM client certificate" string tls_private_key "Required if tls_certificate is specified" string tls_server_name "Optional hostname override" boolean tls_insecure_sk
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 link-society/flowg, 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 link-society/flowg acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 86.7% were successfully merged into the primary branch.
link-society/flowg has a recorded first-timer success rate of 80.0%. Repositories ranked Elite typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 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 70.9 places link-society/flowg in the Elite tier.
The external pull request merge rate is 86.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, link-society/flowg currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for link-society/flowg 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.