Want to help? Read this before you start

Hi, and thanks for thinking about contributing

Maigret gets a lot of people who want to help, and I want to make sure your time actually turns into merged code. There are two different situations, so pick the one that matches you.

1. You want to work on Maigret itself

Great — go ahead. Browse the open issues, pick one, and say in the comments that you're taking it so two people don't do the same work. If you want to add or fix a site check, that's the most useful thing you can do here, and the data lives in maigret/resources/data.json.

2. You just want to help with open source, and you're flexible

Then I'd rather point you somewhere your first PR lands faster.

I maintain several smaller tools, and they get a fraction of the attention Maigret does — not because they matter less, but because this repo absorbs it all. Two of them have real, ready work right now.

socid-extractor — pulls account data out of 130+ sites: usernames, bios, avatars, and the internal IDs that survive renames. It's the library Maigret itself uses, so you'd be working one layer down from here.

• Schemes to write — mostly forum engines (Flarum, phpBB, NodeBB, Lemmy, vBulletin)

Writing a scheme is a good first contribution: it's self-contained, there's an existing scheme to copy the shape from, and you don't need to make any design decisions. Engine schemes are also the best value for your time — one scheme for phpBB covers 155 sites at once, not one.

telegram-bot-dumper — pulls the full chat history of a Telegram bot from Telegram's servers and renders it like Telegram Web. Useful in pentest, recon and malware analysis.

• Good first issues — small, about an hour each
• Help wanted — CLI and web viewer features

Every issue in both repos tells you what's in scope, what's out, how you'll know it's done, which file to look at, and the exact commands to run and test it. You won't need credentials to verify your work — the tests run against saved fixtures, not live requests.

I'll add more repos here as I prepare proper issues for them. I'd rather list two repos with tasks that are genuinely ready than five with empty trackers.

What to expect from me

I review PRs myself. I'm not always fast, but I do answer. If something is unclear in an issue, ask in the issue — a question there helps the next person too.

If you open a PR, please keep it to the scope of the issue. Big unrequested rewrites are the main reason a PR sits unmerged.

Thanks