Product and SEO FAQ

Frequently asked questions about Repo Insight X

This page answers the most common questions about supported languages, Git providers, import formats, HTML / PDF reports, and available subscriptions.

Which languages does Repo Insight X support?

Repo Insight X analyzes polyglot codebases and relies on the languages detected in the repository. The examples already present in the project notably cover TypeScript, JavaScript, Python, Go, Java, Terraform, and mixed full-stack structures.

Which Git providers are supported?

You can provide a cloneable URL from GitHub, GitLab, Bitbucket, SourceForge, Azure DevOps, as well as other providers compatible with a standard Git URL.

Can I analyze an archive instead of a Git repository?

Yes. The service also accepts ZIP, TAR, TGZ, TAR.GZ, RAR, and 7Z archives for codebases delivered outside a Git provider or not publicly exposed.

What kind of deliverable do I get after an analysis?

Each analysis produces a structured technical report that can be read in HTML, with a PDF export ready to be shared with a client, prospect, or product team.

Is there a public example of a frontend report?

Yes. A public page shows a real report generated from a small, simple Next.js repository, with an HTML report and a downloadable PDF.

Which subscription plans are available?

The service currently offers a Free plan to discover the platform, a Starter plan for one-off audits, and a Growth plan to industrialize analyses and project history.

What is included in the Free plan?

The Free plan lets you start with 2 analyses per month, 1 active project, and access to the HTML report, without an initial Stripe subscription.

What is included in the Starter plan?

The Starter plan is designed for first client deliverables with 10 analyses per month, 5 active projects, HTML and PDF reports, and standard email support.

What is included in the Growth plan?

The Growth plan targets more regular usage with 50 analyses per month, 20 active projects, full project history, and priority support.

Do I need rights over the code being analyzed?

Yes. The user must confirm they have the necessary rights to analyze the source code, including when it comes from a private repository or a third-party provider.

Can I keep history by client or by project?

Yes. The product keeps history by account, project, and run, which makes comparison, audit follow-up, and long-term reuse easier.

Can I turn a report into GitHub tickets?

Yes. The project workspace can then turn a report into a structured backlog or reusable GitHub issues, depending on your setup.

Need a more concrete answer?

You can open the sample frontend report page to see the level of detail in the deliverables, or create an account to launch your own analysis.