All integrationsCode Repositories

Open VSX

Search the Open VSX Registry, where VSCodium, Cursor, Gitpod, Theia and other editors get their VS Code extensions.

actions
12
trigger
1

Triggers

Start a workflow when something happens in Open VSX.

  • New Open VSX extension versionRuns when an extension on Open VSX publishes a new version, with whether it is a pre-release, the VS Code versions it needs and its download and changelog links. Optionally only for stable versions or only for pre-releases.

Actions

Steps a workflow can run in Open VSX.

  • Search extensionsFind VS Code extensions on Open VSX by name or words, narrowed by category or by platform, and sorted by best match, downloads, rating or last update. Each result comes with its newest version, downloads, rating and download link. No API key required.
  • Get an extensionGet everything about one extension on Open VSX, its newest version or any other: description, categories, licence, the VS Code versions it needs, the extensions it depends on, downloads and rating, who published it, and the links to its README, changelog, manifest and every platform's download. No API key required.
  • Look up several extensionsLook up as many as 50 extensions in one step, by ID or link, with each one's newest version, the VS Code versions it needs, downloads and whether it is deprecated. IDs Open VSX doesn't have are listed rather than failing the step, so it also tells which of a list of VS Code extensions are available on Open VSX. No API key required.
  • List an extension's versionsList an extension's versions, newest version number first, with when each was published, whether it is a pre-release, the VS Code versions it needs and its download link. Narrow to stable versions or pre-releases, or to one platform's builds. No API key required.
  • Find extension buildsList the builds Open VSX holds for one extension or for every extension in a namespace: one row per extension and platform, with its version, the VS Code versions it needs and its download link. Narrow to a version or a platform, or include every older version too. No API key required.
  • Get download linksGet the download link of an extension's package (.vsix) for a version and platform, with its SHA-256 checksum to check the file against, the links to Open VSX's signature and public key, and every other platform's link for the same version. Nothing is downloaded, so the extension's download count is untouched. No API key required.
  • Get README, changelog or licenceGet the text of an extension's README, changelog or licence, for its newest version or any other, up to the length you choose. A version that ships no such file comes back with 'found' set to false rather than failing the step. No API key required.
  • Get an extension's manifestRead an extension's manifest (its package.json) for its newest version or any other: the VS Code versions it needs, what makes the editor start it, whether it runs in the browser or in an untrusted folder, the commands, languages and settings it adds, and the extensions and npm packages it depends on. No API key required.
  • Check VS Code compatibilityFind the newest version of an extension that works with a given VS Code version, using VS Code's own rule for the versions an extension says it needs. For editors built on an older VS Code, such as an outdated VSCodium, it says which version to install and gives its download link. No API key required.
  • List an extension's reviewsList the reviews people left for an extension on Open VSX, newest first, with each rating, comment and reviewer, and how many reviews gave each rating. No API key required.
  • Get a namespaceGet a namespace (the publisher part of an extension ID, such as 'redhat'): its name, description, website and whether it is verified, and every extension it publishes with its downloads and rating, most downloaded first. No API key required.
  • List version changesRead Open VSX's feed of version changes across the whole registry, oldest first: every version published, taken down or removed since a moment (the last 24 hours by default), optionally for one namespace or one kind of change. It hands back a cursor, so a scheduled workflow can carry on exactly where its last run stopped. Open VSX marks this feed as a preview. No API key required.

Automate Open VSX with Lodol.

Connect Open VSX and ask your AI for your first workflow.

Free plan, no credit card