Until you implement this, can you please add a big red flashy warning on top of the plugin settings page? I am requesting this in hopes that it will save someone else from a lot of frustration, headache and wasted time.
I left the plugin running for a week on a production website to debug an issue. We have 3 external integrations with logistics companies and apparently one of them did some pretty expensive API calls regularly. This was a good thing to find out, so in that sense, the plugin served its purpose. However, thanks to the plugin storing LOG ENTRIES in the MAIN WP POSTS TABLE (!!!!), our wp_posts table went from 17mb to 5GB, took down a production server, took our team half a day to clean up and resulted in a non-trivial financial loss for our client.
Lesson learned: audit *every* plugin thoroughly before installing. I usually get a pretty good initial sense of the code quality by just looking at the settings page, file names and structure – and everything looked good in this case. So I am still somewhat reluctant to take the blame here, because the idea of storing log entries in wp_posts is just so utterly absurd that it never would have crossed my mind.
Please add a warning.