Durable streams on object storage
C-Rank Grade: A (Welcoming) - 70/100
External PR Merge Rate: 90%
Response Time: 1d
First Timer Success: 100%
PicoMQ/picomq has a recorded first-timer success rate of 100.0%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in PicoMQ/picomq respond to incoming external pull requests in approximately 34.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 69.9 places PicoMQ/picomq in the A tier.
The external contributor pull request merge rate for PicoMQ/picomq is 90.5%, based on public PR activity from non-core contributors.
PicoMQ/picomq currently has 8 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in PicoMQ/picomq. Ensure PR scope matches issue requirements closely before requesting review.
Discussions in PicoMQ/picomq 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/PicoMQ/picomq?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 23:00 UTC (23:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 22:00 to 02:00 UTC (22:00 - 02:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (96% approval). Large PRs (>500 lines) take ~115 hours (41% approval). Keep your diff compact for rapid review.
Summary A Terraform harness that stands up a PicoMQ cluster on GCP, same shape as harness/terraform/aws. The Fly page already points at GCP as the other hyperscaler. There is no harness and no docs page yet. The AWS module is the template to copy, so this is the smaller of the two cloud ports. Shape harness/terraform/gcp, docs page next to operations/deployment/aws. Cloud Run or GKE for nodes, Cloud SQL Postgres for metadata, GCS for the object store, internal load balancer, Cloud DNS, Secret Manager for the bootstrap token. Workload identity for GCS, no static keys on the node. node_count = 1 is --routing local. node_count >= 2 is --routing redirect with per-node hostnames. Existing VPC + two private subnets, same opt-in as AWS vpc_id. Notes Keep outputs parallel to AWS (endpoints, bootstrap_secret, bucket, metadata endpoint) so a bench job can target either cloud with the same script. Start by mirroring harness/terraform/aws file for file. Change only the resources that have to be
Summary Same shape as the Flink example, for Spark Structured Streaming. Read from PicoMQ with subscribePattern, transform, write to a sink. Notes examples/spark, PySpark so it stays short. startingOffsets, checkpointing to local disk or S3, at-least-once. Same constraints note as Flink: one partition per topic, no transactions.
Summary A runnable example that reads PicoMQ topics with the Flink Kafka connector, does a windowed aggregate, and writes the result back to another topic. Flink is the most common ask for "does the Kafka listener actually work with X". One committed example answers it and doubles as an integration check. Notes examples/flink, docker compose with a pico node, Flink JobManager and TaskManager. Use KafkaSource / KafkaSink with a topic pattern, since Pico deployments create many small topics. Pico conventions: one partition per topic and constraints: no transactions.
Summary Java client for the Pico protocol, same surface as the Go and TypeScript clients: create, append, read, tail (SSE), delete. Kafka users on the JVM already have a client. This is for teams that want the Pico HTTP protocol without hand-rolling requests. Notes Mirror the method names and options of client/go so docs can share examples. Publish to Maven Central under com.picomq. Docs page under /docs/client/java.
There's a TypeScript client under client/typescript. Go apps have to speak HTTP by hand. Add an official Go client that mirrors that API: connect for pico and ds create, append, read, subscribe Producer with durable acks retries and SSE subscribe Ship it under client/go.
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 PicoMQ/picomq, 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 PicoMQ/picomq acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 90.5% were successfully merged into the primary branch.
PicoMQ/picomq has a recorded first-timer success rate of 100.0%. 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 69.9 places PicoMQ/picomq in the Welcoming tier.
The external pull request merge rate is 90.5%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, PicoMQ/picomq currently has 8 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for PicoMQ/picomq 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.