This solution only covers one out of many options for the @Component annotation replacements.
you have @Service covered, but not for example @Controller, or user defined meta annotations that have @Component included.

Try creating a check that walks the meta-annotation tree instead of something that only checks the top level annotation.
Take a look at RepeatableAnnotations for how this is possible, that class handles meta-annotations for the @Mapping and @SubclassMapping annotations.

Thank you very much for the feedback @Zegveld.

I absolutely agree with you: I initially thought of including checks for @Repository and @Controller, but they seem like a less obvious use case to me. But you are completely right, the way to go should be traversing the different annotation tree looking for the occurrence of @Component within it, directly or through the annotation hierarchy. I will review RepeatableAnnotations as you suggested looking for reference.

Again, thank you very much for the feedback, and sorry for this first baby step.

@Zegveld Sorry for the late reply.

I have pushed some new changes.

Per your suggestion, I tried to process the Mapper instance by checking for the existence of the @Component annotation through the entire annotation hierarchy.

Please let me know what additional work needs to be done.

Thank you very much.

Thank you very much for the code review @filiphr, I appreciate it a lot.

I updated the code with the changes you requested.

Please let me know if any additional changes need to be made.

Thanks a lot for your patience @jccampanero. We've integrated this into main.

Thank you very much @filiphr. Please, on the contrary, thank you very much for your time and for allowing me to contribute to this wonderful library.