Who Contributes to and Uses CMake?

CMake is maintained with contributions from Kitware Inc. and several research and government institutions, and it is used by engineers at companies such as Johnson & Johnson, Medtronic, and John Deere. According to cmake.org, the project sees over 2 million downloads per month. If you are evaluating whether CMake is a safe long-term dependency for a C++ project, the contributor list and the published user testimonials on cmake.org are the two pieces of evidence worth checking first.

Who contributes to CMake

The cmake.org homepage lists the following organizations under "CMake Contributors":

The mix matters: a commercial maintainer (Kitware) plus government- and research-funded contributors is a common pattern for infrastructure tooling that has to stay vendor-neutral. Kitware is also the organization that runs CMake training and offers custom builds and support, so the same company that maintains the tool is the one you would contact for commercial help.

Who uses CMake

cmake.org publishes short testimonials from engineers at the following organizations:

• Johnson & Johnson — Alexander Drew, Staff Software Engineer: CMake lets teams get new projects running quickly.
• Pacific Northwest National Laboratory — Cameron Rutherford, Software Engineer: describes it as the only tool that lets him build C++ projects without substantial overhead.
• Medtronic — James Armes, Principal Software Engineer: switching from bjam was a large boost to development efficiency.
• John Deere — Ashish Patil, Lead Engineer: cites platform independence and the ability to connect multiple small project libraries.
• PickNik — Tyler Weaver, Staff Software Engineer: packages hundreds of packages and finds config modules hard to maintain and teach.
• DroneUp — Keith Bennett, Senior Software Engineer III: uses CMake together with CTest and CPack for deployments and code safety.

These span medical devices, national labs, agriculture equipment, robotics, and drone software — regulated or safety-adjacent industries where build reproducibility tends to be a hard requirement rather than a preference.

What the adoption numbers say

cmake.org states that CMake is "the de-facto standard for building C++ code, with over 2 million downloads a month." Treat that as a popularity signal, not a quality guarantee: high download volume indicates a large installed base and therefore a large pool of people who have hit the same problems you will, but it says nothing about whether CMake fits your specific build.

How to use this when deciding

• If you need long-term maintenance confidence, the contributor list is the relevant evidence: Kitware plus national labs and a federal medical library suggests the project is not dependent on a single company's continued goodwill.
• If you work in a regulated industry, the Medtronic, Johnson & Johnson, and Sandia names are the closest analogues to your situation and worth weighing more than the download count.
• If you need commercial support, note that Kitware — a listed contributor — is also the entity offering training, custom builds, and support through cmake.org.
• If you are comparing build systems, this page gives you contributor and user evidence only. It does not compare CMake against alternatives on features, so pair it with the feature list (single-source builds on multiple platforms, cross-platform packaging, out-of-source builds, system introspection, cross-platform testing) before deciding.

One caveat: the testimonials are published by cmake.org itself, so they are marketing material rather than independent reviews. Use them to identify which organizations have publicly associated themselves with CMake, then look for those organizations' own engineering write-ups if you want an unvetted view.