gitvisualise v1.2.0

gitvisualise 1.2.0

More languages, two new views beyond imports, a redesigned website, and tooling for teams.

Highlights

• Five new languages, plus Kotlin. C#, Ruby, PHP, C/C++ and Dart import graphs, and Kotlin (the project's first community contribution, thanks @Voyagerroc-Lab). Each resolves only to files that exist, and reports a package only when a manifest declares it.
• Infrastructure and data-model views. Docker Compose services (dependencies, start order, the code each is built from) and SQL / Prisma tables with foreign keys, each pointing at the file and line it came from.
• A redesigned website. A real product frame, a gallery of real tours, an Export menu (download, Mermaid, PlantUML, README badge), and the analysis runs in a Web Worker so large repositories no longer freeze the page.
• Pull request architecture diffs. The GitHub Action can comment how a change affects the architecture (comment-diff: true, off by default).
• VS Code extension (0.1). Open the tour beside your code and jump from any component to its file and line. Analyses locally and writes nothing into your workspace.
• Optional AI narration (experimental, off by default). With your own API key; only structured facts are sent, never source code, and the result is checked before it is used. Tested against a fake provider, not yet the live API.
• Viewer. Collapsible swimlanes, screen reader announcements, arrow-key navigation between components, and a skip link.
• CLI. gitvisualise watch and gitvisualise export --format mermaid|plantuml.
• Tests and docs. A real-browser smoke test, a language plug-in interface, a publishing guide and a public roadmap.

Full details in the CHANGELOG. The roadmap lists 18 open issues if you want to help.

Open the website

gitvisualise v1.1.0

gitvisualise 1.1.0

The biggest update since launch: more languages, monorepos, request tracing and a way to see what changed between two revisions.

Highlights

• Compare two revisions. owner/repo@v1...v2 marks components and relationships added (green), removed (red) or changed (amber) and narrates the difference. The CLI has gitvisualise diff <older> <newer>.
• Request tracing. A fetch or axios call is linked to the server route that handles it, only on an exact method and path match, with evidence on both sides and a "Request: GET /x" tour.
• Monorepos. One component per workspace package, or analyse a single folder with --path, owner/repo:folder or a /tree/<ref>/<folder> link.
• Java and Rust import graphs, Go workspaces, and tsconfig/jsconfig/Vite/webpack path aliases.
• Viewer and website. Light/dark theme, component search, SVG/PNG export, swimlanes, deep links to any step, a paginated repository picker and a per-commit IndexedDB cache.
• Optional "Sign in with GitHub", off by default. It needs a small token-exchange function that a maintainer deploys; see server/github-oauth.

Also: Python imports now follow Python 3 semantics, and cached tours are versioned so a release never shows stale results. Full details in the CHANGELOG.

Open the website

gitvisualise v1.0.1

gitvisualise 1.0.1

Fixed

• Website: the tour could appear blank after analysing a repository, leaving only the toolbar. The sandboxed player frame is now created fresh for every tour, inside the already visible results view. A regression test guards against reintroducing the problem.

If you saw a blank tour on 1.0.0, reload the page: no action is needed on your side.

Open the website · CHANGELOG

gitvisualise v1.0.0

gitvisualise 1.0.0

Paste a GitHub link, get an interactive, narrated architecture tour of the repository. Free, open source, and it runs in your browser: no sign-up, no server, no API keys.

Try it

kaushik2210.github.io/gitVisualise

What is in this release

• Website. Paste github.com/owner/repo, or pick a repository from an account. The analysis runs entirely in your browser and the tour plays in a sandboxed frame. Deep links (#/owner/repo), optional tokens for private repositories, and downloadable output (single HTML file or JSON).
• GitHub Action. Regenerate a repository's tour on every push and publish it to GitHub Pages. See the README for a ready-to-copy workflow.
• Claude Code skill. Ask Claude Code to "generate an interactive architecture for this project" and get curated narration written from your actual code, validated against the real files.
• Command line. scan, generate, validate, build, all, serve for local folders and GitHub URLs. Zero dependencies, Node 18+.
• Grounded by construction. Every component and connection links to real files and lines. The validator rejects nonexistent files, out-of-range lines, dangling references and invented paths in narration.
• Regenerate safely. Curated edits survive every re-run.
• Import graphs for JavaScript/TypeScript (JSX, TSX, Vue, Svelte), Python and Go; entry points, routes and dependencies.
• Viewer. Play, pause, step, restart, speed control, voice narration, zoom-to-step camera, keyboard shortcuts, dark mode, phone layout, reduced-motion support and a no-JavaScript fallback.

Contribute

The project is open source under the MIT license and looking for contributors. There are scoped, documented issues for every skill level:
good first issues · help wanted · discussions · CONTRIBUTING.md

See the CHANGELOG for details.