Getting Started

Analyze a GitHub or GitLab repository to explore its structure, file dependencies and detected security findings. Analysis time and coverage depend on the repository.

Quickstart

1

Go to the Analyzer

Navigate to Xolvyn.dev or open the dashboard after logging in.
2

Paste a Repository URL

Enter a GitHub or GitLab URL in the format:
https://github.com/owner/repo or https://gitlab.com/owner/repo
3

Click Analyze

Xolvyn will clone the repo (shallow, depth 1), parse the AST, build a dependency graph, run security + style audits, and return interactive results.
Tip
Start with a public repository such as https://github.com/expressjs/express — sign in to open its workspace and save your analysis history.

Authentication

Xolvyn uses OAuth-based authentication through Auth.js. You can sign in using your GitHub or GitLab account — no separate password required.

Supported Providers

ProviderScopes RequestedWhat It Enables
GitHubrepoPrivate repo access, profile info
GitLabapiPrivate repo access, profile info

How It Works

1

Click 'Continue with GitHub' or 'Continue with GitLab'

You'll be redirected to the provider's authorization page.
2

Authorize the Application

Grant Xolvyn permission to read your repositories. This generates an OAuth token.
3

Token is Stored Securely

Provider credentials are stored server-side for authorized repository workflows. Review the requested scopes before granting access.
Note
If you sign in with both GitHub and GitLab using the same email, your accounts are automatically linked into a single identity. Account linking and access depend on the configured sign-in flow.

Private Repositories

Analyzing private repositories requires authentication. When you log in via GitHub or GitLab, Xolvyn stores your OAuth token and uses it to authenticate git clone operations.

How Private Cloning Works

Private cloning uses authorized provider credentials supplied to the server-side clone operation. The examples below omit credentials:

text
# Public repo (no token needed)
git clone --depth 1 https://github.com/owner/repo

# Private repo (authorized credentials supplied separately)
git clone --depth 1 https://github.com/owner/private-repo
Tip
Sign-in credentials can be stored server-side for subsequent repository access. Repository analysis itself uses a temporary server-side clone.

Data Handling

Temporary Clone

Cleanup is attempted after analysis

Provider Handling

Review AI provider retention before connecting private code

Saved Metadata

Saved analysis reports exclude source snippets

Shallow Clone

Only the latest commit is cloned (--depth 1)

Dependency Graph

The dependency graph maps resolved imports between supported source files. It is a structural view of the analyzed revision, not a call graph or runtime trace.

Node Colors (Layers)

ColorLayerExample
Cyanapiapi/user/route.ts
Tealmiddlewaremiddleware.ts
Violetserviceauth.service.ts
Pinkcorecore/engine.ts
Pale greenmodelmodels/user.ts
Light neutralconfigconfig.ts
Stoneutilutils/format.ts
Graytestauth.test.ts

Interactions

Click any node to inspect it in the Auditor Panel. Use the minimap to navigate large graphs. Toggle fullscreen mode with the expand button. Zoom and pan are fully supported via mouse or trackpad.

Security Audit

Available checks analyze supported files and dependencies. Review which checks completed; no findings does not mean the repository is secure.

What We Scan For

CategoryExamplesSeverity
Hardcoded SecretsAPI keys, tokens, passwords in sourceCritical
Unsafe Functionseval(), innerHTML, dangerouslySetInnerHTMLHigh
Injection VectorsSQL injection, XSS, command injectionHigh
Missing ValidationUnvalidated user inputs in handlersMedium
Style Violationsconsole.log in production, TODO/FIXMELow

Scoring

The analysis displays a grade and a score alongside the assessed maximum. The score reflects completed checks; it is not a security certification.

GradeScore RangeMeaning
A80 – 100Excellent — few or no issues found
B60 – 79Good — some warnings to address
C40 – 59Fair — notable security concerns
D0 – 39Poor — critical issues need attention

AI Mentor (@mentor)

The @mentor is an AI assistant using repository analysis as context. Its answers are interpretations; check important claims against the linked files.

How to Use

1

Run an Analysis

The @mentor becomes available after your dependency graph is generated.
2

Click "Ask @mentor"

Opens the chat panel overlaid on your architecture map.
3

Ask Questions in Natural Language

