Feather is a modern Swift-based Content Management System.
C-Rank Grade: A (Welcoming) - 56/100
External PR Merge Rate: 70%
Response Time: 5d
First Timer Success: 100%
FeatherCMS/feather 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 FeatherCMS/feather respond to incoming external pull requests in approximately 112.7 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 55.7 places FeatherCMS/feather in the A tier.
The external contributor pull request merge rate for FeatherCMS/feather is 69.6%, based on public PR activity from non-core contributors.
FeatherCMS/feather currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Growing Swift project in FeatherCMS/feather 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/FeatherCMS/feather?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 08:00 UTC (08:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 08:00 to 12:00 UTC (08:00 - 12:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~73 hours (87% approval). Large PRs (>500 lines) take ~541 hours (31% approval). Keep your diff compact for rapid review.
Reduce redundancy in generated OpenAPI definition names Problem Generated OpenAPI definitions repeat the same hierarchy in every type name. This is not limited to schemas. The same pattern appears across: Operations Path items Parameters Request bodies Responses Schemas Tags For example: WebMenuCreateOperation WebMenuUpdateOperation WebMenuIdPathItems WebMenuCreateRequestBody WebMenuDetailResponse WebMenuCreateSchema WebMenuTag Repeating the resource hierarchy in every generated type makes the code unnecessarily verbose and increases the risk of inconsistent naming or typos. Proposal Generate nested namespaces that mirror the OpenAPI resource hierarchy. For example: enum Web { enum Menu { struct CreateOperation: OperationRepresentable { ... } struct UpdateOperation: OperationRepresentable { ... } struct IdPathItems: PathItemRepresentable { ... } struct CreateRequestBody: RequestBodyRepresentable { ... } struct DetailResponse: JSONRespons
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 FeatherCMS/feather, 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 FeatherCMS/feather acknowledge new external contributions in approximately 4 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.6% were successfully merged into the primary branch.
FeatherCMS/feather 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 ~4 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 55.7 places FeatherCMS/feather in the Welcoming tier.
The external pull request merge rate is 69.6%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, FeatherCMS/feather 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 FeatherCMS/feather 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.