Artemis - Interactive Learning with Automated Feedback
C-Rank Grade: S (Elite) - 70/100
External PR Merge Rate: 69%
Response Time: -
First Timer Success: 62%
ls1intum/Artemis has a recorded first-timer success rate of 62.0%. Repositories ranked S typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in ls1intum/Artemis 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 69.8 places ls1intum/Artemis in the S tier.
The external contributor pull request merge rate for ls1intum/Artemis is 69.3%, based on public PR activity from non-core contributors.
ls1intum/Artemis currently has 3 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in ls1intum/Artemis. Reviews community pull requests with focus on project quality.
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/ls1intum/Artemis?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 Monday - Wednesday 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 (87% approval). Large PRs (>500 lines) take ~115 hours (31% approval). Keep your diff compact for rapid review.
Describe the bug Excessive problem statement length causes a hard-to-understand "Error on field "translation-not-found[artemisApp.checklistAnalysisRequest.problemStatementMarkdown]"" error. To Reproduce Create a new programming exercise or edit an existing one Exchange the Problem Statement with large amounts (e.g. 100.000 words) of Lorem Ipsum blindtext Click on Analyze Problem Statement The error message shows "Error on field "translation-not-found[artemisApp.checklistAnalysisRequest.problemStatementMarkdown]"" Expected behavior A proper error message should notify the user of a too-long-to-analyse problem statement. Screenshots Which version of Artemis are you seeing the problem on? Hash: 4498bd0 What browsers are you seeing the problem on? Firefox Additional context No response Relevant log output
Describe the bug The points field allows users to enter values with excessive decimal precision (e.g., 1.1111111111111112). While the system rounds the value, the resulting number remains overly precise and unintuitive. Allowing such high precision is unnecessary for grading purposes and leads to cluttered and potentially confusing values in the UI. via @MarkusPaulsen To Reproduce Create a programming exercise In the exercise creation page, enter a points value with excessive decimal precision (e.g., 1.1111111111111112) Save the exercise Observe the displayed points value Expected behavior The system should restrict decimal precision to a reasonable level (e.g., 1–2 decimal places) Screenshots Which version of Artemis are you seeing the problem on? 9.0.0 What browsers are you seeing the problem on? Firefox Additional context No response Relevant log output
Describe the bug In the Continuous Plagiarism Control settings, the input field for "Significant similarity response period (days)" is not fully legible. The text or the box itself is partially obscured, making it difficult for instructors to read or enter data depending on their screen size or browser view. To Reproduce Log in as an Instructor. Navigate to the Create/Edit Text Exercise page. Open the Continuous Plagiarism Control settings. Observe the "Significant similarity response period" field on different screen resolutions or window sizes. Expected behavior The field label and input box should be fully visible and responsive across all screen resolutions, ensuring the "days" unit and the input value are clearly readable. Screenshots Which version of Artemis are you seeing the problem on? 9.0.0 What browsers are you seeing the problem on? Chrome Additional context No response Relevant log output
Describe the bug Via @MarkusPaulsen To Reproduce Create/Edit a programming exercise Set 1e-3 as a bonus point value Expected behavior Same validation as with regular points Screenshots Which version of Artemis are you seeing the problem on? 9.0.0 What browsers are you seeing the problem on? Chrome Additional context No response Relevant log output
Describe the bug Problem statement: Accepts excessively large input (e.g. 1.000.000 words lorem ipsum) without any error => Might be an issue if storage can be exhausted via @MarkusPaulsen To Reproduce As an instructor, create a Programming Exercise In the Problem Statement, paste excessively long text Click Generate Expected behavior Text should be trimmed/truncated Screenshots No response Which version of Artemis are you seeing the problem on? 9.0.0 What browsers are you seeing the problem on? Chrome Additional context Other fields tend to impose limits Relevant log output
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 ls1intum/Artemis, 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 ls1intum/Artemis acknowledge new external contributions in approximately -. Out of all submitted pull requests from non-core authors in the last 180-day window, 69.3% were successfully merged into the primary branch.
ls1intum/Artemis has a recorded first-timer success rate of 62.0%. 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 69.8 places ls1intum/Artemis in the Elite tier.
The external pull request merge rate is 69.3%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, ls1intum/Artemis currently has 3 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for ls1intum/Artemis 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.