Analysis Types

## Analysis Types

SyntaxValid supports multiple analysis types to balance coverage, speed, and signal quality.

Each analysis type serves a different purpose and should be chosen based on context.

---

## Full Repository Analysis

Full analysis scans the entire repository.

### Characteristics

- Analyzes all files and dependencies

- Produces a complete risk baseline

- Most comprehensive TrustScore signal

- Takes longer than other analysis types

### When to use

- First-time project setup

- Major refactors or architecture changes

- Periodic baseline checks

- Audit or compliance reviews

Full analysis establishes the reference point for future comparisons.

---

## Diff Analysis

Diff analysis scans only changed files between commits or pull requests.

### Characteristics

- Faster execution

- Focused on incremental changes

- TrustScore reflects change impact

- Lower noise for active development

### When to use

- Pull requests

- Small fixes or refactors

- Fix verification

- Continuous development workflows

Diff analysis is optimized for speed and developer feedback.

---

## Pull Request–Triggered Analysis

Pull request analysis is a form of diff analysis triggered automatically by integrations.

### Characteristics

- Runs automatically on PR events

- Reports results directly in GitHub

- Enforces policies before merge

- Keeps developers in their workflow

### When to use

- Teams using pull requests consistently

- Enforcing merge safety automatically

- Reducing manual review burden

Pull request analysis integrates risk decisions into code review.

---

## Manual vs Automated Runs

### Manual analysis

- Triggered from the dashboard

- Useful for investigation and verification

- Gives explicit control over scope

### Automated analysis

- Triggered by integrations (GitHub, CI)

- Ensures consistent enforcement

- Scales across teams and repositories

Both modes use the same deterministic engine.

---

## Choosing the right analysis type

| Situation | Recommended Analysis |

|---------|---------------------|

| First project scan | Full analysis |

| Pull request | Diff / PR analysis |

| Fix verification | Diff analysis |

| Compliance review | Full analysis |

| Day-to-day development | Diff analysis |

Choosing the right type improves accuracy and efficiency.

---

## Key principles

- Analysis type affects scope, not correctness

- Deterministic rules apply in all cases

- Policies are enforced consistently

- TrustScore always reflects verified results

---

## Next reference pages

- Severity levels reference

- TrustScore factors

- Limits and quotas