pact-cli

Pact-CLI is a tool that ensures different software components talk to each other correctly.

  • Development
  • Tools & Utilities
Pact-CLI is a tool that ensures different software components talk to each other correctly. It acts as a bridge, sharing and checking "contracts" between systems to guarantee they understand each other’s data, preventing errors before updates are synchronised and released.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • 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.

56/100 Fair

Maintained
100last commit 18 days ago
Popular
123 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
3
Open issues
10
Last commit
2026-11-03
Latest release
v0.10.9
License
MIT
Activity
rising

Checked 18 days ago - source: GitHub (pact-foundation/pact-cli)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install the Linux Pact CLI binary Download the Pact-Reference CLI files for Linux, unzip them, and give them short names like pact_verifier_cli. Then run each with --help to confirm the right binary works, because missing or mismatched binaries will stop Pact tests from running. source
  • Set Pact mock server ports and output folder Before starting, decide the master port (default 8080), the first port number it can use for test mocks, and where Pact files are saved. If ports conflict with another app or the file folder is wrong, your tests can’t connect or you’ll chase Pact files in the wrong place. source
  • Install optional plugins only if you need them If you need the CSV plugin, run the provided pact-plugin install command with -y so it can answer yes to prompts automatically. The plugin is stored in your .pact plugins folder, and skipping the install when your tests use CSV will make those tests fail. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why can Pact broker verification fail when using pact-cli in Docker?

The verification request can fail because it lacks a Bearer token, even when the provider verifier connects. The token must be included so the broker accepts the verification.

What should I check after installing the Linux Pact CLI binary?

Unzip the Pact-Reference CLI files, give them short names such as pact_verifier_cli, and run each with --help. Missing or mismatched binaries will stop Pact tests from running.

Which ports and folder should I configure for the Pact mock server?

Set the master port, default 8080, the first port number it can use for test mocks, and the folder where Pact files are saved. Port conflicts or the wrong folder can prevent tests from connecting or make files hard to find.

How do I install the optional CSV plugin for Pact tests?

Run the provided pact-plugin install command with -y so prompts are answered automatically. The plugin is stored in the .pact plugins folder, and skipping installation when tests use CSV makes those tests fail.

Answers sourced from docs.pact.io, docs.pact.io, docs.pact.io, stackoverflow.com

Community

Collected 48 days ago - public community threads