quarkusio/code.quarkus.io

Code Quarkus - Start coding with Quarkus

Owned by Red Hat · part of IBM

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

quarkusio/code.quarkus.io has 100+ stars and 70+ forks on GitHub, is written in Java, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 41 minutes ago
Added to GitGenius on October 12th, 2026
Created on June 18th, 2019
Open Issues & Pull Requests: 47 (+0)
GitHub issues: Enabled
Number of forks: 73
Total Stargazers: 142 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.1 hours
Mean response time: 48.9 days
90th percentile: 100.1 days
Tracked items: 24

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 540 days
Stale 30+ days: 9
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • feature (19)
  • bug (6)
  • good first issue (1)
  • pinned (1)
  • wontfix (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Code Quarkus is a web application framework for building customizable project starter interfaces powered by Quarkus and React.

The tool solves the problem of providing developers with a guided, interactive way to bootstrap Quarkus projects with selected extensions and configurations. It works as a fullstack React library built on the Quarkus Web Bundler, combining a backend API with a frontend UI that can be extended and reused across different implementations. The architecture separates concerns into distinct modules: web dependencies, a base library containing both the API and React components, and a community application that demonstrates the default implementation.

Adoption suits teams building Quarkus-based platforms or wanting to offer customized project generation experiences to their users. The modular design allows organizations to extend the base library for their own branded versions without forking the entire codebase, as demonstrated by existing implementations. The tool exposes its API through OpenAPI documentation, making it straightforward to understand available endpoints and integrate with other systems.

The project maintains automated staging deployments that refresh approximately fifteen minutes after merges to the main branch, enabling rapid feedback on changes. Promotion to production is fully automated through acceptance tests, removing manual deployment steps. The development workflow is streamlined with a just-based command system for local development and production builds, with both API and UI code organized in clearly separated directories within the base module.