I would like to have security coverage and a stability promise when adopting this module, but neither is available when depending on an alpha release. Do you have a sense of what would be needed to stabilize this module?
Perhaps it could already be marked stable since this module does not have a PHP API. The only requirement of marking it stable would be to provide update hooks when/if the way config is stored changes. Bonus points for adding final
and @internal
all over the place in a simple patch. IOW, the module doesn't have to bug free or in its final implementation to be stable, as long as it is iterated on in a way that keeps things working for existing users.
Active
1.0
Documentation
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.