Server that stores allure-results, generates Allure 2 reports and serves them over a REST API and a web UI; Spring Boot on Java 25, shipped as a Docker image and a Helm chart.
C-Rank Grade: B (Solid) - 55/100
External PR Merge Rate: 100%
Response Time: <1h
First Timer Success: 100%
kochetkov-ma/allure-server has a recorded first-timer success rate of 100.0%. Repositories ranked B typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in kochetkov-ma/allure-server respond to incoming external pull requests in approximately 0.4 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 54.6 places kochetkov-ma/allure-server in the B tier.
The external contributor pull request merge rate for kochetkov-ma/allure-server is 100.0%, based on public PR activity from non-core contributors.
kochetkov-ma/allure-server currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Collaborative maintainer environment in kochetkov-ma/allure-server. Reviews community pull requests with focus on project quality.
Discussions in kochetkov-ma/allure-server focus heavily on practical implementation feedback, code formatting standards, and issue reproduction details.
Unlinked PRs without issue context and changes that fail automated test suites face the highest review friction.
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/kochetkov-ma/allure-server?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 00:00 UTC (00:00 UTC in your timezone). Recommended submission window is Monday - Friday from 00:00 to 04:00 UTC (00:00 - 04:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~4 hours (96% approval). Large PRs (>500 lines) take ~2 hours (45% approval). Keep your diff compact for rapid review.
Summary The published image kochetkovma/allure-server:2.13.9 contains 9 CRITICAL CVEs flagged by Trivy: 2 in the Alpine base layer (OpenSSL) and 7 in bundled Java dependencies (Apache Tika, embedded Tomcat, Spring Security). Because these are all CRITICAL and several have public exploits (notably CVE-2025-24813 RCE in Tomcat and CVE-2025-66516 XXE in Tika), running this image in any environment that processes externally-supplied content is risky. Affected version Image: kochetkovma/allure-server:2.13.9 (Docker Hub) Base: amazoncorretto:21-alpine (resolved to Alpine 3.20.2 at the time of this scan) Same root causes are likely present in earlier 2.13.x tags built against the same Spring Boot 3.3.1 / Vaadin 24.4.4 chain. Steps to reproduce Have Docker installed. Run a Trivy scan against the published image: docker run --rm \ -v /var/run/docker.sock:/var/run/docker.sock \ -v /tmp/trivy-cache:/root/.cache/trivy \ aquasec/trivy:latest image \ --severity CRITICAL \ --scann
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 kochetkov-ma/allure-server, 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 kochetkov-ma/allure-server acknowledge new external contributions in approximately <1 hour. Out of all submitted pull requests from non-core authors in the last 180-day window, 100.0% were successfully merged into the primary branch.
kochetkov-ma/allure-server has a recorded first-timer success rate of 100.0%. Repositories ranked Solid typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~<1 hour. 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 54.6 places kochetkov-ma/allure-server in the Solid tier.
The external pull request merge rate is 100.0%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, kochetkov-ma/allure-server 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 kochetkov-ma/allure-server 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.