@zie1ony / OP - how do you make your clients believe you are not planting a crypto-locker or logic bomb or some other 3-letters-agencies "features"? And why would clients replace existing AI slop with your post-another-slop handwritten code? Do you check it for vulns and, most important, have you considered that later clients will sue you for <something their checkbox audit did not like>? Providing there is no major data leak, in which case you may end up proving your innocence from behind bars?
I remember implementing very complex cryptographic scheme in pure C. After a week of hard work, my friend concluded: "Cryptography would be much easier if people just trust each other."
The truth is that it is my reputation on the line, so I also have to make sure dependencies I use don't mess up things as well. There is no good defense against it. In my contracts I undertake to act in a good faith and take the responibilites to the amount of my professional insurance. Honestly, it is different casy by case.
