Getting started
User guide
The recommended path from a registered URL to a measurable improvement cycle.
- 01
Register the project and repository
In Projects, enter a name and public URL; then connect GitHub or GitLab under Action plans → Connections.
- Use a URL you manage or are authorized to test.
- Confirm the website is accessible without a private session.
- Connect a repository you are authorized to inspect. A GitHub or GitLab connection is currently required before running a diagnostic.
- 02
Run a diagnostic
In Diagnostics, choose the project and verification type.
- Product Quality Diagnostic covers UI/UX, performance, SEO, accessibility, console and network.
- Passive Security Diagnostic checks TLS/certificates, DNS, HTTP headers, cookies, CORS, exposed files, HTTP methods and client-library versions. It does not send attack payloads or replace a penetration test.
- Wait for completion before comparing scores or creating an action plan.
- 03
Review findings
Open the report and assess priority, evidence and context.
- Scores show trends; they do not replace reviewing each finding.
- Filter issues by category, severity and status.
- Review AI recommendations before applying them in production.
- 04
Create an action plan
Convert the completed diagnostic into a prioritized remediation checklist.
- Download the PDF plan for manual execution.
- Use the universal bridge or MCP with your development tool.
- When using GitHub or GitLab, review the branch and pull/merge request before approving any merge.
- 05
Reanalyze and track
Measure the outcome of changes and continue the cycle.
- Reanalyze the project after applying items to get a fresh score.
- Check the project page to compare completed and pending plan items with the latest diagnostic.
- This comparison is calculated from the project records; it is not a separate execution mode.