Rising Stars of Open Source: Projects to Contribute to Now

18 August 2026

Open source software has always been about more than just free code. It is a proving ground for ideas, a portfolio builder for developers, and a collective effort to solve problems that no single company wants to own. But with millions of repositories on GitHub alone, finding the right project to contribute to can feel overwhelming. The usual advice points to Kubernetes, React, or TensorFlow, but those projects are massive, heavily governed, and often intimidating for newcomers. The real opportunity lies in the rising stars: projects with growing momentum, clear roadmaps, and maintainers who genuinely welcome outside help.

This article is not a list of random popular repos. It is a curated look at projects that are technically interesting, have a healthy contribution culture, and are at a stage where your work can actually matter. I have spent years contributing to and maintaining open source projects, and I know the difference between a project that absorbs your pull request and never speaks to you again, and one where your commit leads to a maintainer role. The projects below fall into the latter category for the most part, and I will explain exactly why they are worth your time.

What Makes a Project a Rising Star

Before diving into specific projects, it helps to understand the criteria. A rising star is not just a repo with a lot of stars. It is a project that is gaining traction in real usage, has an active core team, and has a contribution process that does not require you to be a genius to get started. Look for these signals:

- Recent release cadence: A project that ships new versions every few weeks is alive. A project with a single release from two years ago is a zombie, no matter how many stars it has.
- Responsive maintainers: Check the issue tracker. Are questions answered within days? Are pull requests reviewed with constructive feedback, or just merged blindly?
- Good first issue labels: This is a strong signal that the maintainers actually want new contributors. It means they have thought about onboarding.
- Clear documentation for contributors: A CONTRIBUTING.md file that is detailed and current. Not a copy-paste from another project.
- A community beyond GitHub: A Discord, Slack, or mailing list where people discuss the project. This is where you learn the unwritten rules.

The projects I will cover below all meet most of these criteria. They are not the biggest names in open source, but they are on the way up. And that is exactly where you want to be.

The Current Landscape: Why Smaller Projects Matter More Than Ever

The open source ecosystem has changed. Big projects like Linux or VS Code are no longer about individual contribution; they are about corporate sponsorship and full-time maintainers. If you are a hobbyist or a developer looking to build your skills, you will struggle to make a meaningful impact there. Your pull request might sit for months, and even if it is merged, you are one of thousands.

Smaller projects, on the other hand, offer something that big projects cannot: ownership. When you contribute to a project with a few hundred or few thousand users, your code is seen. Your name becomes known to the maintainers. You can influence the roadmap. And if you stick around, you can become a maintainer yourself. That is how many successful open source careers start.

But you have to be careful. Some small projects are small because they are dead. Others are small because they are new and solving a real problem. The trick is telling the difference. The projects below are alive, growing, and have a clear purpose.

Project One: Zed - A Fast, Collaborative Code Editor

Zed is a code editor that has been gaining serious momentum. It is built in Rust, which already gives it a performance edge over Electron-based editors like VS Code. But the real differentiator is its collaborative features. Multiple developers can work on the same file in real time, with low latency, without the jankiness of older remote pairing tools.

Why contribute to Zed? First, Rust is a language that many developers want to learn, and Zed's codebase is well-structured and modern. Second, the project is at a stage where the core architecture is stable, but there are many gaps in features and platform support. For example, the editor has solid support for macOS and Linux, but Windows support is still catching up. That is a huge opportunity for a contributor who knows Windows APIs or wants to learn them.

The maintainers are active on their Discord server, and they have a clear roadmap. They also have a "good first issue" label that is actually curated, not just a dumping ground. The main challenge is that the codebase is complex, and you need to be comfortable with Rust's ownership model and async programming. But if you are willing to invest time, you will learn more from this project than from any tutorial.

A practical starting point: look for issues related to theming, syntax highlighting for less common languages, or terminal integration. These are self-contained areas that do not require deep knowledge of the editor's core.

Project Two: Dolt - A SQL Database with Git-Like Versioning

Dolt is a fascinating project. It is a SQL database that you can branch, merge, and clone, just like a Git repository. Think of it as Git for data. This is not a toy; it is used by data teams to manage schema changes and data migrations in a versioned way. If you have ever dealt with a botched database migration, you know why this matters.