The mentor uses your graph as context. Ask it to separate computed facts, interpretations and unknowns.

Example Prompts

In the workspace file reader, Explain from source is a separate, optional action. Choose an excerpt, review the source-sharing notice, then explicitly send it to Google Gemini. It uses the same message limits and AI-credit rules as @mentor. Source is not added to chat history or saved by Xolvyn. Generated interpretations and your corrections remain in tab memory until reload and can be included in an explicit area-brief export. Citation ranges are checked, not the reasoning; confirm provider-retention terms before sharing private code.

"Where is the authentication logic and how does it connect to the API routes?"
"What are the most critical files in this codebase?"
"Which files import the authentication module? Cite the import relationships."
"Which modules would be affected if I refactor auth.service.ts?"
"Are there any circular dependencies?"

PR Impact Analysis

PR impact views highlight changed files and their import dependents. Review these as potential structural impact, not a prediction that execution will fail.

Status Labels

StatusColorMeaning
modified🟠 OrangeThis file is directly changed in the PR
impacted🔴 RedThis file imports a changed file, directly or transitively
safe🟢 GreenNo resolved import path connects it to changed files; runtime safety is not established
Note
PR Impact is currently a simulation mode on the web app. Full git-diff-based impact analysis is planned for the VS Code extension.

VS Code Extension

A VS Code extension is in development and will ship with Pro.

API Reference

Xolvyn exposes a single REST endpoint for programmatic analysis.

POST /api/analyze

Analyzes a GitHub or GitLab repository and returns a dependency graph plus an audit report.

bash
curl -X POST https://your-domain.com/api/analyze \
  -H "Content-Type: application/json" \
  -d '{"repo_url": "https://github.com/expressjs/express"}'

Request Body

FieldTypeRequiredDescription
repo_urlstringYesFull GitHub or GitLab repository URL
github_urlstringNoLegacy alias for repo_url (backwards compatible)

Response

json
{
  "dependency_graph": {
    "nodes": [{ "id": "src/app.ts", "layer": "core" }],
    "edges": [{ "from": "src/app.ts", "to": "src/routes.ts" }],
    "stats": { "total_modules": 47 }
  },
  "audit_report": {
    "summary": {
      "score": 82,
      "grade": "A",
      "total_files": 47,
      "security_issues": 2,
      "style_violations": 5,
      "scan_duration": "1.2s"
    }
  },
  "persisted": true
}

Error Codes

StatusMeaning
400Invalid URL format
402Insufficient credits
403Private repo — login required
404Repository not found
413Repository exceeds the current analysis limits
429Rate limit exceeded
504GitHub/GitLab API timeout

Credits & Billing

Xolvyn uses a credit-based system. Each analysis costs 1 credit.

Credit Allocation

Check the pricing page for current plan allowances and your dashboard for available credits. Limits differ by plan and analysis type.

Note
The analysis API accepts public repositories anonymously, but opening the workspace currently requires sign-in. Anonymous results are not saved to account history.

How Credits Are Deducted

1 credit is deducted after a successful analysis. If the analysis fails (e.g., timeout, clone error), no credit is deducted. You can view your balance on the Dashboard.

FAQ

What languages does Xolvyn support?

Xolvyn parses import/export statements and works best with JavaScript, TypeScript, Python, Go, and Java. The security scanner covers all text-based source files.

Is there a repo size limit?

Repository size and file-count limits apply. An analysis can be rejected or limited when it exceeds them; check the current limits before scanning a large repository.

Does Xolvyn store my source code?

Analysis uses a temporary server-side clone, with cleanup attempted afterward. Signed-in history saves analysis metadata with source snippets stripped from reports. Review data handling before connecting private code.

Can I self-host Xolvyn?

Self-hosting availability is not established by this documentation. Contact Xolvyn to discuss deployment requirements; the standard analysis flow uses a temporary server-side clone.

Can I use both GitHub and GitLab?

Yes! You can log in with either provider. If both accounts share the same email, they are automatically linked into a single identity with shared credits.

How do I get more credits?

Upgrade to the Pro plan on the Pricing page, or contact us for an Enterprise plan with unlimited analyses.

Still have questions?

We're here to help. Reach out to our team or try the product for free.

Xolvyn — Codebase understanding and security analysis