Next generation open source Altinn platform and applications.
C-Rank Grade: S (Elite) - 71/100
External PR Merge Rate: 79%
Response Time: -
First Timer Success: 81%
Altinn/altinn-studio has a recorded first-timer success rate of 80.6%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in Altinn/altinn-studio 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 71.4 places Altinn/altinn-studio in the S tier.
The external contributor pull request merge rate for Altinn/altinn-studio is 78.7%, based on public PR activity from non-core contributors.
Altinn/altinn-studio currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Strict review standards in Altinn/altinn-studio. Ensure PR scope matches issue requirements closely before requesting review.
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/Altinn/altinn-studio?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 09:00 to 13:00 UTC (09:00 - 13: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 (35% approval). Keep your diff compact for rapid review.
An app that registers its own task for a built-in task type gets an undefined result. Whether the app's task or the built-in runs depends on which interface it implements (IServiceTask or IPipelineServiceTask) and on registration order. ServiceTaskLookupExtensions.GetServiceTasks yields every IServiceTask before every IPipelineServiceTask, and the last exact type match wins. The v9 template registers app services before AddAltinnAppServices. So: an app IPipelineServiceTask typed pdf always replaces the built-in PdfServiceTask; an app IServiceTask typed eFormidling never replaces the built-in EFormidlingServiceTask; within one interface, the built-in registered later wins. That contradicts the doc comment on ResolveByTaskType ("An app can replace a built-in task by registering its implementation after the built-in task"). This is a user error, so it is low priority. Either make the outcome consistent, or fail startup with a clear message when an app registers a task for a built-in typ
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 Altinn/altinn-studio, 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 Altinn/altinn-studio acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 78.7% were successfully merged into the primary branch.
Altinn/altinn-studio has a recorded first-timer success rate of 80.6%. Repositories ranked Elite 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 71.4 places Altinn/altinn-studio in the Elite tier.
The external pull request merge rate is 78.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, Altinn/altinn-studio 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 Altinn/altinn-studio 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.