Add pyobfus to Distribution / Obfuscation

[zhurong2020]

Adds pyobfus as a challenger entry under Distribution → Obfuscation (currently one entry, pyarmor; cap not reached, so no displacement argument is needed).

Quality requirements

• Serves Python developers: obfuscates Python source before delivery; CLI + library + MCP server.
• Active: latest release 0.5.28 on 2026-09-20; commits weekly.
• Stable: Development Status :: 5 - Production/Stable on PyPI; Python 3.9–3.14 tested in CI on Ubuntu/macOS/Windows.
• Documented: README with examples, docs site https://pyobfus.readthedocs.io, framework cookbooks.
• Established: repository created 2025-11 (>1 month).

Why a second entry in this use case
pyarmor protects bytecode; pyobfus takes the other design point — pure-AST, source-level, and it ships a reverse-mapping workflow (pyobfus --unmap) so an obfuscated production traceback can still be debugged by the maintainer or an AI assistant. It also has framework-aware presets (FastAPI/Django/Flask/Pydantic/Click/SQLAlchemy/ML) and a --check pre-flight scan with SARIF output. It is the only obfuscator in this use case with an MCP server and a VS Code extension.

Adoption evidence (honest)
PyPI about 2k downloads/month (pypistats, without mirrors), OpenSSF Best Practices passing badge (project 12788), PEP 740 attestations on every release. This is small next to pyarmor (about 290k/month); I am submitting as a challenger, not an obvious choice.

Disclosure: I maintain pyobfus.

Checked: not previously listed, no prior PR/issue for pyobfus found in this repo.

[JinyangWang27]

@zhurong2020 Thanks for the thorough and transparent write-up. A Challenger slot needs adoption-trajectory evidence, and pyobfus is at ~6k downloads/month versus ~313k for pyarmor. Happy to revisit as adoption grows. See CONTRIBUTING