As part of improving the overall management and organization of the module registry, there is a need to address scenarios where modules may become obsolete, unused, or not aligned with established naming or governance standards.

To support this, enhanced lifecycle management capabilities would be beneficial, including the ability to . This would allow modules to be marked as inactive prior to deletion and automatically scheduled for removal after a defined period (for example, 30 days).

Such functionality would enable teams to manage and clean up unused or redundant modules in a controlled and structured manner, rather than relying on immediate deletion, thereby improving governance, visibility, and overall maintainability of the registry.