The project is written in Go, which is another language with high demand. The codebase is large, but it is well-organized. The team behind Dolt is a company called Dolthub, and they are actively hiring and encouraging community contributions. They have a dedicated section in their docs for contributors, and they even offer bounties for certain issues.

What makes Dolt a rising star is its potential to change how data teams work. The concept is simple but powerful, and the implementation is solid. As a contributor, you can work on SQL function implementations, performance optimizations, or the CLI tooling. The learning curve is moderate. You need to understand SQL and basic database concepts, but you do not need to be a database engineer.

One common mistake new contributors make is trying to fix a bug in the query planner without understanding the overall architecture. Start with something simpler, like adding a new SQL function or improving error messages. The maintainers are known for giving detailed feedback, which is invaluable for growth.

Project Three: PocketBase - A Backend as a Service in a Single File

PocketBase is an open source backend that provides authentication, a database, and file storage, all in a single executable file. It is aimed at developers who want to build a web app without setting up a separate backend server. It has gained a loyal following because it is incredibly easy to get started with, yet powerful enough for production use.

The project is written in Go, and its architecture is modular. You can extend it with custom hooks and JavaScript. This makes it an excellent project for contributors who are interested in backend development but do not want to deal with the complexity of a full cloud infrastructure.

Why is it a rising star? Because the demand for simple, self-hosted backends is growing. Many developers are tired of the cost and complexity of managed services. PocketBase offers an alternative, and its community is enthusiastic. The maintainer, Gani Georgiev, is very responsive and personally reviews most pull requests. That is rare for a project of this size.

A good starting point is the JavaScript SDK or the admin UI. Both are separate from the core engine and easier to understand. The core engine itself is also accessible if you are comfortable with Go. Just be prepared to write tests; the project has a high standard for test coverage, which is actually a great thing to learn from.

Project Four: NocoDB - A Smart Spreadsheet Alternative

NocoDB is often described as an open source Airtable alternative. It turns your database into a smart spreadsheet, allowing non-technical users to interact with data without writing SQL. Under the hood, it supports MySQL, PostgreSQL, SQL Server, and SQLite.

The project is built with Node.js and Vue.js on the frontend, and it has a large codebase. However, the contribution process is well-documented, and the community is active. The reason it is a rising star is the same as PocketBase: people want control over their data without paying enterprise prices.

For contributors, NocoDB offers a wide range of entry points. If you are a frontend developer, you can work on the spreadsheet UI, which is complex and interesting. If you are a backend developer, you can work on the API or the database connectors. The project has a strong emphasis on extensibility, so there are many plugin points.

One thing to watch out for: the project has grown quickly, and some parts of the codebase are less polished than others. Do not be discouraged if you find some legacy code. It is a perfect opportunity to refactor, and the maintainers appreciate that kind of contribution, as long as it is backed by tests.

Project Five: Meilisearch - A Lightning-Fast Search Engine

Meilisearch is a search engine that you can self-host. It is designed to be fast, relevant, and easy to use. Unlike Elasticsearch, which requires significant setup and tuning, Meilisearch works out of the box with a simple API. It is written in Rust and has a growing set of client libraries for various languages.

Why contribute? Search is a hard problem, and Meilisearch is tackling it with a modern approach. The codebase is clean, and the maintainers are very active on GitHub. They have a clear roadmap, and they encourage contributions to their SDKs, which are often simpler to work with than the core engine.

A common misconception is that you need to understand information retrieval theory to contribute. That is not true. Many contributions are about improving the developer experience, writing better error messages, or adding support for new languages in the SDKs. The core engine is more challenging, but the project has a mentorship program for contributors who want to go deeper.

If you are interested in performance optimization, this is a great project. The team regularly publishes benchmarks, and they are always looking for ways to reduce memory usage and latency. That kind of work is highly valued and will look great on your resume.

Project Six: Directus - A Real-Time Data Platform

Directus is another data platform, but it takes a different approach than NocoDB. It wraps an existing SQL database with a real-time API and an admin app. It is highly customizable and supports any SQL database. The project has been around for a while, but it has recently gained significant traction due to its move to a more open core model.

The codebase is TypeScript, both frontend and backend, which makes it accessible to a large pool of developers. The project is well-structured, with a strong focus on modularity. You can build custom extensions, and the documentation for extension development is excellent.

What makes Directus a rising star is its ecosystem. The core project is stable, but the extension marketplace is growing. If you build a useful extension, you can reach thousands of users. That is a powerful motivator.

