RepoDNA v1.3.1: Analyze a Codebase in Your Browser—Without Uploading It
RepoDNA v1.3.1: Analyze a Codebase in Your Browser—Without Uploading It Understanding an unfamiliar codebase often means answering the same questions from scratch: How is the project organized? Which modules and packages depend on one another? What has changed over time? Which files are hotspots? How is the project built and tested? Which findings have evidence behind them? RepoDNA is an…
RepoDNA v1.3.1: Analyze a Codebase in Your Browser—Without Uploading It
Understanding a new codebase typically involves answering questions from scratch. RepoDNA is an open-source, local-first tool that helps with these inquiries. It creates architecture maps, histories, quality metrics, reports, comparisons, and onboarding guides. Findings can be traced back to files, lines, commits, or measurements, enabling developers to examine the evidence.
RepoDNA v1.3.1 introduces a new browser-based analysis feature. Users can open the web version, select a folder or archive, and let WebAssembly perform the analysis directly in the browser. This eliminates the need for a native CLI installation and prevents project files from being uploaded.
The browser interface can generate HTML and Markdown reports and Project DNA cards, which can be downloaded as SVG or PNG. The browser continues working offline after the web version loads. However, it cannot access the repository's Git history, so historical analysis requires the command line or desktop app.
Version 1.3.1 also adds a WebAssembly package (@sanskarin/repodna-wasm) that delivers analysis, reports, and cards to Node.js and browsers. Users can run the analysis with a command like npx @sanskarin/repodna-wasm analyze . GitHub Actions are available to display summaries, annotate findings, keep the analysis, write reports, compare with baselines, and set failure thresholds based on severity. The action runs on the runner without uploading the source to a RepoDNA service.
Windows on Arm now has CLI and desktop app builds. Desktop saving improvements include separate full-report folders by analysis and the ability to save Project DNA cards in the selected theme. The GitHub Action is listed in the GitHub Marketplace, and documentation includes inputs, outputs, and workflow examples.
The analysis is evidence-first and describes a project without assigning a grade. It is lexical rather than compiler-level and labels missing data rather than treating it as zero. Feedback is welcomed on how to make repositories easier to understand and which views are most useful for day-to-day maintenance.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
