Integrations/VS Code Extension

Browse and inspect your Cloudsmith packages without leaving VS Code

The Cloudsmith VS Code Extension puts your entire artifact registry inside your editor. Browse workspaces, inspect package metadata, and access repositories without switching tabs or opening a browser. It works with VS Code, Cursor, and Theia IDEs.

How we support VS Code Extension

Cloudsmith gives your development team direct access to package management from inside VS Code. Browse, inspect, and act on your artifacts without breaking your flow.
    Workspace and repository browsing
    Navigate your Cloudsmith workspaces and repositories from the VS Code Activity Bar using a familiar tree-based explorer. No browser required.
    Rich package metadata inspection
    View package status, version, tags, download counts, upload timestamps, and slug details directly in the tree view. Use Inspect Package to pull the full raw JSON dataset.
    Package group support
    Toggle package group view to see count, size, download totals, and last-pushed date for each group, keeping large repositories organised and scannable.
    API key and service account authentication
    Authenticate using a personal API key or a service account token directly from within VS Code. Credentials are stored securely and used to load your repositories on demand.
    Cursor and Theia IDE compatibility
    The extension installs via the VS Code Marketplace or a .vsix file, making it compatible with Cursor and Theia as well as VS Code itself.

Why teams integrate Cloudsmith with VS Code Extension

Developers lose focus every time they leave the editor to check a package version or browse a registry. Cloudsmith removes that friction entirely.
Without CloudsmithDevelopers constantly switch between VS Code and a browser to check package versions, browse repositories, or verify metadata. Each switch breaks focus and slows down delivery.
With CloudsmithThe Cloudsmith Explorer panel surfaces workspaces, repositories, and package details right inside VS Code. Developers stay in flow and find what they need without leaving the editor.
Without CloudsmithVerifying the exact status, version, or tags on a package means navigating to the Cloudsmith web app, finding the right repository, and hunting through package lists. This adds up across a team.
With CloudsmithSelect any package in the tree view to see status, version, tags, slug, download count, and upload time at a glance. Use Inspect Package to pull the full JSON payload straight into your editor.
Without CloudsmithSetting up access to a private registry from an IDE typically means copying tokens from a browser, consulting documentation, and configuring settings files manually.
With CloudsmithEnter your Cloudsmith API key or service account token once in the VS Code prompt. The extension connects immediately and loads all your workspaces and repositories with a single refresh.

Frequently asked questions

  1. It adds a Cloudsmith Explorer panel to VS Code that lets you browse your workspaces, repositories, and packages in a tree view. You can inspect package metadata, copy field values, and open packages directly in the Cloudsmith web app, all without leaving your editor.

  2. Open the Extensions view in VS Code (Ctrl+Shift+X), search for Cloudsmith, and click Install. You can also install directly from the VS Code Marketplace or download the .vsix file from the GitHub releases page and install it manually via the Extensions menu.

  3. After installation, click the key icon in the Cloudsmith Explorer view and enter your personal API key or service account token. Entitlement tokens are not supported. Once entered, click the refresh icon to load your workspaces and repositories.

  4. Yes. Cursor and Theia both support VS Code extensions. Install via the VS Code Marketplace if available in your IDE, or use the .vsix file from the GitHub releases page to install manually.

  5. The extension displays up to 30 packages per repository by default. You can adjust this limit between 1 and 30 in VS Code settings under the Cloudsmith section.

  6. The tree view shows status, name, slug, slug perm, download count, version, tags, and upload timestamp for each package. You can right-click any field to copy its value. For the full dataset, use the Inspect Package command to retrieve the raw JSON.

  7. Package Groups let you view packages aggregated by group rather than individually. Enable the Show Packages by Group setting in VS Code preferences. Group view shows count, total size, download count, and last-pushed date for each group.

  8. By default, the raw JSON is sent to the VS Code Output window. You can change this in extension settings to open the output in a new untitled document instead, which makes it easier to search and copy.

  9. Yes. Right-click any package in the explorer and select Open Package in Cloudsmith. This opens the package page in your default browser. If you use the legacy Cloudsmith web app, you can enable the Use Legacy Web App setting to point URLs there instead.

  10. The extension works with any Cloudsmith account that has API access. Authenticate with a personal API key or service account token. Check your Cloudsmith workspace settings to confirm API keys are enabled for your account.

  11. The official documentation is available at docs.cloudsmith.com. It covers installation, authentication, configuration options, and all supported features of the VS Code Extension.

Integrations

Discover more Cloudsmith Integrations