RepoPilot

microsoft/vscode · Architecture

A static read of how microsoft/vscode is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 100/100
0
Import cycles
lower is better
400
Modules parsed
48 edges
100%
Layeredness
clean-layer ratio

Most-depended-on modules

These are the highest-fan-in files — change them and the blast radius is largest. Read them first.

  • src/vs/base/common/marked/marked.js2 importers · radius 2
  • src/vs/base/browser/ui/actionbar/actionbar.css2 importers · radius 2
  • src/vs/base/browser/ui/dropdown/dropdown.css2 importers · radius 2
  • src/vs/base/browser/ui/findinput/findInput.css2 importers · radius 2
  • src/vs/base/browser/ui/grid/gridview.css2 importers · radius 2
  • src/vs/base/browser/ui/list/list.css2 importers · radius 2
  • src/vs/base/browser/ui/tree/media/tree.css2 importers · radius 2
  • src/vs/base/browser/dompurify/dompurify.js1 importers · radius 1

Modules (24)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

Ask AI about microsoft/vscode

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.