Looking for Contributors: Good First Issues in Network Doctor

Looking for Contributors

I've been working on Network Doctor, an open-source Go TUI for diagnosing network problems, and I'd like to get more people involved in the project. I currently have a few issues ready for contributors.

I've been working on Network Doctor, an open-source Go TUI for diagnosing network problems, and I'd like to get more people involved in the project. I currently have a few issues ready for contributors.

Good First Issues

• #110 - Make the causal-evidence golden mutation test non‑vacuous A small, test‑focused issue. No production behavior changes are needed. https://github.com/heymaikol/network-doctor/issues/110
• #111 - Add hermetic tests for macOS and Windows SSID command wrappers A slightly larger testing task involving the existing platform‑specific SSID code. https://github.com/heymaikol/network-doctor/issues/111
• #97 - Bound hunt shard inputs before netdoc‑sim merge decodes them This one involves input‑size enforcement and is better suited to someone already comfortable with Go. https://github.com/heymaikol/network-doctor/issues/97

Field Validation Issues

There are also several field‑validation issues for contributors who have access to environments I can’t easily reproduce, including macOS, IPv6‑only networks, VPN split DNS, captive portals, and managed proxy networks.

Project & Setup

Network Doctor is here: https://github.com/heymaikol/network-doctor

The contributor setup is intentionally simple:

• git clone https://github.com/heymaikol/network-doctor.git
• cd network-doctor
• go test ./...
• go run . github.com

If you're new to open source, that's completely fine. The good first issues are scoped so you shouldn't need to understand the entire project before getting started. Questions are welcome too.

Comments

Top comments (0)