quarkusio/quarkus-platform

Quarkus Platform aggregates extensions from Quarkus Core and those developed by the community into a single compatible and versioned set that application...

Owned by Red Hat · part of IBM

View on GitHub ↗Jump to charts ↓

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

Summary Information

Updated 1 hour ago
Added to GitGenius on October 12th, 2026
Created on September 30th, 2019
Open Issues & Pull Requests: 17 (+0)
GitHub issues: Disabled - open counts may still include pull requests.
Number of forks: 107
Total Stargazers: 163 (+0)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

GitHub issues are disabled for this repository, so issue analytics and the issue explorer are not available.

Detailed Description

Quarkus Platform is a dependency management tool that aggregates Quarkus extensions from core and community sources into a single compatible and versioned set for application developers.

The platform solves the problem of extension compatibility by collecting dependency constraints from individual Quarkus extensions and generating unified platform artifacts that ensure extensions can be used together without conflicts. It includes an integration testsuite that validates all included extensions work in combination, and produces a bill of materials, JSON descriptor, and properties files that developers reference to align dependency versions across their applications.

Developers should adopt this tool if they are building applications on Quarkus and want to use multiple extensions without manually resolving version conflicts. It suits projects that need a stable, tested combination of extensions rather than managing individual extension versions independently. The platform is particularly valuable for teams using community-developed extensions alongside Quarkus Core, as it guarantees compatibility across the entire stack.

The project maintains active coordination through a dedicated mailing list for platform participants to discuss releases and changes. Development includes comprehensive tooling for generating platform artifacts and managing dependency constraints, with configuration options for release management, external Maven repositories, and handling extensions with or without bill of materials files. The project provides detailed documentation on platform configuration, testing procedures, and the generation of platform project layouts.