[WIP] Fix Claude Code Review badge status in README.md

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

Open a pull request in kimocoder/wifite2 to fix the Claude Code Review badge status in README.md.

Repository

• kimocoder/wifite2
• Base branch: master

Problem

The README currently includes this badge markdown near the top:

[![Claude Code Review](https://github.com/kimocoder/wifite2/actions/workflows/claude-code-review.yml/badge.svg?branch=master&event=status)](https://github.com/kimocoder/wifite2/actions/workflows/claude-code-review.yml)

The workflow file .github/workflows/claude-code-review.yml is named Claude Code Review and is triggered on:

on:
  pull_request:
    types: [opened, synchronize, ready_for_review, reopened]

Because the badge URL uses event=status, the badge status appears incorrect/misleading for this workflow.

Requested change

Make the smallest safe fix to the README badge so it correctly reflects the workflow status.

Requirements

1. Update the Claude Code Review badge in README.md.
2. Prefer the smallest possible change.
3. Preserve the existing badge link target to the workflow page unless there is a strong reason to change it.
4. Do not make unrelated README edits.

Suggested approach

Use a badge URL that matches the workflow correctly. A minimal safe fix is to remove the mismatched event=status query parameter from the badge URL. If there is a clearly better, correct GitHub badge URL for this workflow, use it.

Deliverable

Open a PR that fixes the Claude Code Review badge status in README.md.

The following is the prior conversation context from the user's chat exploration (may be truncated):

User: Retry

Assistant: I’m the GitHub Copilot Chat Assistant. I can help you plan the config refactor and even make the changes, but to actually “fix config refactoring” I need one clarification:

1. Do you want me to open a Pull Request in kimocoder/wifite2, or do you want step-by-step instructions / a patch plan only?

If you want a PR, tell me:

• the base branch to target (e.g. master)
• whether you want a minimal safe refactor (internal re-org, no behavior changes) or a full refactor (move settings into structured config objects and update callers)

What I recommend (minimal safe refactor, lowest risk)

Because Configuration is imported all over (from ..config import Configuration) and used as a big global, the safest “refactor” is staged:

Stage A (no breaking imports):

• Create a new package: wifite/config/
  • defaults.py (all default values)
  • validators.py (validate + helper validation like _validate_interface_name)
  • parsers/ (split parse_*_args into files: settings.py, wep.py, wpa.py, wps.py, pmkid.py, eviltwin.py, dual.py, monitor.py, wpasec.py)
  • manufacturers.py (OUI lazy load)
• Keep wifite/config.py but shrink it to:
  • the Configuration class (as the public API)
  • delegating calls into the new modules
• Result: no other file needs changing, but config.py becomes maintainable.

Stage B (optional, later):

• Introduce dataclasses like Configuration.wps, Configuration.wpa, etc.
• Update call sites incrementally.

One important limitation

My earlier code-search results are not exhaustive (the search tool only returns a limited set), so before doing a PR I’d do a repo-wide sweep for Configuration. usage and from ..config import Configuration imports to avoid missing edges. You can also browse all matches in GitHub UI search here:

https://github.com/kimocoder/wifite2/search?q=Configuration.&type=code

Reply with:

• “Open a PR” or “Plan only”
• base branch (likely master)
• minimal vs full refactor

…and I’ll proceed accordingly.

User: Open a PR

Assistant: I’ve started the PR creation process and we

Assistant: I've started working on the refactor of the monolithic Configuration module in the kimocoder/wifite2 repository. You can follow the progress and view updates directly on the Pull Request once it's opened. I'll notify you when it's completed!

User: Find all TODO comments and list then up here

Assistant: I found these TODO comments in kimocoder/wifite2. Note: the code search tool returns a limited set of matches, so this list may be incomplete. You can browse all matches in GitHub here:

https://github.com/kimocoder/wifite2/search?q=TODO&type=code

TODOs found

• docs/TODO.md

  • This entire file is a TODO/roadmap document with many planned improvements.

• docs/EVILTWIN.md

  • Go through Fluxion to know hostnames/paths and expected responses for Apple & Google devices.
  • Can we use macchanger to detect vendor, or have some mapping of BSSID_REGEX -> HTML_FILE?
  • The exact commands to verify WiFi passwords in Linux; likely wpa_supplicant or similar.
  • Choose the fastest & most reliable method for verifying WiFi passwords.
  • See if CGIHTTPServer can maintain/alter background threads.
  • See how hard it would be to maintai...

This pull request was created from Copilot chat.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Copilot]

Pull request overview

This PR fixes the GitHub Actions badge for the Claude Code Review workflow in README.md so it correctly reflects the workflow’s status given its pull_request trigger.

Changes:

• Removes the mismatched event=status query parameter from the Claude Code Review badge URL.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.