Personalized open-source roadmap

Your OSS Battle Plan

Mapped from 150+ repositories across @pya-h and @pydea-rs — every suggestion below is hand-matched to what you actually build: security tooling, prediction markets & crypto, proxy/networking stacks, language internals, games and CLI tools. Four tiers — from starter-sized first PRs you can ship this week to pro-level arenas — across C/C++, Rust, Go, Python and TypeScript (frameworks included: NestJS, Next.js, Hono, Node…). Repos flagged with hit one of your personal obsession domains head-on.

0
Repos analyzed
0
Curated matches
0
Languages
0
Obsession domains
0
★ Fascination matches
// 01 — Your developer DNA

What your Git history says you love

Six clear patterns emerged from your two accounts. The contribution matches are scored against these — the ★-flagged repos let you contribute inside a domain you already can't stop building in.

🔐

Security & Exploitation

You read Art of Exploitation and Black Hat Go and actually wrote the code — scanners, steganography, pranks that hijack cursors.

art-of-exploitation-tryoutsmyBlackhatGoBookPracticesPortScannerhide-n-seedCursor-Prank
🔮

Prediction Markets & Crypto

Your deepest, most persistent rabbit hole: Gnosis-CTF markets, Polymarket scraping, trading bots on Pyth oracles, chain explorers — even market-resolution math.

AskAroundPredictionMarketScratchBinaryMarketdekant-trader-botspolyscraperdekantpmsolexplorerevm-explorerpyth-pal
🌐

Networking & Proxy Stacks

Xray/V2Ray tooling, FTP-over-websocket, server-client experiments, bots that talk to everything. You clearly enjoy packets.

FiViv2finderftpserver_by_websocketRemoteVectorTinTinChaturl-poker
🧠

Language Internals & Data Structures

Crafting Interpreters, dynamic-variable systems in Rust, hand-rolled trees/lists/sets, even assembly calculators — you like knowing what's under the abstraction.

lox-plusVaXC-SearchTreesmy-link-list.hgosetAssemblyCalculators
🎮

Games & Playful Software

Chess×backgammon hybrids, 3D tic-tac-toe leagues, minesweepers, snake, game AI opponents. You build games for the joy of it.

Shatnardt3dMineSweeperGameDotsAndLinesMySnakesMyMonkeyShooter
🛠️

CLI & Developer Tooling

File-combination searchers, batch renamers, npm auto-updaters, shell utilities — you automate your own workflow constantly.

anyshapenpm-packupbatchrenameUseful-Scriptsbyteculatorgofr3eky
★ Obsession matches only
// 02 — The matches

repos, ranked to your curve

● Starter = this week, no deep codebase knowledge needed — small but real · ● Medium = jump in this month · ● Advanced = after a few merged PRs · ● Pro = long-game, career-defining arenas. Expand any card for what the project is actively working on and exactly how to break in.

No matches for that filter — loosen it a bit. 🕳️
// 03 — Execution order

How to actually run this

Not all at once. One lane at a time, in this order.

PHASE 01 · WEEKS 1–6

Strike where you're already strong

Warm up in the Starter tier — a nuclei template (pure YAML), an HTTPie fix, a freeCodeCamp first-timers task, a NestJS docs page — to learn the PR workflow risk-free. Then open with ProjectDiscovery (naabu/nuclei — you've literally built a Go port scanner), file your first Rust PRs at clap and rust-clippy, and look at Polymarket's Rust clients — small, active, and squarely in your domain.

PHASE 02 · MONTHS 2–4

Convert obsessions into reputation

Move up to Foundry (your Solidity background is rare among Rust devs — huge edge), Xray-core / sing-box (your FiVi & v2finder work is their exact problem space), and Axum / Yew / Bevy to make your Rust production-grade. Add a web track — Hono / viem / NestJS if TypeScript pays your bills, or Textual / python-telegram-bot in Python. Target: 2–3 merged PRs per project, then get known in one community's chat.

PHASE 03 · MONTH 4+

Enter the pro arenas

With a trail of merged PRs, aim at reth or go-ethereum (the Rust×EVM combo is your most monetizable niche), LLVM, rust-analyzer, CPython or the TypeScript compiler (your Crafting-Interpreters endgame — pick one), and Kubernetes / Cilium / Node.js if you want the cloud-native career door. One meaningful PR here outweighs twenty small ones elsewhere.

Field notes that save you pain

  • One project at a time. Maintainers trust repeat contributors; ten drive-by PRs build less reputation than three in one repo.
  • Read the CONTRIBUTING guide first — they differ. Foundry, for example, rejects typo-only doc PRs and requires disclosing AI assistance in your PR. Breaking local norms gets you ignored.
  • Comment before you code. Claim the issue ("I'm working on this") so effort isn't duplicated and maintainers know you exist.
  • Small, focused, green CI. Run the project's formatter and linter before pushing (cargo fmt / cargo clippy / gofmt). Review latency is the #1 killer of first PRs.
  • Don't skip the Starter tier. A merged YAML template or docs fix this week beats a heroic PR you never finish. Momentum compounds.
  • Templates & docs are real contributions. nuclei-templates, Xray's docs site, clap's examples — these merge fast and get your name in the contributor list while you learn the codebase.