> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iriscode.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace and Folder Analysis: Aggregate Scores and Trends

> Score the whole project at once: hotspots, unused packages, issues, TODOs and trends over time.

Reviewing files one at a time tells you about each file. It does not tell you where the problems are concentrated.

A workspace scan reads every supported file and ranks the results, so the parts of the codebase that need attention are listed rather than guessed at.

Your **first full project review is free** and needs no account. Iris Code saves it locally, so the rankings, issues, TODOs, security findings and duplicates stay available without scanning again. Rescanning requires Pro.

## Running one

**Iris Code: Analyse Workspace** from the command palette, or the **Scan Workspace** button in the Workspace tab. It walks every supported file and gives you:

* **Readiness** - the top-level score, blockers, warnings, TODO load and trend
* **The totals** - files, directories, lines, functions
* **A language breakdown**
* **Hotspots** - the five biggest files and the five most complex
* **Unused packages** - declared in `package.json`, `go.mod`, `requirements.txt` or `pyproject.toml`, never imported
* **A CVE badge** on the Dependencies section, green when the last cached dependency scan found nothing, otherwise the count and worst severity. It reads the local cache only and never goes to the network on its own. See [Dependents Table](/features/dependents-table)
* **Issues** - every blocker and warning in one list
* **TODOs** - grouped by type
* **A file tree** you can click through
* **Trends** - the score delta plus your three most improved and three most regressed files

<Note>
  The free review omits unused packages, dependency conclusions and trends. Those answers depend on a current scan, and reporting them from a snapshot taken weeks earlier would state something no longer true. **Refresh With Pro** replaces the rescan button, and the saved evidence stays viewable and clickable.
</Note>

<Tip>
  Results are cached, so you can leave the Workspace tab and come back without scanning again.
</Tip>

## Just one folder

Right-click any folder in the Explorer and pick **Iris Code: Analyse This Folder**. Or hit **Scan Current Folder** in the Folder tab to scan whatever the open file lives in.

The **Folder** tab shows the same stats, chart, rankings and tree as the workspace, with its own Rescan and Clear.

<Note>
  One full project review is free without an account. Rescanning and folder scans are Pro. File reviews and click-to-open stay free forever.
</Note>

## Issues and TODOs

Both tabs fill from your most recent scan, whether that was a folder or the whole workspace. A label at the top tells you which ("Showing: folder · src"), with one click back to workspace-wide, so you're never reading folder results thinking they're the whole project.

Each row gives you a severity dot, the file and line, and what's wrong. Click it to land there.

The Issues badge shows errors in red, or the total when there are none. The TODOs badge counts everything. Findings stay put until you rescan or clear.

## Trends

After each workspace scan, Iris Code saves one score per file for that day. Over a few weeks that's the difference between "I think it's getting better" and knowing.

**In a file**, you get a ↑ or ↓ next to the score against the last snapshot.

**In the workspace**, the overall delta plus your three most improved and three most regressed files.

How it works:

* One snapshot per day. Scan five times today and you update today's, rather than creating five
* They live in `.iris-snapshots/` at your project root
* That folder is added to `.gitignore` for you, because trends are yours and shouldn't be committed
* Delete the folder to start over

<Tip>
  Free keeps 2 rolling snapshots, so about two days. Pro keeps them all, which is what you need for week-over-week or month-over-month.
</Tip>

## Exporting it

Turn the current analysis into a single dark-themed HTML file you can send someone, attach to a PR, or keep.

<Steps>
  <Step title="Run a scan">
    File, folder or workspace. There has to be something to export.
  </Step>

  <Step title="Run the command">
    **Iris Code: Export Scan Report as HTML** from the command palette.
  </Step>

  <Step title="Pick where it goes">
    Defaults to `iris-report.html` in your project root.
  </Step>

  <Step title="Look at it">
    **Open in Browser** on the confirmation.
  </Step>
</Steps>

The file is self-contained. No assets, no internet, no build step; it opens on any machine you send it to. It includes only the scans you actually ran.

From the terminal:

```bash theme={null}
iris report
```

Writes `iris-report.html` to the current directory. `--output <path>` puts it elsewhere, and you can pass a directory to scan.

<Note>
  Export is free on every plan. It's a snapshot, so rerun the scan and export again for fresh numbers.
</Note>