Skip to content

Security Policy

Alex edited this page Jan 18, 2025 · 4 revisions

Security Policy

I'm a solo developer, and this is not a legal document.
I just want to provide a bit of transparency to users.

Using third-party scripts means you trust that the script’s developer hasn’t inserted malicious functionality into the code and has secured it against attackers trying to do the same. You should never run code you don't trust.

What I'm doing to ensure this is safe for users:

  1. This is an open-source project, it can be audited by anyone.
  2. It is officially distributed via GitHub Releases, allowing for independent auditing and review.
    • You can see all previous versions and their changelogs.
    • I cannot edit or remove reviews or comments on the repository.
  3. Bypasser will NOT use external dependencies or dynamically download scripts or make external requests.
    It will only interact with the necessary elements of the target website for the core functionality.
  4. Bypasser will NEVER collect or transmit any personal data.
  5. No code obfuscation.
  6. Inform users of the potential risks involved.
  7. I will make sure I have good security habits regarding this GitHub account.
  8. Lastly, I @falpearx will never accept or add malicious commits into THIS repository.
    (Be aware I have no control over forks from other users)

That said, you still have the final responsibility of what you run on your computer. I am not responsible for any issues that may arise from using this software. Disclaimer

Note about Forks

This project is open-source, which means that anyone can make copies of this project (called forks), and make their own changes.
While I have full control over what goes into this repository, I DON'T have any control over forks of this project.

That means the terms above ONLY apply if you're using the original key bypasser.

  • When using a fork, make sure to check their code, and only use it if you trust the author of that copy/fork.
Clone this wiki locally