micronaut-projects/micronaut-core

Micronaut Application Framework

View on GitHub ↗Jump to charts ↓

micronaut-projects/micronaut-core has 6k+ stars and 1k+ forks on GitHub, is written in Java, and was last pushed on Oct 16, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 44 minutes ago
Added to GitGenius on September 10th, 2026
Created on March 7th, 2018
Open Issues & Pull Requests: 720 (+0)
GitHub issues: Enabled
Number of forks: 1,226
Total Stargazers: 6,433 (+0)
Total Subscribers: 165 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.2 days
Mean response time: 264.9 days
90th percentile: 1072.2 days
Tracked items: 1,092

Maintainer activity

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

At least 56% of micronaut-core's 9 maintainers work at Oracle. 6 say where they work, and 5 of those are Oracle.

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 11, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 12% of issues opened in the past year have never received a reply. 85% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "info: workaround available" is answered fastest, typically in about 29 hours, while "status: validated" waits about 3 months. Almost all tracked open issues have seen activity in the last three months. 67% 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: 485
New in 7 days: 9
Closed in 7 days: 10
Avg open age: 1,215 days
Stale 30+ days: 445
Stale 90+ days: 42

Recent activity

Opened in 7 days: 9
Closed in 7 days: 7
Comments in 7 days: 5
Events in 7 days: 20

Top labels

  • type: bug (436)
  • type: enhancement (250)
  • status: under consideration (192)
  • status: example attached (105)
  • status: awaiting validation (96)
  • relates-to: http-server (87)
  • info: workaround available (64)
  • status: awaiting feedback (64)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Micronaut is a modern, JVM-based full stack framework designed for building modular, easily testable applications with support for Java, Kotlin, and Groovy.

Micronaut addresses the overhead of traditional JVM frameworks by shifting framework infrastructure computation from runtime to compile time. Rather than using reflection, proxies, or runtime bytecode generation, the framework pre-computes dependency injection, aspect-oriented programming, and auto-configuration during compilation. This approach delivers fast startup times, reduced memory footprint, and minimal runtime overhead while maintaining the full feature set developers expect from a comprehensive framework.

Micronaut suits teams building microservices, serverless applications, or cloud-native systems where startup time and memory efficiency matter. It provides distributed configuration, service discovery, HTTP routing, and client-side load balancing alongside core capabilities like dependency injection and AOP. The framework is particularly valuable for containerized deployments and resource-constrained environments. Developers familiar with Spring, Spring Boot, or Grails will recognize the programming model, as the core team drew on experience building those frameworks to inform Micronaut's design.

The project maintains active development with regular updates to its core framework and ecosystem. The team sustains the codebase through the Micronaut Foundation and continues to expand language support and integration options. Documentation is comprehensive and kept current alongside releases. The project uses semantic versioning and clearly marks experimental or internal APIs, providing stability guarantees for production use.