Skip to content

Veyra Hotspots 1.0.0: a living heat map of your codebase - #39

Merged
fcopensource merged 1 commit into
mainfrom
hotspots-extension
Nov 19, 2026
Merged

fcopensource merged 1 commit into
mainfrom
hotspots-extension

Conversation

@fcopensource

Copy link
Copy Markdown
Owner

A new, original VS Code extension: Veyra Hotspots. It finds the files where bugs live: code that is both complex and changed often, from the project's own git history.

What it does

  • The Hotspot Map: every file as a tile, sized by lines of code and coloured by risk. Zoom into folders, filter, hover for details, click a file for its full story (who knows it, nesting depth, last change) with dashed links to the files that change with it.
  • Five colour modes: Hotspots, Change frequency, Complexity, Code age, Knowledge risk.
  • Sidebar: Top Hotspots (ranked), Changes Together (temporal coupling, huge commits ignored), Knowledge Risks (only one author, or the only author has left).
  • 🔥 flames on the hottest files in the Explorer (only warm-or-hotter files), and the open file's rank in the status bar.
  • Why Is This a Hotspot?, Open Files That Change With This One, File History (recent commits with their diffs), Copy report (Markdown).
  • Period from the last month to all history; refreshes after commits, pulls and checkouts. Language-agnostic complexity (indentation depth), 100% local.

Also in this PR

  • hotspots added to the Publish VS Code extension workflow
  • A row in the repo README's extension table
  • The tested .vsix (47 KB) in extensions/hotspots/release/

Tested

  • 14 unit tests: git log parsing (binary files, quoted paths), complexity metric, scoring, period, knowledge risk, coupling, colour modes, treemap geometry (no overlaps, areas match, no slivers), globs, report.
  • 9-step integration test inside VS Code on a repo with two years of backdated history from four people: ranking, lists, Explorer flames, status bar, knowledge risk of a departed author, report, the map page loading under the webview security policy, and a new commit being picked up. It caught flames on tiny files in small projects, now fixed.
  • README screenshots are the real map of this repository from the extension's own engine (author names anonymized).

After merging

Publish from Actions → Publish VS Code extension → hotspots.

🤖 Generated with Claude Code

A new, original VS Code extension. From the project's own git history and the
code as it is today, it scores every file on change frequency x complexity
(indentation depth, language-agnostic) and shows:

- the Hotspot Map: a zoomable canvas treemap sized by lines of code, coloured
  by risk, with five modes (hotspots, change frequency, complexity, code age,
  knowledge risk), hover details, a per-file panel and dashed links to the
  files that change with it
- Top Hotspots, Changes Together (temporal coupling, huge commits ignored)
  and Knowledge Risks (single owner, or the only author has left)
- flames on the hottest files in the Explorer, the open file's rank in the
  status bar, Why Is This a Hotspot?, File History with diffs, Markdown report

15 unit tests (parser, metrics, scoring, coupling, knowledge, treemap
geometry, globs) and a 9-step integration test in VS Code on a repo with two
years of backdated history. README screenshots are the real map of this repo
(author names anonymized). Added to the publish workflow and repo README.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fcopensource
fcopensource merged commit 429ee5b into main Nov 19, 2026
5 of 6 checks passed

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛡️ Veyra Code Guard · Grade B (88/100)

Review needed: high-risk findings. Found 1 suspicious line in pull request #39: 🔴 1 high

Severity Where What How to fix
🔴 high extensions/hotspots/src/model.ts:412 Invisible character in code: Invisible character <U+200B> on this line. Remove the invisible characters, then check the names on the line: a variable with a hidden character is a different variable from the one it looks like.

Each line is marked in Files changed. To accept a line that is safe, add a comment veyra-guard-ignore: <rule> on it or the line above.


// ------------------------------------------------------------------------------------------------ globs

/** A glob like "**​/node_modules/**" or "**​/*.min.*" as a RegExp over workspace-relative POSIX paths. */

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 Invisible character in code (high)

Invisible character <U+200B> on this line.

Zero-width and blank characters can hide extra code or create look-alike names (two variables that look identical but aren't), a known way to sneak in backdoors.

How to fix: Remove the invisible characters, then check the names on the line: a variable with a hidden character is a different variable from the one it looks like.

Veyra Code Guard · rule invisible-character · add veyra-guard-ignore: invisible-character to accept

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants