🎁 Gleam's standard library
C-Rank Grade: B (Solid) - 54/100
External PR Merge Rate: 67%
Response Time: 20h
First Timer Success: 50%
gleam-lang/stdlib has a recorded first-timer success rate of 50.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in gleam-lang/stdlib respond to incoming external pull requests in approximately 19.6 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 53.7 places gleam-lang/stdlib in the B tier.
The external contributor pull request merge rate for gleam-lang/stdlib is 66.7%, based on public PR activity from non-core contributors.
gleam-lang/stdlib currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Active maintainer team in gleam-lang/stdlib 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/gleam-lang/stdlib?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 12:00 to 16:00 UTC (12:00 - 16:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~13 hours (83% approval). Large PRs (>500 lines) take ~94 hours (30% approval). Keep your diff compact for rapid review.
import gleam/io import gleam/string pub fn main() { io.println(string.drop_start("广州abcdefghijklmn", 0)) io.println(string.drop_start("广州abcdefghijklmn", 1)) io.println(string.drop_start("广州abcdefghijklmn", 2)) io.println(string.drop_start("广州abcdefghijklmn", 3)) } outputs on the JS target: 广州abcdefghijklmn bcdefghijklmn efghijklmn fghijklmn So the first two characters are counted as 3 each. unsafe_byte_slice is used here with byte offsets: stdlib/src/gleam/string.gleam Line 236 in c6f7cee unsafe_byte_slice(string, prefix_size, byte_size(string) - prefix_size) It calls string_byte_slice, which contrary to its name does not operate on bytes but UTF-16 code units: stdlib/src/gleam_stdlib.mjs Line 202 in c6f7cee export function string_byte_slice(string, i
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 gleam-lang/stdlib, 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 gleam-lang/stdlib acknowledge new external contributions in approximately 19 hours. Out of all submitted pull requests from non-core authors in the last 180-day window, 66.7% were successfully merged into the primary branch.
gleam-lang/stdlib has a recorded first-timer success rate of 50.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~19 hours. 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 53.7 places gleam-lang/stdlib in the Solid tier.
The external pull request merge rate is 66.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, gleam-lang/stdlib 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 gleam-lang/stdlib 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.