A high-performance observability data pipeline.
C-Rank Grade: A (Welcoming) - 65/100
External PR Merge Rate: 59%
Response Time: -
First Timer Success: 40%
vectordotdev/vector has a recorded first-timer success rate of 40.4%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in vectordotdev/vector respond to incoming external pull requests in approximately 0.0 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 65.4 places vectordotdev/vector in the A tier.
The external contributor pull request merge rate for vectordotdev/vector is 59.1%, based on public PR activity from non-core contributors.
vectordotdev/vector currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (100% critical review signals). Ensure PRs strictly follow guidelines before requesting review in vectordotdev/vector.
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/vectordotdev/vector?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 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Wednesday - Friday from 17:00 to 21:00 UTC (17:00 - 21:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~16 hours (74% approval). Large PRs (>500 lines) take ~115 hours (27% approval). Keep your diff compact for rapid review.
A note for the community Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request If you are interested in working on this issue or have submitted a pull request, please leave a comment Use Cases Keyboard users read a docs page with the Tab key. Each Tab moves focus to the next focusable element, and the browser scrolls the page to that element. On vector.dev, headings in the page content are not focus stops. Only links, buttons, and code blocks get focus. On a page with long sections and few links, one Tab can jump past one or more full sections. The user cannot move through the document section by section. Example on https://vector.dev/docs/setup/quickstart/: after the breadcrumbs, the Tab sequence in the content is: button "Script" button "Docker" pre "curl --proto '=https' ..." a "installation methods" pre "vector --version" a "configuration file" ... No heading in the page gets focu
Summary Three counter metrics in the memory enrichment table are missing the _total suffix, violating the instrumentation spec. From docs/specs/instrumentation.md: "Counters MUST end with total" Metrics to rename Current name Correct name memory_enrichment_table_failed_insertions memory_enrichment_table_failed_insertions_total memory_enrichment_table_failed_reads memory_enrichment_table_failed_reads_total memory_enrichment_table_ttl_expirations memory_enrichment_table_ttl_expirations_total These are defined in lib/vector-common/src/internal_event/metric_name.rs as CounterName variants. Their descriptions already say "The total number of..." confirming the intent was to follow the _total convention. Notes These are breaking changes for anyone scraping these metrics directly. The old names should be kept as deprecated aliases or the rename should be accompanied by a changelog entry.
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 vectordotdev/vector, 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 vectordotdev/vector acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 59.1% were successfully merged into the primary branch.
vectordotdev/vector has a recorded first-timer success rate of 40.4%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~-. 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 65.4 places vectordotdev/vector in the Welcoming tier.
The external pull request merge rate is 59.1%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, vectordotdev/vector 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 vectordotdev/vector 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.