Meshery published 7 release events in 30 days and 30 releases in 90 days. That is not quiet maintenance. It looks like an active control plane project tightening its server, CLI, UI, schemas, and provider boundaries at the same time.

Meshery describes itself as an extensible Kubernetes manager and cloud native manager. Its site claims 380+ built-in integrations across CNCF projects, clouds, Kubernetes clusters, and existing tools. The GitHub repository uses the same positioning, Meshery, the cloud native manager, and ToolVitals tracks 10,245 GitHub stars for the project.

The interesting signal is not one huge launch. It is the density of cleanup and compatibility work after the 1.0 line. Recent releases include post-login redirect handling, typed schema-version copies, event metadata canonicalization, Docker CLI pinning, provider metadata key fixes, server error handling, mesheryctl test work, and UI dependency updates. That reads like a team paying down control-plane edge cases, not chasing a single splashy feature.

This matters because Meshery sits in the messy part of DevOps. It touches Kubernetes, cloud native integrations, design imports, provider flows, policy evaluation, and CLI workflows. A release stream full of camelCase migrations, schema bumps, redirect-loop fixes, and error-shape cleanup is boring in the best possible way. Those are the seams that hurt users when they go stale.

What ToolVitals cannot infer

ToolVitals can see public activity signals: 10,245 stars, 7 release events in 30 days, 30 releases in 90 days, a 100 health score, a 100 shipping score, and a 99 ToolVitals score. It can also see that Meshery has an Apache-2.0 license signal and fits the OSI-approved OSS class in this dataset.

ToolVitals cannot prove that Meshery works well in your cluster. It does not measure code quality, user satisfaction, upgrade pain, production reliability, revenue, or whether the 380+ integration claim maps to the exact integrations your team needs. The recent releases show active maintenance, but they do not prove operational fit.

How it compares

Pulumi is hotter by ToolVitals score math, with a 221.6 hot score, 25,239 stars, and 17 release events in 30 days. Meshery sits lower on raw heat at 193.1, but it still posts a perfect 100 shipping score and more than 10k stars.

Jenkins is the useful peer for boring reliability. It has 25,288 stars, 10 release events in 30 days, and a 100 shipping score. Meshery is smaller by stars, but its 7 release events in 30 days keep it in the same active-maintenance conversation rather than the dormant-tool pile.

Recommendation

If your team needs a Kubernetes and cloud native management layer with a visible Apache-2.0 OSS development stream, evaluate Meshery now, especially if integrations, CLI workflows, and provider-driven management matter. Do a hands-on trial before betting on it. The public signals say the project is alive and shipping, not that it will fit your architecture without friction.

Sources