Skip to content

Conversation

@dvershinin
Copy link

@dvershinin dvershinin commented Jan 11, 2026

This PR replaces the MegaManSec/Gixy-Next entry with dvershinin/gixy, which is the more actively maintained fork.

dvershinin/gixy (published as gixy-ng on PyPI) offers:

  • Python 3.6-3.13 support
  • Additional security checks beyond the original
  • Regular updates and releases
  • Modern dependency support

Official website: https://gixy.org
Documentation: https://gixy.getpagespeed.com

The original yandex/gixy reference is preserved for historical context.

dvershinin/gixy (gixy-ng on PyPI) is the more actively maintained fork with:
- Python 3.6-3.13 support
- Additional security checks
- Regular updates and releases

Official website: https://gixy.org
@dvershinin dvershinin changed the title Update gixy repository link to actively maintained fork Replace Gixy-Next with dvershinin/gixy as the actively maintained fork Jan 11, 2026
@MegaManSec
Copy link
Contributor

MegaManSec commented Jan 11, 2026

Please consider https://joshua.hu/gixy-ng-new-version-gixy-updated-checks#quality-degradation and https://joshua.hu/gixy-ng-ai-slop-gixy-next-maintained before making this change. Gixy-Next (https://gixy.io / https://github.com/megamansec/gixy-next) was deliberately created due to the low quality, broken code that was automatically contributed to in gixy-ng, as well as the advertising that was added in gixy-ng.

Thank you.

@bad-antics
Copy link

Solid work! The formatting looks clean and consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants