Maintained repositories
Places to make your first commit
43 issues labelled good-first-issue across 6 repositories, all carrying the Hacktoberfest topic. Comment to claim one — one at a time, so everyone gets a turn.
recon-oss
CLI that maps a repository's dependency and ownership graph, then flags unmaintained paths.
TypeScriptNodeCLI
18 open7 good first issues →
syncit
Self-hostable file sync daemon with conflict-free replicated state. Rust core, TS control plane.
RustTypeScriptgRPC
24 open9 good first issues →
sage-ops-site
This website. Good first PRs: accessibility fixes, new components, leaderboard data adapters.
Next.jsTailwindTypeScript
11 open6 good first issues →
kernel-notes
Annotated walkthroughs of Linux subsystems for students starting systems programming.
CMarkdownDocs
9 open5 good first issues →
prquality
GitHub Action that scores PR hygiene — description, tests, scope — and comments a checklist.
TypeScriptGitHub Actions
14 open4 good first issues →
dsa-visualiser
Step-through visualiser for classic algorithms. Beginner-friendly React issues, lots of them.
ReactCanvasTypeScript
21 open12 good first issues →
Before you open a pull request
- Claim the issue first. Comment on it and wait for the 'assigned' reply — duplicate work helps nobody.
- One issue, one branch, one pull request. A PR that touches four unrelated things gets sent back.
- Run the tests locally before pushing. If there are no tests for what you changed, add the smallest one that would fail without your fix.
- Write the description like the reviewer has never seen the issue: what broke, what you changed, how you checked.
- Reformatting a file, fixing a typo in a comment, or adding whitespace is not a contribution. Those get closed.