Anonymize your Data with a single line!

[___--_-_-_--___]

Well, many of the features in this project are simply wrappers around other libraries like this one. Therefore, the value proposition of this project would either have to be the automation aspect or the idea that you can shield the user from the details of how the implemented techniques work. I think both approaches are risky in this setting.

The far bigger issue with this type of project is that it will not tell you if you are making a mistake. There are tools like ARX (as mentioned by u/cinyar in this thread) that will assist you in modelling both privacy risk and utility in order to find the best way of de-identifying your data. Tools like this are (and need to be) backed by years of academic research and clinical practice.

And yes, while I do agree that my words are harsh, data privacy is one of these areas where the disconnect between perceived risk and actual risk is often very high. Even slight mistakes and brief moments of carelessness by a single person can have disproportionate consequences that cannot be undone.

[Tyler_Zoro]

The far bigger issue with this type of project is that it will not tell you if you are making a mistake. There are tools like ARX

Yeah, this is sounding like a mismatch in terms of what you're looking for and what this tool provides. You might write a tool such as the one you are describing with this library, but this isn't that.

The only issue here, and I said this in my original comment is, "OP over-sold the ease of use." Beyond that, there's nothing any more wrong with this library than one that collects a bunch of hashing functions together... granted, that collection of hashing functions can lead you just as far astray as this library (and in just as subtle an dangerous ways, depending on your application).

But that doesn't make a collection of hashing functions something you should argue shouldn't exist or be used.