Contribute
67,000 lines of Swift. One maintainer. You see the problem.
G-Rump is MIT-licensed, built in the open, and honest about being early. That makes it a genuinely good project to contribute to: the rough edges are documented, the issues are labeled, and PRs get read by the person who wrote the code they touch.
Build it in four commands
git clone github.com/Aphrodine-wq/G-Rump.git cd G-Rump make run # debug build + launch swift test --parallel # the suite — 1,500+ tests, run before you PR
macOS 14+ and Swift 5.9+. There’s one SwiftData/SPM gotcha worth reading about first — CONTRIBUTING.md covers it, plus the hard rules (no print(), SwiftLint strict).
Good first issues
Scoped, labeled, and real — filtering Ollama's paywalled models, an accessibility pass on the new mode card, docs audits. Each one says exactly where to look.
Browse good first issues →Break it, then tell us
The fastest way to help: use it on your real project and file what goes wrong. Build-and-run edge cases and chat rough spots are exactly what the roadmap's 'rough' column needs.
File a bug →The big one: GRumpKit
Extracting the harness into a SwiftPM library is the top roadmap item, and the boundary design is happening in the open. If you want your name on the foundation, start there.
Join the design discussion →No Swift required
Verifying MCP presets still work, docs fixes, and comparison-page corrections are all real contributions. Help wanted is labeled.
Browse help wanted →Questions before you start? Use GitHub Discussions. Security reports go through the security page, not public issues.