A governance model determines who holds commit rights, sets a project's roadmap, and whose interests guide it. It helps explain why a project is developing as it is and what to reasonably expect next; maintainability signals describe its current condition. section 4.3.2
Two recurring open-source patterns illustrate different levels of maintainer concentration:
- Single-maintainer projects depend on one person. The risk depends partly on how deeply the project is woven into your codebase: a replaceable leaf utility differs from a dependency spread across many components. section 4.3.2
- Small-team community projects have a handful of contributors and no formal governance; multiple active maintainers provide a higher safety net. section 4.3.2
Dependency risk
Core-js illustrates single-maintainer concentration. Assessing its risk means considering how extensively the dependency is woven into your code, not treating every use as equally difficult to replace. section 4.3.2
