Thank you for the feedback!

That is indeed an interesting feature, but like you said it could come with certain risks... However, as the implementation follows the single-responsability principle (each classmethod is responsible for getting a certain entity's data and nothing else), it wouldn't be difficult to add checkboxes on the extension's pop-up and query only chosen resources.

This wouldn't allow for custom entities per se, but it would allow for the addition of many other entities to the API without diminishing performance or cluttering the report for people who only care about a few of them. I'll definitively add this to my to-do!

And just a reminder, this project is 100% open source, so anyone is welcome to fork it and add custom resources to fit more specific needs like quering custom tables and such :)