quarkusio/registry.quarkus.io

Quarkus Extension Registry application

Owned by Red Hat · part of IBM

View on GitHub ↗Jump to charts ↓

quarkusio/registry.quarkus.io has 10+ stars and 10+ 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 59 minutes ago
Added to GitGenius on October 12th, 2026
Created on January 13th, 2021
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 18
Total Stargazers: 13 (+0)
Total Subscribers: 5 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 1.8 hours
Mean response time: 2.1 days
90th percentile: 6.8 days
Tracked items: 10

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 3
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 369 days
Stale 30+ days: 3
Stale 90+ days: 2

Recent activity

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

Top labels

  • good first issue (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Quarkus Extension Registry is a backend application that indexes and serves metadata about Quarkus extensions and platforms through a REST API.

The tool solves the problem of discovering and managing Quarkus extensions and platforms by maintaining a centralized registry. It indexes extensions and platforms from configured sources, then exposes this data through multiple endpoints: REST API for direct queries, Maven repository endpoints for dependency resolution, and GraphQL queries for programmatic access. The application uses PostgreSQL for persistence and can be deployed via Docker.

Teams building Quarkus applications should adopt this tool if they need to query available extensions, determine platform compatibility with specific Quarkus versions, or integrate extension discovery into their build tooling. The registry distinguishes between platform extensions and non-platform extensions, allowing consumers to filter by compatibility with their target Quarkus version. It serves both human-readable REST endpoints and Maven-compatible artifact endpoints, making it suitable for integration into build systems and IDE tooling.

The project maintains active CI automation that deploys new container images on every commit. Development follows a pattern of continuous integration with automated deployments to a container registry.