For new contributors, the easiest entry point is the documentation or the extension examples. The core codebase is more complex, but the maintainers are helpful. They have a weekly community call where you can ask questions and get guidance. That kind of access is rare and valuable.

How to Choose the Right Project for You

The projects above are all good, but they are not all right for you. Choosing a project is like choosing a team to join. You need to match your skills, your interests, and your available time. Here is a practical framework to help you decide.

First, assess your current skill level. If you are new to open source, choose a project with a gentle learning curve, like Meilisearch SDKs or PocketBase extensions. If you are experienced, go for the core challenges in Zed or Dolt.

Second, think about what you want to get out of it. Are you looking to learn a new language? Zed will teach you Rust. Are you looking to build a portfolio for backend jobs? Dolt and PocketBase are better. Are you interested in frontend work? NocoDB and Directus are the way to go.

Third, check the community vibe. Join the Discord or Slack for a week before you write any code. See how people talk to each other. Is it welcoming? Do maintainers explain their reasoning? If the community is toxic, even the best project is not worth your time.

Fourth, start small. Do not try to solve a big architectural problem on your first contribution. Fix a typo in the docs, add a test, or improve an error message. This builds trust and helps you understand the contribution process.

Best Practices for Making Your First Contribution

Once you have chosen a project, how do you actually get started? The following practices apply to almost any project and will save you a lot of frustration.

Read the CONTRIBUTING file carefully. It will tell you how to set up your environment, how to run tests, and what the coding standards are. Follow it exactly, even if it seems tedious. Maintainers notice when you follow their process.

Find a "good first issue" and comment on it before you start. Say that you are interested and ask any clarifying questions you have. This does two things: it confirms the issue is still relevant, and it gives you a direct line to the maintainer who will review your work.

Do not fork the repository and immediately create a pull request. Instead, clone the repo, make your changes on a branch, and run the tests locally. Make sure your changes pass all tests, including the ones you did not write. Then push your branch and create a pull request.

Write a clear pull request description. Explain what you changed and why. Reference the issue number. If you are not sure about something, say so. Honesty is appreciated more than pretending you know everything.

Be patient. Maintainers are often busy. If you do not get a response in a week, send a polite follow-up. Do not spam or complain. The open source world is small, and your reputation matters.

Common Mistakes to Avoid

Many contributors make the same mistakes, and they are easily avoidable. Here are the ones I see most often.

Submitting a huge pull request that touches hundreds of files. This is the fastest way to get your work ignored. Break your work into small, logical commits. Each commit should do one thing.

Not writing tests. If a project has a test suite, you must add tests for your changes. This is non-negotiable. If you do not know how to write tests, learn. It is the most valuable skill you can develop as a contributor.

Ignoring the code style. Every project has a style guide, even if it is not written down. Look at the existing code and match it. This includes indentation, naming conventions, and comment style.

Asking questions that you can answer yourself. Before asking for help, read the docs, search the issue tracker, and try to figure it out. If you are stuck after a reasonable effort, then ask. But ask smart questions. Show what you have tried and where you are stuck.

The Long-Term Value of Contributing to Rising Stars

Contributing to a rising star is not just about the code you write. It is about building relationships. The maintainers of these projects are often the same people who will write you a recommendation letter, offer you a job, or introduce you to other opportunities. The community you join becomes your professional network.

In the long run, the projects you contribute to become part of your identity as a developer. When you interview for a job, you can talk about the features you built, the bugs you fixed, and the design decisions you influenced. That is far more compelling than saying you starred a repo or solved a few LeetCode problems.

There is also a financial angle. Many open source projects now have sponsorship programs. If you become a key contributor, you can receive funding for your work. This is not common, but it happens. And even if it does not, the skills you gain will make you more valuable in your day job.

Final Thoughts

The open source world is vast, but the projects that will define the next few years are already here. Zed, Dolt, PocketBase, NocoDB, Meilisearch, and Directus are all in a sweet spot. They are growing, they have real users, and they welcome contributors. Your job is to pick one, show up, and do good work.

Do not wait for the perfect moment. The perfect moment is now. Start by reading their documentation, joining their community, and looking at the open issues. You will be surprised at how quickly you can make a difference. And one day, when someone asks you how you got started, you will have a story to tell, not just a list of technologies.