Guides
Understand findings
Severities, statuses, and how Vibefilo keeps results free of duplicates.
A finding is one issue your agent found: a rule, a severity, a location and a short masked snippet. Findings belong to a project and update across runs.
Severities
| Severity | Meaning |
|---|---|
| Blocker | Fix before you launch. Data exposure or a broken security boundary. |
| High | A serious weakness that is likely to be exploited or to breach the law. |
| Medium | A real gap with a smaller impact or harder path. |
| Low | A hardening step or a minor gap. |
| Info | A note worth knowing. No action required. |
Every severity is shown with an icon and a label, never by colour alone.
Statuses
- open
- Found and not fixed yet.
- fix_in_progress
- Your agent is working on it.
- fixed
- A fix was made and is waiting for a re-check.
- verified
- A re-check confirmed the fix.
- reopened
- A later check found the problem again.
- accepted
- You chose to accept the risk.
No duplicates
Each finding has a fingerprint built from the rule, the file and the normalized evidence. Submitting it again updates the existing finding instead of creating a new one, so resubmitting a run is safe.
Where to see them
- Projects: one card per app with the latest run and open findings by severity.
- A project page: its runs and findings, with filters for severity and status.
- Findings: every finding across your organization, updating live.