This document is the canonical inventory of public, first-party repositories owned by the Microcks GitHub organization. It records repository purpose, lifecycle status and responsible ownership without treating external forks, private repositories or every repository as a governed subproject.
Last reviewed: September 09, 2026
The inventory includes public repositories owned by Microcks that are not forks. External forks and private repositories are excluded. Archived first-party repositories remain listed so that their status and history stay visible.
The central Maintainers and Code Owners list is authoritative for project governance roles. A repository CODEOWNERS file identifies the people automatically requested to review changes in that repository; it does not grant a project governance role by itself. When no repository-specific ownership record exists, the top-level Maintainers are responsible.
Changes to repository lifecycle or ownership must update this inventory in the same decision or pull request. The Maintainers review the inventory at least annually.
CNCF CLOMonitor evaluates selected Microcks repositories using the repository-specific check sets declared in the CNCF CLOMonitor configuration.
CLOMonitor provides an external project health and conformance signal. This inventory remains authoritative for Microcks repository scope, lifecycle and ownership. A repository not configured in CLOMonitor is not necessarily unsupported or excluded from the project.
- Core product: The main Microcks application and its primary delivery components.
- Integration: An extension or adapter connecting Microcks to another platform or developer workflow.
- SDK or library: A reusable client, runtime or testing library.
- Tooling: Automation, packaging or utilities supporting Microcks users and contributors.
- Demonstration or workshop: Educational examples and hands-on learning material; these are not production deliverables.
- Website or content: Documentation, websites, catalogs and reusable content.
- Community or governance: Project-wide governance, community coordination and CNCF metadata.
- Infrastructure: Images or other assets used to build and operate Microcks services.
- Experimental: Exploratory work for which compatibility and long-term support are not yet promised.
- Active: Supported work that may receive features, fixes, releases or content updates.
- Maintenance: Supported work limited primarily to security and critical fixes.
- Deprecated: Work with a documented replacement or migration path that is preparing for archival.
- Archived: Read-only historical work that no longer receives fixes or releases.
A lifecycle change requires the formal decision process defined in GOVERNANCE.md. Before a repository becomes Deprecated, its documentation should identify any replacement and migration path. Archived repositories remain in this inventory. Any future transfer to a dedicated archive organization must be approved as a repository removal and recorded here, with redirects or successor links where practical.
| Repository | Category | Purpose | Lifecycle | Responsible owners | Ownership record |
|---|---|---|---|---|---|
| microcks | Core product | API mocking and testing platform | Active | @lbroudoux, @yada, @SebastienDegodez | CODEOWNERS |
| microcks-operator | Core product | Kubernetes Operator for deploying and managing Microcks | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-cli | Tooling | Command-line client for Microcks APIs | Active | @lbroudoux, @yada, @Harsh4902, @Caesarsage | CODEOWNERS |
| microcks-mcp-server | Integration | MCP server for interacting with Microcks from agents and MCP clients | Active | @lbroudoux, @yada | CODEOWNERS |
| microcks-agent-skills | Tooling | Agent skills and integrations for Microcks workflows | Active | @lbroudoux, @yada, @SebastienDegodez | CODEOWNERS |
| microcks-postman-runtime | SDK or library | HTTP bridge for executing Postman tests | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-java | SDK or library | Java Testcontainers integration | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-go | SDK or library | Go Testcontainers integration | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-node | SDK or library | Node.js and TypeScript Testcontainers integration | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-dotnet | SDK or library | .NET Testcontainers integration | Active | @SebastienDegodez, @lbroudoux | CODEOWNERS |
| microcks-quarkus | Integration | Quarkus extension for Microcks Dev Services and contract testing | Active | @lbroudoux | CODEOWNERS |
| microcks-aspire | Integration | .NET Aspire integration for hosting and testing with Microcks | Active | @SebastienDegodez, @lbroudoux | CODEOWNERS |
| microcks-java-client | SDK or library | Java client for the Microcks API | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-go-client | SDK or library | Go client for the Microcks API | Active | @lbroudoux | CODEOWNERS |
| microcks-docker-desktop-extension | Integration | Docker Desktop extension for running Microcks | Active | @lbroudoux, @hguerrero | CODEOWNERS |
| microcks-backstage-provider | Integration | Backstage provider for synchronizing API entities from Microcks | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-jenkins-plugin | Integration | Jenkins plugin for running Microcks tests | Active | @lbroudoux, @yada | CODEOWNERS |
| microcks-spectral-ruleset | Tooling | Spectral rules for Microcks OpenAPI and AsyncAPI conventions | Active | @lbroudoux | CODEOWNERS |
| import-github-action | Tooling | GitHub Action for importing API specifications into Microcks | Active | @lbroudoux | CODEOWNERS |
| test-github-action | Tooling | GitHub Action for running Microcks tests | Active | @lbroudoux | CODEOWNERS |
| homebrew-tap | Tooling | Homebrew formulae for Microcks tools | Active | Top-level Maintainers | Central MAINTAINERS |
| api-tooling | Tooling | API development, testing, validation and migration utilities | Active | Top-level Maintainers | Central MAINTAINERS |
| hub.microcks.io | Website or content | Public catalog for reusable Microcks mocks and tests | Active | @lbroudoux, @yada | CODEOWNERS |
| community-mocks | Website or content | Community mocks and tests published through the Microcks Hub | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-quickstarters | Website or content | Reusable API examples for industry and vertical standards | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-images | Infrastructure | Base container images used by Microcks | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-testcontainers-java-spring-demo | Demonstration or workshop | Spring Boot example using Microcks Testcontainers | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-quarkus-demo | Demonstration or workshop | Quarkus example using Microcks Dev Services and Testcontainers | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-testcontainers-node-nest-demo | Demonstration or workshop | NestJS example using Microcks Testcontainers | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-go-demo | Demonstration or workshop | Go example using Microcks Testcontainers | Active | @lbroudoux | CODEOWNERS |
| microcks-testcontainers-dotnet-demo | Demonstration or workshop | .NET example using Microcks Testcontainers | Active | @SebastienDegodez, @lbroudoux | CODEOWNERS |
| microcks-aspire-demo | Demonstration or workshop | .NET Aspire example using the Microcks Aspire integration | Active | Top-level Maintainers | Central MAINTAINERS |
| api-lifecycle | Demonstration or workshop | End-to-end API lifecycle demonstration | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-testcontainers-java-workshop | Demonstration or workshop | Workshop for the Java Testcontainers integration | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-quarkus-workshop | Demonstration or workshop | Workshop for Microcks Quarkus Dev Services | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks-testcontainers-dotnet-workshop | Demonstration or workshop | Workshop for the .NET Testcontainers integration | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks.io | Website or content | Microcks website and documentation source | Active | Top-level Maintainers | Central MAINTAINERS |
| microcks.github.io | Website or content | Published Microcks website content | Active | Top-level Maintainers | Central MAINTAINERS |
| .github | Community or governance | Canonical organization governance and community health files | Active | Top-level Maintainers | Central MAINTAINERS |
| community | Community or governance | Community meetings, steering material and collaborative resources | Active | Top-level Maintainers | Central MAINTAINERS |
| .project | Community or governance | CNCF project metadata and automation | Active | Project Maintainers and Steering Committee | CODEOWNERS |
| Repository | Category | Purpose | Lifecycle | Responsible owners | Ownership record |
|---|---|---|---|---|---|
| microcks-ansible-operator | Core product | Former Ansible-based Kubernetes Operator | Archived | Top-level Maintainers for archive stewardship | CODEOWNERS |
| microcks-go-operator | Core product | Former Go-based Kubernetes Operator | Archived | Top-level Maintainers for archive stewardship | No repository-specific ownership record |
| microcks-keycloak | Infrastructure | Former Microcks Keycloak distribution | Archived | Top-level Maintainers for archive stewardship | No repository-specific ownership record |
| microcks-azure | Tooling | Former Azure deployment templates and scripts | Archived | Top-level Maintainers for archive stewardship | No repository-specific ownership record |
The following repositories are not entries in this first-party inventory:
- External forks:
agent-bond,backstage,community-module-registry,community-operators,community-operators-1,community-operators-prod,graphql.github.io,hub,java,microk8s-community-addons,protoc-jar,quarkus-extension-catalogandwebsite. - Private repositories: Private repositories are excluded from this public inventory and are not enumerated here.
This inventory does not control distribution of organization-level files. Those files are replicated to the repositories where they are needed and relevant according to the deliberate per-file scope and exclusions in the replication workflow.