FAQ & TROUBLESHOOTING
Short answers to the questions support hears most. If yours is not here, email support@vibe-eval.com or use the chat widget in the app.
Where to look first
- Scan status help — hover the status badge on any scan for a one-line explanation. Definitions are listed under Running scans.
- On-call review note — the card at the top of a completed scan says what the reviewer confirmed and what was out of scope.
- Report inaccuracy — on the scan header; the fastest way to get a detection issue in front of the team.
Common situations
Findings look preliminary
While a scan is in review, findings carry a Preliminary badge and may change. Wait for the review email before filing tickets. See Findings.
The scan tested fewer pages than expected
Give the crawler a Sitemap URL in the Target step, raise Crawl depth in Options, widen Scan scope to the whole domain or subdomains, and make sure Excluded paths is not too broad. Pages behind login need Authentication set.
An API is missing from the results
Use the API Scan profile and supply an OpenAPI/Swagger URL, or add the base path to the target. GraphQL endpoints are discovered from the app’s network traffic; an endpoint the frontend never calls will not be found without a spec.
I want to hide a finding I have accepted
Use Ignore to hide it in your own browser, or set the status to False positive to exclude it for the whole team and from the risk score.
A teammate cannot see the organization
Check Team for their status: Pending means the activation link has not been used; Deactivated means access was revoked. Roles change on next login. See Team and roles.
Contact
Email support@vibe-eval.com or open the chat widget in the bottom-right corner of the app. Sales and enterprise questions: contact sales.
COMMON QUESTIONS
SEE IT ON YOUR OWN APP
Docs explain the product. A scan shows you what it finds on your deployed URL — keys, RLS, auth, and API gaps in under 60 seconds.
14-day free trial · No credit card · Cancel anytime