Add a License to your VS Code Extension and sign the Publisher Agreement

Thank you for being part of the Open VSX community by adding your extensions to the Open VSX Registry. Please note that the service was recently transferred to the Eclipse Foundation and urgent action on your part is needed so we can continue to list your extensions. To ensure uninterrupted service, please add a license to your extension and upload a new version as early as possible before January 15, 2021. To include a license with the extension, add a license field with the license identifier in the package.json and add a LICENSE file with the full license text. If you are unsure which license to choose, check the list of OSI-approved licenses.

Furthermore, publishing to open-vsx.org now requires you to sign the Eclipse Publisher Agreement.

Regrettably extension versions that have no license will be deleted after the date mentioned above. Of course you can publish them again with a license at a later date.

Please note, the latest version of the ovsx tool offers to add the MIT license when you try to publish without a license.

Useful links: Eclipse Publisher Agreement Eclipse Foundation Open VSX Registry Frequently Asked Questions (FAQ)

More details are in these recent blog posts: https://blogs.eclipse.org/post/brian-king/open-vsx-registry-under-new-management https://blogs.eclipse.org/post/brian-king/new-era-open-vsx-registry

cevr / aeon

Add a License to your VS Code Extension and sign the Publisher Agreement #2