RepoDNA v1.3.0: A Better Way to Explore Repository Analysis
Understanding a codebase is not just about counting files or identifying programming languages.
When entering an unfamiliar project, developers need to understand its architecture, dependency relationships, history, quality signals, and the areas that deserve a closer look. These details are often spread across hundreds of files and many commits.
That is the problem RepoDNA is designed to address.
RepoDNA is an open-source, local-first repository intelligence and code archaeology platform. It turns repository data into architecture maps, historical views, evidence-backed findings, and shareable Project DNA reports.
Today, I'm sharing RepoDNA v1.3.0, released on October 9, 2026.
🔗 Release: https://github.com/sanskarIN/RepoDNA/releases/tag/v1.3.0
What changed in v1.3.0?
This release focuses on making the web interface easier to use in day-to-day development.
1. Resume recent analyses
The web interface keeps a browser-side list of the last five analysis files opened there. You can reopen an analysis from the start page or search without uploading the file.
You can also remove individual entries, clear the list, or disable this feature in Settings.
2. Keep your place after reloading
Reloading the page preserves the current analysis and view. A new tab starts at the start page.
This is a small but useful improvement when exploring a large report or returning to an analysis later.
3. Navigate analysis views more easily
The interface connects related views and panels more clearly. Overview numbers lead to the relevant sections, views link to previous and next destinations, and the [ and ] keys make moving between views more convenient.
A Back to top button also helps on long pages.
4. Explore findings in manageable batches
Findings are displayed 25 at a time, with controls to load more. Filtered findings can be opened through a URL, making specific views easier to revisit or share.
5. Export tables to CSV
Every table now provides a Download CSV option for its complete set of rows.
This allows you to work with the analysis in a spreadsheet or continue processing the exported data. Formula-leading text is handled to reduce the risk of unintended spreadsheet execution.
6. Open analysis files through drag and drop
Drop an analysis file onto the page to open it, including while another analysis is already open. The Compare view also accepts another analysis file for comparison.
7. Run the web interface locally
Version 1.3.0 introduces the @sanskarin/repodna-web npm package.
With Node.js and npm available, you can launch the interface using:
npx @sanskarin/repodna-web
The package starts a small local server at http://127.0.0.1:8080/. It provides the interface for opening analysis files and exploring the demo offline.
The web interface itself does not replace the command-line or desktop application for analyzing your own repository. Use RepoDNA's analysis tools to create the analysis first, then open the resulting file in the interface.
How to get started
Install the command-line tool
With npm:
npm install --global @sanskarin/repodna
repodna --version
Then navigate to a repository and run:
repodna analyze
repodna serve
repodna report
These commands analyze a repository, launch the local web interface, and generate reports, respectively.
You can also download a prebuilt binary or desktop installer from the GitHub releases page.
Try the browser-based demo
Visit the RepoDNA web version to explore the included demo without installing the CLI first.
The web version opens analysis files in your browser; it does not upload those files for processing.
Why local-first matters
Repository analysis can involve source structure, internal naming conventions, dependency details, and contributor history.
RepoDNA is built around a local-first approach, with no telemetry. The web interface's recent-analysis list stays in the browser. Network use by the broader tool depends on the action being performed and the features configured; for example, cloning a Git URL or contacting an explicitly configured AI provider may use the network.
This design keeps control of the analysis with the developer while still supporting useful reports and exports.
More than a list of metrics
RepoDNA can explore repository architecture, dependencies, Git history, code complexity, security signals, test and build setup, and project evolution.
Its goal is not to assign a simplistic grade to a codebase. It is to help developers inspect evidence, understand relationships, and identify what they should investigate next.
Version 1.3.0 makes that exploration more convenient through better navigation, persistent views, recent analyses, exports, and local web usage.
Try RepoDNA
- Source code: https://github.com/sanskarIN/RepoDNA
- v1.3.0 release: https://github.com/sanskarIN/RepoDNA/releases/tag/v1.3.0
- Web version: https://sanskarin.github.io/RepoDNA/
- Changelog: https://github.com/sanskarIN/RepoDNA/blob/main/CHANGELOG.md
RepoDNA is open source, and feedback, bug reports, and contributions are welcome.
If you explore v1.3.0, which view is most useful for your workflow: architecture, Git history, code quality, findings, or dependencies?
Top comments (0)