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

# Project Analytics

> Measure how findings, remediations, and team activity change security posture over time

<Warning>
  Project Analytics is coming soon. This interface is a preview.
</Warning>

# Turn security work into a measurable trajectory

Project Analytics combines AI tools, static analyzers, agents, and human auditors in one view, then tracks how the project responds to their findings.

<Frame caption="Project analytics showing the analysis network, active members, and findings history">
  <img src="https://mintcdn.com/bevor/LWyeXr6VX5AMQEQw/images/project-analytics.png?fit=max&auto=format&n=LWyeXr6VX5AMQEQw&q=85&s=c2bd13e1f5ae78b3fe14d6f0189c0ba6" alt="Bevor Project Analytics dashboard with analysis network, active members, and findings history charts" width="1337" height="676" data-path="images/project-analytics.png" />
</Frame>

## Read the dashboard

* **Analysis network:** Security work across code versions and branches.
* **Active members:** Validation and remediation by people and systems.
* **Findings history:** Discovered risk becoming verified remediation.

## The shape of good security posture

A stronger security program may surface more findings at first. That means previously unknown risk is becoming visible.

1. **Surface broadly:** Apply overlapping models, analyzers, agents, and human review.
2. **Validate:** Remove duplicates and false positives; identify real risk.
3. **Remediate and verify:** Open validated findings trend toward zero while verified remediations trend upward.

<Info>
  Zero findings from one tool is not the same as zero risk. Confidence comes from diverse analysis, independent validation, and evidence that confirmed issues were remediated.
</Info>

The graph keeps discovery, validation, remediation, and verification together, making stalled work and under-reviewed branches visible.