Repository navigation
RepoDNA v1.4.3 improves local-first analysis reliability, desktop startup,
release integrity, and secure export workflows.
Highlights
-
Export all currently filtered Findings to spreadsheet-safe CSV, including matching results beyond the visible page.
-
Added a What's New sidebar page and an offline first-launch announcement on
installation or update, with notes for the installed version. -
Opened the Windows desktop in a smaller centered, resizable default window
instead of occupying nearly the full display. -
Added Files explorer filters for generated, vendored, binary, skipped, and
ordinary files. -
Improved local-first browser analysis reliability, including WebAssembly engine
discovery, progress events, worker callback handling and export filenames. -
Strengthened package publication gates and Windows installer validation with
safer npm staging, version checks, and checksum/inventory verification.
Added
-
A What's New section in the sidebar showing the current version's highlights
from the bundled changelog, with a once-per-version first-launch announcement after
installing or updating RepoDNA. The announcement works offline and remains dismissible. -
Filter the Files explorer by generated, vendored, binary, skipped, or ordinary file
state, alongside its existing category, language, and path search filters. -
Export currently filtered Findings as CSV with inline save-error reporting.
Security
-
Escape formula-like CSV fields even when whitespace or control characters precede the
formula, protecting exported tables from spreadsheet evaluation. -
Check Windows-invalid ZIP filenames in the Windows portable CLI smoke verifier as
well as the WinGet manifest generator, with negative-case regression tests on CI. -
Reject Windows-forbidden characters and reserved COM/LPT device names, including
superscript-digit variants, when validating portable CLI ZIP archives for WinGet. -
Require advisory, source, license, and dependency-ban checks for both the workspace and
desktop dependency trees before release jobs publish GitHub packages, npm packages,
container images, or release installers.
Fixed
-
The desktop app now starts in a smaller, centered, resizable window instead of
occupying nearly the entire screen on common Windows laptop displays. -
Refuse to clear unrelated, nonempty npm package staging directories or the repository
itself; allow repeat builds only for explicitly RepoDNA-owned staging directories. -
Preserve the original display order of highlighted findings when imported artifacts
contain duplicate finding identifiers. -
Recover from temporary browser database opening failures and validate saved recent-analysis
pointers so malformed session state cannot disrupt returning to an analysis. -
Reject malformed or empty successful responses from the local server API instead
of letting invalid JSON cause misleading downstream interface failures. -
Remove empty or repeated
?token=parameters from local web interface URLs,
while retaining valid tokens for the current tab. -
Make browser-exported analysis filenames portable and predictable: normalize accented
repository names, limit the filename length, and use a safe date fallback when metadata
contains an invalid date.
Maintenance
-
Verify the complete Windows CLI, desktop installers and WinGet manifest inventory
before publication; run the same check in unpublished release trials. -
Require installers and WinGet manifest validation before npm and container image
publication; wait for all published packages and images before creating the GitHub
release, reducing the risk of a partial release. -
Run the cross-platform CI matrix once per pull request rather than again for
every feature-branch push, while preserving automatic checks onmainand
manual workflow dispatch for standalone branches. -
Lock Razorpay donations to the single official link,
https://razorpay.me/@SanskarCodes, across the website, project documentation,
and GitHub Sponsors configuration. Run an automated audit and regression tests in CI
to reject alternate, insecure, or outdated destinations.
Downloads
repodna-1.4.3-<target>: therepodnacommand line, with the web interface of
repodna servebuilt in. The Linux builds are static and run on any distribution.repodna-1.4.3-wasm32-wasip1.zip: RepoDNA's analysis, reports, and cards as
WebAssembly, the program the web version runs, for WASI runtimes:
wasmtime run --dir .::/my-project repodna.wasm analyze /my-project(without Git
history).RepoDNA_1.4.3_amd64.deb,RepoDNA-1.4.3-1.x86_64.rpm,
RepoDNA_1.4.3_universal.dmg,RepoDNA_1.4.3_x64_en-US.msi,
RepoDNA_1.4.3_x64-setup.exe, and for Windows on Arm
RepoDNA_1.4.3_arm64_en-US.msiandRepoDNA_1.4.3_arm64-setup.exe: the
desktop app.ghcr.io/sanskarin/repodna:1.4.3: a container image with the command line and
Git, for CI jobs:docker run --rm -v "$PWD:/work" ghcr.io/sanskarin/repodna analyze .ghcr.io/sanskarin/repodna-web:1.4.3: the web interface, served on port 8080, for
your own network:docker run --rm -p 8080:8080 ghcr.io/sanskarin/repodna-web- npm packages on npmjs.com and GitHub Packages:
npm install --global @sanskarin/repodna
installs the command line, with one package per platform;
npx @sanskarin/repodna-webruns the web interface on this machine;
npx @sanskarin/repodna-wasm analyze .analyzes with the WebAssembly program, on any
system Node.js runs on, and runs it in browsers too;
@sanskarin/repodna-schemaand@sanskarin/repodna-visualizationare the TypeScript
libraries. repodna-1.4.3-winget-manifests.zip: WinGet community manifests for
the Windows desktop app (Sanskar.RepoDNA) and CLI (Sanskar.RepoDNA.CLI).
After Microsoft accepts the manifests, install and upgrade throughwinget.SHA256SUMS.txt: checksums of every file.- Web version: https://sanskarin.github.io/RepoDNA/ — analyze a folder or an archive, or open analyses and the demo, in your browser: nothing to install, nothing uploaded.
The binaries are not code-signed, so macOS and Windows ask for confirmation the first time they start; see the installation guide.
More open-source projects by Sanskar, the creator of RepoDNA: https://sanskarin.github.io