GitHub Repository to Diagram

Rekhic can inspect public GitHub repositories and generate an architecture diagram directly from a repository URL, without requiring you to clone the code locally or connect your GitHub account.

The Workflow

text Copy
       Public GitHub Repository URL
  (e.g. https://github.com/owner/repo)
                   │
                   ▼
       Public GitHub API Fetch
     (Fetches file tree & manifests)
                   │
                   ▼
      Local Architecture Analysis
   (Detects services, dependencies & DBs)
                   │
                   ▼
          Architecture Preview
                   │
                   ▼
             Rekhic Canvas

1. Navigate to Generators -> GitHub Repo (/import/github).
2. Paste any public GitHub repository URL (e.g. https://github.com/octocat/Hello-World or https://github.com/facebook/react).
3. Click Analyze Repository.
4. Rekhic fetches the repository tree using the public GitHub REST API directly to your browser.
5. Review the detected technologies, services, and relationships in the Architecture Preview.
6. Click Open in Canvas to start editing the generated diagram.

Key Operating Rules

1. Public Repositories Only

Important: Rekhic currently supports public GitHub repositories only.

Private repositories are not supported. Rekhic does not request, store, or require GitHub personal access tokens, SSH keys, or OAuth credentials.

2. GitHub API Rate Limits

To remain lightweight and avoid server-side credentials, Rekhic calls GitHub's public API directly from your browser:

• GitHub limits unauthenticated requests to 60 requests per hour per IP address.
• If you analyze dozens of repositories in a short window, GitHub may return an HTTP 403 Rate Limit error.
• If you hit this limit, simply wait for your hourly rate-limit window to reset, or analyze downloaded files using Code to Diagram.

3. File Filtering & Performance Protection

To maintain high performance and prevent browser memory overload when inspecting large projects:

• Rekhic fetches the repository tree and selects only architectural configuration files (e.g. package.json, pom.xml, docker-compose.yml, README.md, go.mod).
• Ignored Directories: Vendor, build, and generated directories are automatically filtered out:
  • node_modules/, vendor/, .git/
  • dist/, build/, out/, target/
  • .next/, coverage/, .cache/
• For monorepos or multi-module repositories, Rekhic prioritizes root and top-level package manifests.

Next: Learn what Rekhic attempts to detect in Architecture Analysis.