Add wildlint to Linters (General)

[patchwright]

Adds wildlint under Linters → General, beside flake8-bugbear (same niche: bug classes the base linters miss).

wildlint is a precision linter for bug classes off-the-shelf linters (ruff/flake8/pylint) don't cover — the kind that look like ordinary, working code:

• dead argparse flags (option defined but its dest is never read)
• str.replace(prefix, "") meant as removeprefix/removesuffix
• deep negative indexing s[-k] → IndexError
• humanizer rounding rollover (millify(999999) → '1000k')

Each rule is distilled from a real upstream fix (provenance-pinned), so the default tier is near-silent on mature, heavily-linted codebases (django/click/flask) by design — it's a low-false-positive tool, not a high-recall scanner. Cross-language: Python, JS, TS, Go, Rust (via ast-grep).

• Repo: https://github.com/patchwright/wildlint
• PyPI: https://pypi.org/project/wildlint/ (0.8.2)
• License: MIT
• pre-commit hook available

Happy to move it to a different section if there's a better fit. Thanks for curating this list.

[fjsj]

thanks, tool looks nice, but as this is a relatively new tool, could you please give more details?

• are you the sole maintainer?
• I've seen you made some contributions to other projects, but is it actively used on commercial projects or large-ish free/open-source ones?
• any human professional dev behind this? feel free to contact me on LinkedIn: https://www.linkedin.com/in/flaviojuvenal
• do you plan to keep maintaining this tool?

sorry for this verification, it's also for security.

[patchwright]

Fair questions, thanks for asking rather than just closing it.

• Yes, I'm the sole maintainer — this is an independent project, no company or team behind it.
• No large-scale commercial adoption yet. It's been shipped as fixes into other open-source projects though — happy to point at a few: caesar0301/treelib#246, remarshal-project/remarshal#69 — real merged PRs where wildlint caught the bug being fixed. That's the track record so far, not enterprise usage.
• No LinkedIn to share right now, sorry — happy to keep this conversation on GitHub instead. If it'd help, I can add more background to the project's README or my profile.
• Yes, I intend to keep maintaining it — it's actively developed (see the commit history / CHANGELOG), and I use it myself as part of an ongoing gift-PR effort to other projects.

No hard feelings if this doesn't clear your bar for the list — happy to leave it as-is or close it, your call.

[fjsj]

I will leave it open and merge once you get larger adoption or I can really verify a human team behind this. Thanks!