Not sure Django and Flask are real competitors. Both are excellent and mature Python web frameworks but they vastly differ in scope.
Django has tools like Ninja and DRF that let's you use Django in much the same way you would Flask, while still being comparable with the rest of the Django ecosystem.
The difference isn't so much one of actual scope, but rather that Django is still perceived as much heavier and more complicated than Flask to get started with.
I would also say that could account for the download count differences between the projects. Django may still be used for more monolithic applications whereas Flask and FastAPI may be the choices for smaller-scoped microservices resulting in 10x downloads.
No negative connotation is intended here for "monolithic". On the contrary, if the above assumption is at all true, it highlights a overhead cost of individual microservices.
I ported an app from CherryPy to Quart and am very happy with my decision so far.
I'm hoping Flask and Quart have a long future ahead, it doesn't seem like there's anything to add or take away that a plugin can't handle.