Jenkins is old enough to be taken for granted, but the maintenance signal is not stale. ToolVitals tracks a 100 health score, 100 shipping score, 99 ToolVitals score, 25,285 GitHub stars, 20 GitHub releases in 90 days, and 10 release events in 30 days. For a mature CI/CD automation server, that is the interesting part: Jenkins is still moving.

The official site still positions Jenkins plainly: an open source automation server for building, deploying, and automating projects, backed by hundreds of plugins. The GitHub repository describes it the same way, Jenkins automation server, and shows a public project with a long release and tag history. ToolVitals marks Jenkins as OSI-approved OSS with an MIT license signal, so it is fair to call it open source here.

The real signal is maintenance depth

The recent activity is not just version churn. Jenkins 2.563 shipped as a weekly release with UI refinements, bundled plugin updates, and bug fixes. The 2.555.2 release candidate pointed users to an LTS track, an announcement thread, an artifact download, and later official changelog and upgrade guide links. That looks like boring release machinery, which is exactly what CI infrastructure needs.

The blog stream backs up the same story. A Java 21 upgrade write-up reported one production Jenkins environment dropping monthly mean memory use from 33 to 34 GB down to 28 GB after moving from Java 17, without app-level code changes. A Secret Guard Plugin announcement focused on hardcoded secret detection in jobs, Pipeline definitions, parameters, environment variables, and command content. A Plugin of the Month post highlighted the Coverage Plugin as a unified path for coverage and mutation coverage reporting.

That combination matters. Jenkins is not betting on one flashy feature. The public material points to platform upkeep, security hygiene, plugin modernization, and contributor onboarding.

Community work is part of the product surface

Jenkins also announced 5 Google Summer of Code 2026 project slots. The selected projects include AI-assisted user guidance, documentation access, Outlook SMTP with OAuth, Plugin Modernizer Stats Visualization, and retooling the Jenkins Success Stories site. Two follow-up posts from GSoC contributors describe work on plugin modernization dashboards and a Gatsby to Vite migration for stories.jenkins.io.

That is not core release velocity by itself. But for Jenkins, the website, plugin modernization tooling, and contributor pathways are not side quests. They are how a large plugin-heavy project keeps itself legible.

What ToolVitals cannot infer

ToolVitals can see release events, GitHub stars, public release cadence, website availability, SSL signals, and score outputs. It cannot see whether your Jenkins instance is pleasant to operate, whether a plugin you depend on is healthy, or whether your team has enough internal knowledge to maintain it safely.

It also cannot infer user satisfaction, revenue, security posture inside private deployments, or code quality from these metrics alone. A 100 health score is a strong public maintenance signal. It is not a guarantee that Jenkins will fit your architecture or make your pipelines less painful.

The Java 21 memory result should also be read narrowly. It came from a specific production environment, described as handling more than 10,000 daily builds, more than 1,000 active users, and more than 100 connected agents. It is useful evidence that modern JVM upgrades can matter for Jenkins operations. It is not a universal benchmark.

Comparisons

Against nearby DevOps tools, Jenkins looks less hyped but not asleep. Pulumi has 25,233 GitHub stars, a 100 shipping score, and 18 release events in 30 days. SST has 26,011 GitHub stars, a 100 shipping score, and 14 release events in 30 days. Jenkins sits in the same star neighborhood with 25,285 stars and 10 release events in 30 days.

The comparison gets stranger outside pure DevOps. n8n has 189,324 stars and 31 release events in 30 days, but ToolVitals classifies it as fair-code, not OSI-approved open source. LangChain has 137,425 stars, 15 release events in 30 days, and OSI-approved OSS status. Jenkins is not winning the attention contest. It is showing the kind of steady release discipline that large CI installations should care about more than star velocity.

Recommendation

If your team needs a self-hosted CI/CD automation server with a mature plugin model, evaluate Jenkins seriously because the project still shows strong public maintenance signals: 100 health score, 100 shipping score, 20 GitHub releases in 90 days, and ongoing release, plugin, security, and community work.

If you need a newer workflow automation product or a managed-first developer platform, compare Jenkins against n8n, Pulumi, and SST on operating model before features. Jenkins is the right candidate when control, plugin depth, and long-running infrastructure discipline matter more than novelty.

Sources