1) It would be clearer what this was if you linked to the SaaS page rather than the client libraries on Github. Or even put in the readme that these are just client libraries for the SaaS app.
2) For the Django code, if you converted that to generic wsgi middleware, it would work with most Python frameworks. If you also created asgi middleware, it would also work with the newer async frameworks (including DJango 3.1). You could also keep the framework specific middleware for ease of integration for those who want, but the generic middleware would be a basic framework agnostic option.
1) It would be clearer what this was if you linked to the SaaS page rather than the client libraries on Github. Or even put in the readme that these are just client libraries for the SaaS app.
2) For the Django code, if you converted that to generic wsgi middleware, it would work with most Python frameworks. If you also created asgi middleware, it would also work with the newer async frameworks (including DJango 3.1). You could also keep the framework specific middleware for ease of integration for those who want, but the generic middleware would be a basic framework agnostic option.