Zerobypass
Proof of concept tool to bypass document replay technology (such as GPTZero). Uses Playwright automation to simulate human typing behavior.
Requirements
- Python 3.11 or newer
- Display and clipboard access.
[!CAUTION]
Disclaimer - Research and Testing Only
This project and its contents are provided strictly for research and testing purposes. They are not intended for educational use, including but not limited to classroom assignments, coursework, exams, tutorials, or any form of formal instruction or certification.
Do not use, submit, distribute, or present this code or its outputs as part of academic work or educational materials without explicit permission from the project maintainers and any affected parties. The authors and maintainers make no representations or warranties regarding suitability for educational use.
Use of this project is at your own risk. The authors and contributors accept no liability for any damages, legal consequences, or disciplinary actions that may arise from misuse, including presenting this work in an academic context where it is not allowed.
If you require a version of this project for legitimate educational purposes, please contact the devs.
Installation
Install using pipx (recommended)
pipx install zerobypass
Install using uv
uv tool install zerobypass
Install using pip (not recommended)
pip install zerobypass #--break-system-packages
Install from source
git clone https://github.com/ZyluxXD/zerobypass.git`
cd zerobypass
Quick Start
Run:
zerobypass
or
python -m zerobypass
Arguments
browser-data-dir
Specifies a custom browser profile directory.
⚠️ Warning:
Do not point this to an existing personal browser profile. Doing so may corrupt your data.
Always use a cloned directory or a backup.
Notes
- This is still a Work In Progress and is not finished.
- The Playwright user data directory lives at:
~/.zerobypass. Delete it to reset the profile. - Rich text formatting is not yet supported — contributions welcome!
Contributing
- Feel free to make pull requests to contribute! There are various TODO's scattered throughout the project, and it would be great to help with those!
Metadata
Release files for zerobypass 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| zerobypass-1.0.3.tar.gz | 21.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| zerobypass-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 44.8 kB
Release files / zerobypass-1.0.3.tar.gz
| Download URL | zerobypass-1.0.3.tar.gz |
|---|---|
| Size | 21.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3a143cb35b3b7b8f0eb6dbe3b21ecfc2b212fa9a75fd1dfb3298b540e44eee7a
|
|
BLAKE2b-256 checksum How to use checksums |
6d143525a48f2a888410b12e0ec0cf1c41cbde50875e7cdbf80c0c8132a45318
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency logRelease files / zerobypass-1.0.3-py3-none-any.whl
| Download URL | zerobypass-1.0.3-py3-none-any.whl |
|---|---|
| Size | 23.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e3b343ee35ddcad6e9d60ee402c4160b8bdb49f15199bd94dfd6f1937be75cf
|
|
BLAKE2b-256 checksum How to use checksums |
bdcbaef098e5886e0625449c49aa3f55f221275bdea61cd1513a8e099acaf4fe
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Feb 16, 2026.
Transparency log