Product · Health

See what needs attention, and why.

Health grades what it finds and shows the evidence for each finding, so you can check it rather than trust it.

Housekeeping, not alarms.

Most findings in the sample workspace are routine, such as a branch with no upstream or a repository with no remote. They are labelled “worth a look”. Informational results are not presented as problems, and nothing here is a security finding.

  1. Read the totals

    Counts of files measured and projects scanned come first.

  2. Filter by severity

    Use the severity filters to narrow the list to what you care about.

  3. Open the evidence

    Each finding states what was observed, such as “git status shows no upstream for this branch”.

  4. Go to the project

    Jump from a finding to the project, its Map or its Storage.

DevMap Health: counts of files measured and projects scanned, severity filters, and per-project findings such as Branch has no upstream with the evidence git status shows no upstream for this branch.

What you get

Practical benefits

Sorted by what to look at first

Findings are ordered so the ones that matter most for a project come first.

Evidence you can verify

Each finding records what was observed, so it can be checked against the repository.

Scoped to what DevMap can see

Findings come from git state and project files on your Mac.

When it helps

Before you push or hand a project over.

A quick pass shows which repositories have no remote, which branches have no upstream and which projects have not been touched recently.

Screenshot