A multiplatform, compile-time dependency injection framework for Kotlin
C-Rank Grade: S (Elite) - 74/100
External PR Merge Rate: 96%
Response Time: 1d
First Timer Success: 100%
ZacSweers/metro has a recorded first-timer success rate of 100.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ZacSweers/metro respond to incoming external pull requests in approximately 25.5 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 73.9 places ZacSweers/metro in the S tier.
The external contributor pull request merge rate for ZacSweers/metro is 96.4%, based on public PR activity from non-core contributors.
ZacSweers/metro currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Highly welcoming maintainers in ZacSweers/metro. Prompt code reviews with positive guidance for new contributors.
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/ZacSweers/metro?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 11:00 to 15:00 UTC (11:00 - 15:00 UTC local).
Limited recent maintainer review activity recorded for this repository. Prediction based on heuristic baseline.
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~17 hours (96% approval). Large PRs (>500 lines) take ~122 hours (43% approval). Keep your diff compact for rapid review.
Enter your branch size and test coverage below to forecast review turnaround and get 1-click git splitting commands.
Alternative open-source projects with active maintainers in Kotlin.
A Nostr relay in your phone
On-device speech SDK for Android — ASR, TTS, VAD, and noise cancellation powered by ONNX Runtime with Qualcomm NNAPI acceleration
Archive viewer for TVs
From @bnorm in kotlinlang While there isn't an "official" way to share information, it is possible to access some FIR elements from IR using the metadata property: val IrClass.firClass: FirClass? get() = (metadata as? FirMetadataSource.Class)?.fir Combine that with the ability to add custom data to FIR declarations, you should be able to store information in FIR and access it from IR: class CustomData(...) object CustomDataAttribute : FirDeclarationDataKey() var FirClass.customData: CustomData? by FirDeclarationDataRegistry.data(CustomDataAttribute) val IrClass.customData: CustomData? get() = (metadata as? FirMetadataSource.Class)?.fir?.customData Dumped this into an LLM for some inspo in case anyone wants to take some cracks at this Plan: FIR Attribute Migration for Metro Compiler This document outlines a plan to use FIR attributes (FirDeclarationDataKey / FirDeclarationDataRegistry) to share precomputed analysis data between the FIR and IR phases of the Metro compiler. This will
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 ZacSweers/metro, 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 ZacSweers/metro acknowledge new external contributions in approximately 1 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 96.4% were successfully merged into the primary branch.
ZacSweers/metro has a recorded first-timer success rate of 100.0%. Repositories ranked Elite 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 73.9 places ZacSweers/metro in the Elite tier.
The external pull request merge rate is 96.4%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ZacSweers/metro 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 ZacSweers/metro 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.