# Local inspection

Refresh information about your code and fix missing or inaccessible folders.

## What inspection shows

Orbit inspects linked folders to check whether they are available and read information about their Git repository and packages. The overview can show the latest known commit, its branch, and when and where Orbit found it. This information reflects the last scan; it does not update with every file edit.

A folder's availability tells you whether Orbit can access its saved path. Scan states such as Queued, Scanning, Current, or an error describe inspection progress. A missing folder does not mean Orbit deleted it: the path may have moved, a drive may be disconnected, or access may be unavailable.

## Refresh a folder

1. Open **Sources**.
2. Find the folder and open its menu.
3. Select **Rescan folder**.
4. Wait for the queued scan to complete, then review its state.

Orbit can schedule a new scan when you open a project whose saved information is out of date. Keep the desktop app running while the scan finishes. Local folder scans and remote repository activity have separate refresh controls: rescanning a folder does not refresh GitHub or GitLab activity.

## Repair missing or failed scans

If a folder is unavailable, reconnect the drive or use **Change folder location** to point to the current checkout. Rescan after fixing access.

If a scan cannot finish, review the displayed error and retry. Orbit may show the last successful scan while the new scan is failing; its timestamp matters. An interrupted scan can be retried from the folder menu.

## Inspect dependencies

Package files are organised into locations within a linked folder. Open **Dependencies → Manage locations** to add a subdirectory that contains package files, such as `apps/web` in a monorepo. Local inspection and online security/update checks are different steps. Follow [dependency checks](/guide/sources/dependency-checks/) to review package findings.