Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/publish-vscode-extension.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ on:
extension:
description: Which extension
type: choice
options: [api-client, auto-rename-tag, blast-radius, code-guard, codesnap, docker, document-viewer, env, error-lens, garden, git-graph, live-server, mcp-studio, mongodb, npm-intellisense, path-intellisense, pets, port-manager, rewind, todo-tree, wrapped]
options: [api-client, auto-rename-tag, blast-radius, code-guard, codesnap, docker, document-viewer, env, error-lens, garden, git-graph, hotspots, live-server, mcp-studio, mongodb, npm-intellisense, path-intellisense, pets, port-manager, rewind, todo-tree, wrapped]
default: live-server
target:
description: Where to publish
Expand Down
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,6 +136,7 @@ The team behind Veyra (FlightCoders) also makes free extensions for VS Code, Cur
| Extension | What it does |
| --- | --- |
| [**Veyra Blast Radius**](https://marketplace.visualstudio.com/items?itemName=flightcoders.veyra-blast-radius) | See every file, page, route and test your change can break, and run only the affected tests |
| [**Veyra Hotspots**](https://marketplace.visualstudio.com/items?itemName=flightcoders.veyra-hotspots) | A heat map of your codebase: find the complex, often-changed files where bugs live |
| [**Veyra Rewind**](https://marketplace.visualstudio.com/items?itemName=flightcoders.veyra-rewind) | Local history and time travel for every file; find code you deleted |
| [**Code Garden Veyra**](https://marketplace.visualstudio.com/items?itemName=flightcoders.veyra-garden) | A garden that grows while you code: saves water it, commits make flowers bloom |
| [**Veyra Live Server**](https://marketplace.visualstudio.com/items?itemName=flightcoders.veyra-live-server) | Live reload on save; CSS updates without a reload |
Expand Down
5 changes: 5 additions & 0 deletions extensions/hotspots/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
out/
dist/
bundle/
node_modules/
.vscode-test/
10 changes: 10 additions & 0 deletions extensions/hotspots/.vscodeignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
src/**
test/**
out/**
dist/**
node_modules/**
tsconfig.json
**/*.map
.gitignore
.vscode-test/**
media/readme/**
11 changes: 11 additions & 0 deletions extensions/hotspots/CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# Changelog

## 1.0.0

- The Hotspot Map: every file as a tile, sized by lines of code and coloured by risk, with zoom, filter, hover details and a side panel for each file.
- Five colour modes: Hotspots, Change frequency, Complexity, Code age and Knowledge risk.
- Top Hotspots, Changes Together and Knowledge Risks in the sidebar.
- Flames on the hottest files in the Explorer, and the open file's rank in the status bar.
- Why Is This a Hotspot?, Open Files That Change With This One, and File History with each commit's diff.
- Copy a Markdown report.
- Choose the period: the last month up to all history. Refreshes after commits, pulls and checkouts.
21 changes: 21 additions & 0 deletions extensions/hotspots/LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
MIT License

Copyright (c) 2026 Vikram Singh

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
91 changes: 91 additions & 0 deletions extensions/hotspots/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,91 @@
<p align="center">
<img src="https://raw.githubusercontent.com/fcopensource/veyraeditor/main/extensions/hotspots/media/readme/map.png" alt="The Hotspot Map: every file in the project as a tile sized by its lines of code and coloured from calm slate to hot coral, with the top hotspots listed on the right" width="100%">
</p>

# Veyra Hotspots

**A living heat map of your codebase. Find the files where bugs live.**

Some files cause most of the trouble: they're complicated **and** they change all the time. Veyra Hotspots reads your project's own git history, finds those files, and shows your whole codebase as one heat map. It also shows who knows each file, which files secretly change together, and the code only one person understands. **Free, 100% local, nothing to configure.** By the makers of [Veyra Studio](https://veyraeditor.com).

- 🔥 **The hotspot map:** every file is a tile, sized by its code and coloured by risk. Zoom into any folder.
- 🏆 **Top hotspots, ranked:** the files to refactor first, with the reason spelled out.
- 🔗 **Files that change together:** pairs that keep landing in the same commits, often across folders. A hidden dependency, made visible.
- 👤 **Knowledge risks:** files only one person has changed, and code whose only author has left.
- 🧭 **Five ways to look:** Hotspots, Change frequency, Complexity, Code age and Knowledge risk.
- 🚩 **Flames in the Explorer** on the hottest files, and the open file's rank in the status bar.
- 📋 **Copy a report** for a planning meeting, an issue or a pull request.

---

## Why hotspots?

Studies of real codebases keep finding the same thing: a small share of the files attract most of the bugs and most of the work. They are the files that are **complex** (deeply nested, long) and **changed often**. Either one on its own is fine: complex code nobody touches is stable, and simple code that changes a lot is easy. Together they're where mistakes happen.

Veyra Hotspots scores every file on both, from your git history and the code as it is today, so you know where refactoring pays off most.

## The map

<img src="https://raw.githubusercontent.com/fcopensource/veyraeditor/main/extensions/hotspots/media/readme/detail.png" alt="App.tsx selected in the map: rank 1 critical hotspot, 38 commits, 785 lines, nested 9 levels deep, who knows it, and dashed lines to lib.rs and workspace.spec.ts, the files that change with it" width="100%">

- **Hover** a tile to see its commits, size, depth, last change and main author.
- **Click** a file for the full story: who knows it, how deep it's nested, and the files that change with it, linked by dashed lines on the map.
- **Double-click** to open it. **Click a folder's name** to zoom in, and use the breadcrumb or <kbd>Esc</kbd> to zoom out.
- **Type** to filter (<kbd>/</kbd> jumps to the filter box).

Open it from the **Hotspots** icon in the activity bar, or run **Hotspots: Show Hotspot Map**.

## Five colour modes

| Mode | Hot means |
| --- | --- |
| **Hotspots** | Complex *and* changed often: refactor these first |
| **Change frequency** | Touched by many commits |
| **Complexity** | Deeply nested code |
| **Code age** | Not changed for a long time |
| **Knowledge risk** | Only one person has changed it, or its only author has left |

<img src="https://raw.githubusercontent.com/fcopensource/veyraeditor/main/extensions/hotspots/media/readme/knowledge.png" alt="The same map in Knowledge risk mode: files changed by one person in pink, shared files in blue" width="100%">

## In the sidebar

| | |
| --- | --- |
| **Top Hotspots** | The 50 hottest files, ranked. Hover for why |
| **Changes Together** | Pairs of files that change in the same commits, with how often |
| **Knowledge Risks** | Files whose only author has left, then files only one person has changed |

Right-click a file for **Why Is This a Hotspot?**, **Show in Hotspot Map**, **Open Files That Change With This One** and **File History** (its recent commits, each one's diff a click away).

## How it's measured

- **Change frequency:** the commits that touched the file in the period you choose (the last year by default), merges excluded.
- **Complexity:** the file's lines of code and how deeply they're indented. Indentation follows nesting (ifs in loops in callbacks) in every language, so it works the same for TypeScript, Python, Go, Rust, C#, Java and the rest.
- **Hotspot score:** change frequency × complexity, each on a log scale so one giant file doesn't flatten the rest.
- **Changes together:** two files that shared at least 4 commits, together at least 40% of the time. Huge commits (formatting runs, mass renames) are ignored.
- **Knowledge:** who changed the most lines. "Has left" means no commits for 6 months.

Lock files, build output, `node_modules`, minified files, snapshots and migrations are left out. Change that with `veyraHotspots.exclude`.

## Settings

| Setting | Default | |
| --- | --- | --- |
| `veyraHotspots.months` | `12` | How much history to read: 1, 3, 6, 12, 24 months, or 0 for all |
| `veyraHotspots.explorerBadges` | `true` | Flames on the hottest files in the Explorer |
| `veyraHotspots.explorerTop` | `10` | How many files get a flame |
| `veyraHotspots.statusBar` | `true` | The open file's rank in the status bar |
| `veyraHotspots.exclude` | lock files, build output… | Files to leave out |
| `veyraHotspots.maxCommits` | `20000` | The most commits to read |

## Private

Everything happens on your computer. Hotspots runs `git log` and reads your files, and that's all: no account, no telemetry, nothing sent anywhere. It needs a trusted folder, because it runs git.

## More from Veyra

Veyra Hotspots is part of a family of free extensions from [Veyra Studio](https://veyraeditor.com), a lightweight code editor. Pairs well with [Veyra Blast Radius](https://veyraeditor.com/blast-radius), which shows what a change can break before you commit. See them all at **[veyraeditor.com/extensions](https://veyraeditor.com/extensions)**.

## License

[MIT](LICENSE) © Flight Coders
1 change: 1 addition & 0 deletions extensions/hotspots/media/activity.svg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added extensions/hotspots/media/icon.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added extensions/hotspots/media/readme/detail.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added extensions/hotspots/media/readme/knowledge.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added extensions/hotspots/media/readme/map.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Loading