Reaching version 1.0.0 is a special moment for any open source project.
It marks more than a collection of features or bug fixes. It reflects years of collaboration, thousands of commits, countless discussions, and a shared belief that an idea is worth building together.
Today, we are pleased to celebrate the release of Eclipse Open VSX 1.0.0
While the recent articles in this series focused on security, scalability, infrastructure investments, and software sovereignty, this post is about something even more important: the people who made Open VSX what it is today.
Why Open VSX matters
Open VSX was created to solve a practical challenge that has only become more important over time.
As the Visual Studio Code extensibility model emerged as a de facto standard across modern developer tools, many vendors wanted to remain compatible with that ecosystem without becoming dependent on a proprietary marketplace operated by a single company.
Open VSX provides a vendor neutral, open source governed alternative.
What started as a solution for VS Code compatible tools has evolved into critical infrastructure used by a growing ecosystem of editors, IDEs, cloud development environments, and AI powered developer tools.
Today, Open VSX helps power extension experiences across a diverse landscape of products and platforms. It has become a foundational component for organisations building open, interoperable developer tooling. See also: Open VSX and software sovereignty in the era of AI-driven developer tools
That evolution makes the 1.0.0 milestone particularly meaningful.
A milestone years in the making
Version 1.0.0 is not the beginning of the Open VSX story.
The project has been serving users and tooling ecosystems for years. It has supported millions of extension downloads, attracted a growing contributor community, and become an essential part of the modern developer tooling landscape.
The release includes a number of improvements that reflect the project's growing role as production infrastructure. Among them are the introduction of a new read-only mode, support for TLS secured Redis connections, additional security hardening measures, operational reliability improvements, and continued work to strengthen deployment and maintenance workflows.
And in true open source fashion, by the time we started celebrating version 1.0.0, version 1.0.1 was already available, bringing additional fixes, dependency updates, cache management improvements, and further refinements to the platform.
Taken together, these releases demonstrate a healthy project with active maintainers, responsive contributors, and a clear commitment to continuous improvement.
Thank you to the people behind Open VSX
Open source projects succeed because people choose to invest their time, expertise, and energy into them.
Open VSX project would not exist without the vision and early work of the TypeFox team.
The early foundations of Open VSX were shaped by contributors including Miro Spönemann, and Jan Bicker, and some others who recognised the need for an open and vendor neutral extension registry. Their work established the technical foundations of the project and helped create an open source alternative that could serve a growing ecosystem of tools and platforms.
Then, the first deployment of the Open VSX Registry runtime by the Eclipse Foundation was established to serve the Eclipse Theia ecosystem, providing an open and vendor neutral extension registry for an IDE platform that was compatible with the Visual Studio Code extension ecosystem while remaining independent from Visual Studio Code itself. See also: Why Cursor, Windsurf and co fork VS Code, but shouldn't
As the project grew, Aart van Baren played a key role in its stewardship, helping guide Open VSX through important phases of growth, maturity, and its evolution within the Eclipse ecosystem. More recently, Thomas Neidhart has been a driving force behind the project's technical evolution and the work leading to the 1.0.0 milestone. His contributions over the past year have had a significant impact on both the platform itself and the momentum of the community around it.
I would also like to thank Vinokur Ginzburg , Achim Demelt, Christopher Tsamas, Martin Lowe and the all the contributors who helped make the 1.0.0 releases possible...
Beyond the open source project itself, the success and growing adoption of the Open VSX Registry has also been supported by many individuals who contributed through programme management, operations, ecosystem development, and community building. In that regard, I would like to recognise Brian King and John Kellerman and others who helped expand the reach and impact of the registry hosted by the Eclipse Foundation over the years.
What began as a practical solution for Eclipse Theia quickly proved valuable to a much broader ecosystem. Open VSX evolved into a vendor neutral registry serving a growing number of developer tools, platforms, and AI powered development environments. Today, the registry delivers more than 600 million extension downloads per month!
Finally, thank you to the Eclipse Foundation teams operating the Open VSX Registry, and the thousands of extension publishers and users who continue to make Open VSX a thriving ecosystem.
As Open VSX has grown into critical infrastructure for modern developer tools, the Eclipse Foundation has also introduced the Open VSX Managed Registry, a production-grade service for organisations that depend on Open VSX at scale and require enterprise-grade operational guarantees, support, and SLA-backed reliability. The managed service helps ensure that commercial adopters can rely on Open VSX with confidence while contributing to the long-term sustainability of the ecosystem. Learn more at https://managed.open-vsx.org
Open source milestones are never the achievement of a single person or organisation. They are the result of a community working together over time.
