I want to contribute to open-source projects that are popular, actively maintained, and used by real people. However, I keep finding repositories with little activity, very few stars or forks, or issues that appear abandoned. I also tried using a "good first issue" directory, but many of the listed projects seem inactive. What are better ways to discover worthwhile projects and find contributions that match my skills in Node.js, React, Next.js, TypeScript, Solidity, and Rust?
4 Answers
Directories for beginner-friendly issues can be useful, but they are often outdated. Before investing time, check the commit history, recent releases, issue and pull-request activity, and whether maintainers respond to contributors. Search directly through code-hosting platforms using your languages and topics, then filter for recently updated repositories. Also read the contribution guide and start with documentation, tests, bug fixes, or small improvements rather than waiting for an issue labeled as beginner-friendly.
Popularity is not the only useful measure. A smaller project with active maintainers may offer better feedback and a clearer path to getting a contribution accepted. Since you work with JavaScript, TypeScript, React, Next.js, Solidity, and Rust, look for active projects in areas you already care about, install them locally, run the tests, and inspect open issues. If no issue is suitable, first report a specific problem or propose a small improvement rather than submitting an unrelated change.
The best issues are often ones you discover through normal use. Use a project regularly, watch for bugs, confusing documentation, missing features, or awkward workflows, and then check whether an issue already exists. This is usually more productive than searching for a repository solely because it has a high star count.
A good way to find projects is to start with software you personally use. Look for the main project, related tools, or open-source alternatives. That gives you enough familiarity with the domain to understand bugs and suggest useful improvements. A repository can be popular and active, but that does not automatically mean you will be able to contribute effectively if you do not understand what the software does.
That makes sense. I have been trying to focus more on tools and hobbies I already understand instead of choosing projects based only on popularity.
I have started doing that, although I was hoping there was also a reliable way to search for active projects by language and issue type.