IDE Extension

Install and configure the RepoGate IDE extension for your development environment.

RepoGate IDE Extension

RepoGate provides powerful IDE extensions that act as security gatekeepers for your project's dependencies. The extensions monitor dependency changes in real-time and validate them against your organization's security policies through the RepoGate platform.

Enterprise Dependency Governance
RepoGate embeds automated governance directly into your development lifecycle, preventing costly audit failures and accelerating business velocity.

Available IDEs

RepoGate extensions are available for the following development environments. Click on your IDE to visit the marketplace:

VS Code

Visual Studio Code

Available on VS Code Marketplace

View in Marketplace → JetBrains

JetBrains IDEs

IntelliJ IDEA, WebStorm, PyCharm, and more

View in Marketplace →
Need support for another IDE?
If your preferred IDE is not listed, please contact the RepoGate team to request support. We're continuously expanding our IDE coverage.

Installation

Choose your IDE below for specific installation instructions:

Installing on Visual Studio Code

The easiest way to install RepoGate is directly from the VS Code Marketplace:

  1. Open VS Code
  2. Go to Extensions (Ctrl+Shift+X or Cmd+Shift+X)
  3. Search for "RepoGate"
  4. Click Install

Or install directly from the VS Code Marketplace.

VS Code Extension

From VSIX File

If your organization distributes the extension manually:

  1. Download the .vsix file
  2. Open VS Code Extensions view
  3. Click the ... menu (Views and More Actions)
  4. Select Install from VSIX...
  5. Select the downloaded file

Installing on JetBrains IDEs

Install RepoGate from the JetBrains Marketplace:

  1. Open your JetBrains IDE (IntelliJ IDEA, WebStorm, PyCharm, etc.)
  2. Go to Settings/Preferences → Plugins
  3. Click the Marketplace tab
  4. Search for "RepoGate"
  5. Click Install
  6. Restart your IDE when prompted

Or install directly from the JetBrains Marketplace.

Supported JetBrains IDEs

  • IntelliJ IDEA
  • WebStorm
  • PyCharm
  • PhpStorm
  • GoLand
  • RubyMine
  • CLion
  • Rider

Configuration

Authentication

RepoGate offers two authentication methods to connect your IDE extension to the platform:

Option 1: Sign In with EntraID (Recommended)

The recommended authentication method uses Microsoft Entra ID (formerly Azure Active Directory) for secure, seamless single sign-on:

  1. In your IDE, open the Command Palette or RepoGate menu
  2. Select RepoGate: Sign In with EntraID
  3. A browser window will open for authentication
  4. Sign in with your organizational credentials
  5. Return to your IDE - you're now authenticated
Benefits of EntraID Authentication:
• No need to manage API tokens
• Automatic token refresh
• Centralized access control through your organization's identity provider
• Enhanced security with multi-factor authentication support

Option 2: Sign In with API Token (Legacy)

For organizations not using EntraID, you can authenticate using an API token:

  1. Log in to your RepoGate dashboard at app.repogate.io
  2. Navigate to Settings → API Tokens
  3. Generate a new token or copy an existing one
  4. In your IDE, select RepoGate: Sign In with API Token
  5. Paste your token when prompted
API Token Setup

API URL

The API URL points to your RepoGate instance. The default value is https://app.repogate.io/api/v1 for cloud-hosted instances. If you're using a self-hosted or enterprise instance, update this URL to match your deployment.

Settings

Configure RepoGate behavior through your IDE's settings:

Setting Type Default Description
repogate.apiToken string "" API authentication token (stored securely)
repogate.apiUrl string https://app.repogate.io/api/v1 URL of the RepoGate API
repogate.enabled boolean true Enable/disable the extension
repogate.logLevel string "info" Logging verbosity (debug, info, warn, error)

How It Works

Initialization Flow

When you first install RepoGate or open a workspace with the extension enabled, the following initialization sequence occurs:

  1. First Install: Extension scans all existing packages and sends them to the /queue endpoint
  2. Baseline Established: The RepoGate platform receives an inventory of current dependencies
  3. Watchers Start: File watchers activate only after a successful scan
  4. Continuous Monitoring: The extension watches for any dependency changes

Supported Package Managers

RepoGate currently monitors the following package ecosystems and their associated files:

Ecosystem Files Monitored Status
npm package.json ✅ Fully Supported
Maven pom.xml ✅ Fully Supported
Gradle build.gradle, build.gradle.kts ✅ Fully Supported

Security & Privacy

Token Storage

RepoGate uses your IDE's secure storage mechanism to store your API token securely. This provides:

  • Encryption: Tokens are encrypted at rest
  • Automatic Migration: Tokens previously stored in plain settings are automatically migrated to secure storage
  • Secure Access: Only the RepoGate extension can access stored tokens

Logging & Data Sanitization

All sensitive data is automatically redacted from logs, including:

  • API tokens
  • Passwords
  • Authentication headers

Troubleshooting

"No API token configured"

Solution:

  1. Open your IDE settings
  2. Search for "RepoGate"
  3. Enter your API token in the settings
  4. Test the connection using the RepoGate extension menu

"Connection failed"

Possible Causes:

  • RepoGate service not running
  • Wrong API URL or port
  • Invalid API token
  • Network or firewall issues

Solution:

  1. Verify the RepoGate service is running
  2. Check the API URL in settings
  3. Test the connection using the extension menu
  4. Check the IDE's output/console for detailed error messages

"Bootstrap failed"

Cause: Initial package scan failed

Solution:

  1. Check API connection status
  2. Test the connection using the extension menu
  3. Manually trigger a scan from the RepoGate menu

Packages not being monitored

Solution:

  1. Check that repogate.enabled is set to true
  2. Verify API token is configured
  3. Check the IDE output/console for errors
  4. Ensure the file is not in node_modules or other excluded directories