Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>RepoRadar: Codebase InsightsNew to Visual Studio Code? Get it now.
RepoRadar: Codebase Insights

RepoRadar: Codebase Insights

RepoRadar

| (0) | Free
Understand unfamiliar codebases, then discover better building blocks.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

RepoRadar

Understand unfamiliar code. Find the next right building block.

RepoRadar is a premium VS Code workspace companion for early users. It uses two explicit API stages:

  1. A connected, OpenAI-compatible analysis API reads a consented workspace research pack and returns a structured explanation of the codebase.
  2. Exa searches GitHub only for repositories related to the highest-value opportunities. RepoRadar verifies each candidate with GitHub's repository API before showing its canonical link, description, activity, and estimated match percentage.

Nothing is sent until the user presses Understand workspace and confirms the privacy prompt, which identifies the analysis endpoint. The endpoint is read only from user-level settings, must use HTTPS, and cannot redirect requests. Keys live in VS Code Secret Storage, never in settings or source control. Before GitHub research, users see and must approve the exact queries sent to Exa; credential-like strings and long exact source excerpts are excluded.

Run in VS Code

npm install
npm run build

Open this folder in VS Code, press F5, then open the RepoRadar icon in the Activity Bar. Connect an OpenAI-compatible chat-completions endpoint to analyze a workspace. Exa is optional and can be connected to discover GitHub repositories.

Product principles

  • Understanding precedes search. RepoRadar produces a project brief before it researches public solutions.
  • Evidence remains visible. Feature cards link each conclusion to source paths supplied to the analysis model.
  • Consent is concrete. Users see the number of files and characters to be transmitted before every analysis.
  • External destinations are explicit. Workspace settings cannot redirect analysis requests; redirects are blocked, and Exa searches require a separate review of the exact query text.
  • Provider keys are private. Credentials are stored through VS Code's SecretStorage API.
  • Search stays on GitHub. Exa queries are restricted to github.com, and results must resolve to a live, non-archived repository through GitHub's API. Match percentages estimate search relevance to a feature; they do not guarantee compatibility.
  • A provider is replaceable. The understanding and discovery clients are isolated behind adapters.

Current scope

This is an early-user extension foundation. The semantic analysis currently uses a bounded workspace research pack; large-repository map/reduce analysis, language-server adapters, deeper compatibility analysis, and team cloud sync belong to the next product milestones.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
  • Your Privacy Choices
  • Consumer Health Privacy
© 2026 Microsoft