Microcks

Microcks is an open-source, cloud-native API mocking and testing platform for developers and platform teams that turns API specifications and microservice…

  • Development
  • Tools & Utilities
Microcks is an open-source, cloud-native API mocking and testing platform for developers and platform teams that turns API specifications and microservice assets into live mocks and runs contract conformance and non-regression tests to validate integration early.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

62/100 Good

Maintained
100last commit 8 days ago
Popular
662,089 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
201 serious finding, 2 minor, CI, tests, OpenSSF Scorecard 7.1/10

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
2,089
Open issues
55
Last commit
2026-11-13
Latest release
1.16.0
License
Apache-2.0
Activity
declining

Checked 4 days ago - source: GitHub (microcks/microcks)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Set the right Microcks and Keycloak URLs In the Helm install, set microcks.url and keycloak.url to the address people and services will actually use. If these are wrong, login redirects and saved API calls break. source
  • Set up a Keycloak user for login Keycloak is the login service in front of Microcks, so create or verify a user before your first login. The admin username and password are in the Helm notes or the microcks-keycloak-admin secret, and without them you may not be able to sign in. source
  • Save the gRPC TLS certificate if you need gRPC mocks If you'll test gRPC services, copy the gRPC TLS certificate shown in the Helm notes into your gRPC client's trusted certificates. Without it, gRPC calls can fail because the client doesn't trust the server. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which Helm settings need to match my exposed address in a Kubernetes install?

Set microcks.url and keycloak.url to the address that people and services will actually use. If these values are wrong, login redirects and saved API calls can break.

What do I need to know about Keycloak before the first login?

Keycloak is the login service in front of Microcks, so create or verify a user before signing in. The admin username and password are in the Helm notes or the microcks-keycloak-admin secret.

Why might gRPC calls to a Kubernetes-deployed mock fail?

If you will test gRPC services, copy the gRPC TLS certificate shown in the Helm notes into your gRPC client's trusted certificates. Without it, the client may not trust the server and calls can fail.

Why does importing an API artifact report no service found or an empty result?

Check that the artifact follows the expected conventions for its API type. You should also confirm that examples are defined, because Microcks relies on them.

Answers sourced from github.com, microcks.io

Community

Collected 48 days ago - public community threads