The Open VSX Registry at the Eclipse Foundation: What You Need to Know

The Open VSX Registry is a vendor-neutral, open source alternative to the Microsoft Visual Studio Marketplace for VS Code extensions. It’s built on the Eclipse Open VSX project, and delivers on the industry’s need for a more flexible and open approach to VS Code extensions and marketplace technologies.

As of December 2020, the Open VSX Registry is hosted at the Eclipse Foundation and is being managed under the Eclipse Cloud Development (ECD) Tools Working Group.

Tim DeBoer, Chair of the ECD Tools Working Group Steering Committee, says hosting the Open VSX Registry at the Eclipse Foundation is a logical move.

“The Eclipse Open VSX project is already fostered within the ECD Tools ecosystem. And, as the number of extensions in the Open VSX Registry grows, we expect the marketplace to play an increasingly important role for developers who rely on open source cloud development tools,” DeBoer says.

Open Source Developer Tools Need an Open Source Marketplace

In contrast to the Visual Studio Marketplace that licenses free extensions only for use with Microsoft VS products, with the Open VSX Registry, developers have free and open access to VS Code extensions that can be used with any technology or tool that supports them. In addition, because the Eclipse Open VSX source code is open to all, anyone can adopt, adapt, and enhance the marketplace technology to meet their specific needs.

The Open VSX Registry is already the default extension registry for Eclipse Theia, Gitpod, and VSCodium. And it can be easily added as the default extension registry in forks of VS Code.

According to Sven Efftinge, project co-lead for Eclipse Theia and Eclipse Open VSX, platforms such as Eclipse Theia simply don’t make sense without the ability to add extensions.

“It makes no difference that the software is open source if it can’t be used by downstream adopters and inventors simply because they can’t install extensions,” Efftinge says. “Besides, it would be a very boring landscape if no one tries to innovate on top of what Microsoft does.”

Extension Users Have a Familiar and Intuitive User Interface to Find Extensions

If you’re already using the Open VSX Registry, the technology’s transition to the Eclipse Foundation has no impact on the way you access or use extensions.

If you’re accessing extensions through the Open VSX Registry for the first time, you’ll notice it’s very similar to the Visual Studio Marketplace from a usability perspective (Figure 1). Icons identify extensions and publishers, and star ratings are provided for each extension. Extensions can be found by name, tag, or description, filtered by category, and sorted by various criteria.

Figure 1: Open VSX Registry

Figure 1: Open VSX Registry

Extension Publishers Must Sign a Publisher Agreement and Choose a License

With the transition to the Eclipse Foundation, all Open VSX Registry extension publishers — even those who published extensions before the transition — must create an Eclipse Foundation account and sign a publisher agreement.

In addition, all extensions in the Open VSX Registry must be licensed under the license of your choice. To identify the license under which you’re publishing the extension, simply add the license identifier to the extension manifest (package.json) file. If you don’t identify a license, you’ll have the opportunity to choose the default MIT license during the publishing process.

We’ve made the publishing process as straightforward as possible, and provided the steps in the Open VSX wiki.

Previous publishers will also find that the extension ownership model has changed since the transition to the Eclipse Foundation. The Namespace Access wiki page provides the latest policy details and describes the new process to claim extension ownership.

Organizations Can Create Their Own Internal Extension Registry

The source code for the Open VSX Registry is available in GitHub so organizations can create an in-house registry that’s customized for the extensions their developers use and their internal processes. Organizations can also connect their in-house extension registry to the upstream public Open VSX Registry so their developers can easily access private and public extensions (Figure 2).

Figure 2: An Internal Extension Registry Connected to Public Registry

Figure 2: An Internal Extension Registry Connected to Public Registry

Tool Developers Can Add Open VSX Registry Access to Their Software

To make it easy for tool developers to integrate access to the Open VSX Registry into any IDE, desktop tool, or online tool, a REST API provides endpoints for creating namespaces, publishing, querying metadata, and searching.

Miro Spönemann, co-lead of the Eclipse Open VSX project, points out this is the first time tool developers outside of Microsoft can integrate access to VS Code extensions into their solutions.

“With this public API, any developer can provide their users with access to VS Code extensions,” Spönemann says. “This is a significant new capability that will help developers add value to their solutions.”

Learn More

Take a few minutes to explore the more than 900 extensions in the Open VSX Registry. Once you’re on the site, you’ll find easy access to detailed documentation, an FAQ, the community conversation on Gitter, and more.

For details about the Eclipse Open VSX project and access to the source code for the Open VSX Registry, visit the project page.

About the Author

Dr. Jan Köhnlein

Dr. Jan Köhnlein

Dr. Jan Köhnlein is a co-founder of TypeFox GmbH. TypeFox is a major contributor to the Eclipse Open VSX project. The company also developed and hosted the Eclipse Open VSX Registry before its transition to the Eclipse Foundation.