How we build
Project levels
Every project in the community carries a maturity level, so you know what you're adopting before you clone it. Three levels, modeled on the OWASP project lifecycle.
Strategic & mature
The community's reference implementations. Flagship projects have sustained maintainer investment, regular versioned releases, full documentation, a stability contract, and real adoption. If you're evaluating the community's work, start here.
Released & maintained
Complete and ready for real-world use. Production projects have shipped a stable release and are actively maintained, but are narrower in scope or earlier in their lifecycle than a flagship.
Early & experimental
Where new work enters the community. Incubator projects are public so you can evaluate them and shape their direction, but expect breaking changes between versions — don't build production dependencies on them yet. They live on GitHub only until they graduate.
The lifecycle
How projects move between levels
New projects enter as incubators. That's true whether the idea comes from the core team or from a community contribution — everything starts public, experimental, and open to feedback.
Incubator → Production happens when a project ships a stable release with documentation, a version policy, and a demonstrated maintenance commitment — it's something you can rely on for its stated scope.
Production → Flagship reflects sustained investment and adoption: a flagship project is strategic to the community's mission, with an ongoing release cadence, a stability contract, and a track record of responding to issues and contributions.
Visibility follows the level. Flagship projects are fully represented across the community site — cards, structured metadata, sitemaps, and llms.txt. Production projects are included in those discovery surfaces at a minimal level. Incubator projects are deliberately left out of them: they're discoverable on GitHub, carrying their level pill, until they graduate.
Levels are reviewed as projects evolve and are recorded here. Each project's GitHub README carries a level pill that links back to this page. Shared infrastructure — the plugin marketplace, this website — supports the projects and isn't leveled.