CMB2 is a developer toolkit for WordPress custom fields, metaboxes, settings pages, and forms. What makes it unique in the WordPress ecosystem is that it was purpose-built to be safely bundled inside other plugins and themes. Hundreds of WordPress products ship CMB2 as an embedded dependency — and its WP Lib Loader pattern automatically resolves version conflicts so only the newest copy loads, even when multiple plugins include it.
CMB2 doesn't meet the 5K GitHub stars threshold because WordPress developers don't install via GitHub — they install via wordpress.org and Composer, or more often, they never install it directly at all. It arrives inside something else. Our real adoption numbers tell a different story.
| Platform | Metric |
|---|---|
| WordPress.org | ~5M total downloads, 300K+ active installs |
| Packagist | 630K installs, 26 dependent packages |
| GitHub | 3,014 stars, 564 forks, 2,844 commits, 568 dependents |
| Rating | 5/5 stars across 91 reviews |
| Translations | 19 locales |
Combined reach: 5.6M+ downloads/installs across platforms.
CMB2 is developer infrastructure, not an end-user product. It was designed from the start to be bundled inside other plugins and themes. The typical path:
- A developer adds CMB2 to their plugin via Composer or bundles it directly.
- CMB2's WP Lib Loader pattern handles version conflicts automatically — when multiple plugins ship different versions, only the newest one loads. This pattern has worked reliably since 2014.
- That plugin gets installed on thousands of sites. Site owners never know CMB2 is there.
Nobody in this chain stars a GitHub repo. The 568 GitHub dependents and 26 Packagist dependents are only those with explicit declarations — the real number of products shipping CMB2 is far larger.
CMB2 may be the only WordPress plugin with 300K+ active installs that does nothing visible on its own and still maintains a perfect 5-star rating. Developers who use it love it enough to review it even though their end users never see it.
I'm Justin Sternberg (@jtsternberg), the sole lead developer and maintainer of CMB2 since its creation. I've maintained it across three companies (WebDevStudios, Zao, Awesome Motive) and through the full lifecycle of WordPress's evolution from classic to block editor. I've spoken about CMB2 at WordCamps and WPSessions, contributed to WordPress core releases, and continue active development.
WordPress is moving toward an agent-operable future. The WordPress ecosystem is exploring capabilities layers (like the Abilities API) that let AI agents safely interact with plugins. CMB2 is uniquely positioned to become the structured-meta bridge for this new paradigm.
With Claude, I plan to:
- Modernize CMB2 for current WordPress — restore full test suite, compatibility matrix, and regular release cadence.
- Integrate with the Abilities API — expose CMB2 field groups and capabilities in a machine-consumable contract so AI agents can safely read and write structured metadata.
- Build agent-safety primitives — capability-aware hooks, validation boundaries, and auditable operation logs so agents can interact with CMB2-managed data without breaking sites.
This isn't just maintenance of legacy infrastructure. It's bringing a foundational WordPress library into the AI era — and Claude is the tool that makes that feasible for a solo maintainer.
- GitHub: https://github.com/CMB2/CMB2
- WordPress.org: https://wordpress.org/plugins/cmb2/
- Packagist: https://packagist.org/packages/cmb2/cmb2