Class with Excessive Number of Child Classes

An inheritance hierarchy with too many child classes becomes difficult to understand, navigate, and maintain. This complexity slows down development and code reviews, making it harder to spot logic errors, security flaws, or unintended side-effects when changes are made. The increased cognitive load on developers indirectly raises security risks, as vulnerabilities can be more easily introduced and are more time-consuming to find and fix. While the specific threshold for "excessive" can vary by project, the CISQ (Consortium for IT Software Quality) recommends a default maximum of 10 direct child classes for a single parent. Adhering to this guideline helps maintain a cleaner, more modular design, promoting code that is easier to secure and audit. Consider refactoring through techniques like composition or creating intermediate abstract classes to flatten overly deep hierarchies.