Sensitive Areas

The Sensitive Areas tab lists files where a change carries more risk. It has two tables, Hotspots and Change Impact.

Both tables come from the repository’s latest completed assessment.

Open the tab

Open Repositories and select a repository.
Select the Sensitive Areas tab.
Select Hotspots or Change Impact. Each label shows how many files are in that table.

Use Search files to filter both tables by file path.

A hotspot is a file that changes often. A file with frequent changes is more likely to be touched by an AI tool, and more likely to break.

Column	Meaning
Files	The file path.
Commits	How many commits changed the file.
Lines	The line count the assessment reported for the file.
Reason	Why the assessment flagged the file.

The table is sorted with the highest-scoring hotspots first.

Change impact shows files that many other files use. A change to one of these files can affect every file that depends on it.

Column	Meaning
Files	The file path.
Used by	How many files use this file.

The table is sorted with the most-used files first. Select a Used by value to open a panel that lists the files using it.

Message	Meaning
No completed assessment yet	Run an assessment first.
This assessment found no hotspots	No file stands out as changing unusually often.
Change impact was not analyzed in this assessment	The assessment is older than this analysis, or the repository has no supported source files. Select Re-assess.
Change impact could not be analyzed in this assessment	The analysis failed. Select Re-assess to try again.
No widely depended-on files	No file crossed the change impact threshold. This is a good sign.