quarkusio/quarkus

Quarkus: Supersonic Subatomic Java.

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on April 7th, 2021
Created on July 6th, 2018
Open Issues & Pull Requests: 2,826 (+4)
GitHub issues: Enabled
Number of forks: 3,329
Total Stargazers: 15,933 (+0)
Total Subscribers: 262 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.5 hours
Mean response time: 158.4 days
90th percentile: 631.0 days
Tracked items: 6,554

Maintainer activity

66 people did triage or write work on this repository in the last 12 months.

At least 44% of quarkus's 66 maintainers work at IBM. 48 say where they work, and 29 of those are IBM.

Red Hat owns this repository. 6 of its people did this work here, and are not included above.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 7, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits.

How this project is maintained

About 6% of issues opened in the past year have never received a reply. 70% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "area/oidc" is answered fastest, typically in about 3 hours, while "area/hibernate-orm" waits about 25 hours. 55% of tracked open issues have had no activity in three months. 72% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1,501
New in 7 days: 67
Closed in 7 days: 41
Avg open age: 586 days
Stale 30+ days: 1,316
Stale 90+ days: 1,205

Recent activity

Opened in 7 days: 49
Closed in 7 days: 25
Comments in 7 days: 128
Events in 7 days: 534

Top labels

  • kind/bug (3,695)
  • kind/enhancement (1,813)
  • area/native-image (431)
  • area/smallrye (373)
  • area/config (369)
  • triage/needs-feedback (367)
  • area/hibernate-orm (344)
  • env/windows (344)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Quarkus is a cloud-native Java framework designed specifically for building containerized applications with minimal resource footprint and fast startup times. The project emphasizes container-first development, optimizing Java applications to run efficiently in Linux containers and Kubernetes environments while adhering to twelve-factor application principles. The framework supports both JVM and native compilation modes, allowing developers to choose between high-throughput JVM execution and native binaries optimized for resource-constrained environments.

The framework unifies imperative and reactive programming models under a single development paradigm, enabling developers to write both blocking and non-blocking code without switching between different frameworks or abstractions. Quarkus builds on established standards and widely-used technologies including RESTEasy and JAX-RS for REST APIs, Hibernate ORM and JPA for data persistence, Netty for networking, Eclipse Vert.x for reactive capabilities, Eclipse MicroProfile for microservices standards, and Apache Camel for integration patterns. This standards-based approach allows developers to leverage existing knowledge and ecosystem tools while gaining the benefits of Quarkus's optimizations.

The project prioritizes developer experience through features like hot reload during development, enabling rapid iteration without full application restarts. Build-time optimizations allow Quarkus to perform substantial processing at compile time rather than runtime, contributing to its characteristic fast startup times and reduced memory consumption. The framework positions itself as versatile enough to support applications ranging from small microservices to large monolithic systems.

The repository is classified across numerous categories reflecting its comprehensive scope: extensibility, JVM languages, developer productivity, containerization, Kubernetes integration, reactive programming, polyglot support, microservices architecture, cloud-native deployment, and performance optimization. The framework's positioning around cloud-native development, hot reload capabilities, RESTful API development, and enhanced developer experience addresses core concerns in modern application development while maintaining focus on Java performance and efficiency.