Make a stable release with security compliance

I am sorry, but I would need a co-maintainer before I could make a stable release of this module subject to the security advisory policy -- I'm semi-retired and sometimes traveling and unable to respond to security team inquiries. So, I would need to have someone else co-maintaining the module with me before I would be willing to take on the responsibility of another module under the security advisory policy. Sorry!

Hey Jennifer-

I'd be willing to be co-maintainer with you on this module if you're still willing. I have a client who needs this functionality, so two birds, one stone. Let me know!

Thanks, Pamela

Hi! Yes, I would love to have a co-maintainer. Have you maintained a project on drupal.org before? If not, you might want to read
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...

Usually, a person would become a co-maintainer after submitting patches on a few issues in the project to demonstrate familiarity with the project and its code. This project doesn't have many issues, but there is one that probably needs a patch, if you would like to work on it:
#3102754: Redirect hardenning

Thanks for your interest!

Hi! I'm actually in the process of stopping my volunteer work with the Drupal project. @pamelaalies -- are you willing to maintain this project? If so, I'll ask to have ownership transferred to you. If I don't hear back from you, or you're not willing to be the maintainer any more, I'll be following the process in
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
to abandon this project.

Thanks!

I haven't heard back in a month, so I'm going to follow the procedure on
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
and mark this project as Abandoned.

If someone would like to take it over, please follow the procedure on
https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or...
to take over the abandoned project.

I like the idea of this module, but instead of making it work with redirects I propose to output all the links with the correct URL (the URL after redirect). So instead of output the URL like /es/node/77 and then do the redirect to /alias, I propose to directly output the link as /alias
For this we need to create a service with the tag path_processor_outbound with priority higher than path_alias.path_processor service and add all needed functionality into that service.

Please let me know if you think that is a good solution, if so then I will proceed with a new ticket and the patch for this.

I have inherited this project. I just published an alpha release. My contribution for the moment is to review community patches and move them forward and cut releases as needed.

I have done a very small amount of work so far which was to add Drupal 10 to the .info.yml file and I cut an alpha release.

Note: I have a more popular module called moderated_content_bulk_publish which does something similar but uses an on403 , this module could easily be refactored to use an on404. The on404 event might make more sense, with that said, I haven't planned refactoring just was looking at the current design.