Security

Here, I’ll share how I approach security and what I do to keep my tools safe and reliable for you.

I don’t store or see your data in any way—your information stays yours, always.

Most of what I build is in Python, and security is a top priority for me. I use pip-audit and Snyk to catch third-party vulnerabilities and make sure my dependencies are safe. I also rely on Snyk for secure coding, helping me spot and fix issues early. My approach is guided by OWASP standards, so security is built in from the start. Whenever possible, I stick to vendors' open APIs and SDKs, keeping things straightforward and secure by going straight to the source.

I don’t run any infrastructure—everything runs locally and communicates directly with the vendor’s API endpoints. There’s no man-in-the-middle (MITM) or C2 here!

As an additional security measure, all binaries are hashed immediately upon release. Users are strongly advised to verify that the SHA256 checksum matches before executing any files.

The software is provided 'as is,' without any express or implied warranties, including but not limited to warranties of merchantability or fitness for a particular purpose. The author assumes no liability for any damages, losses, or other consequences arising from the use or misuse of these software.