RepoDNA v1.2.2

RepoDNA v1.2.2: A Small Follow-Up for Better Mobile Tables and npm Releases

RepoDNA v1.2.2 is now available.

This release is intentionally small. Instead of introducing another large subsystem, it focuses on two practical improvements that make the existing project more predictable:

• better feedback when scrolling wide tables on phones
• safer npm publishing when releases are published out of chronological order

These changes build directly on the work in RepoDNA v1.2.1.

From v1.2.1 to v1.2.2

RepoDNA v1.2.1 focused heavily on usability and distribution.

It introduced normal npmjs.com installation without requiring a GitHub token, restored the Project DNA card in repodna serve, improved accessibility in the web interface and generated reports, improved long paths and tables on phones, clarified Git clone failures, and made recent-history calculations more accurate.

v1.2.2 keeps that direction.

It is less about adding another headline feature and more about removing two remaining sources of friction.

Better table scrolling on phones

RepoDNA's web interface contains tables that can become wider than a phone screen.

When that happens, the interface indicates that more content is available horizontally by shading the edge of the scrollable area.

The previous implementation used a gradient that became weaker toward the top and bottom of a long table.

That meant the first rows of a long table could show almost no visible indication that more content existed outside the viewport.

v1.2.2 changes the shading so the indication remains consistent across the entire edge.

It is a small visual change, but it improves discoverability without adding another control or changing the underlying table behavior.

More predictable npm releases

The second change is in the release workflow.

RepoDNA publishes packages to npmjs.com as well as GitHub Packages.

That creates an interesting release-management case: sometimes an older version needs to be published after a newer version is already available.

For example, v1.2.0 was ready as an actual release but could not simply become npm's latest version after v1.2.1 had already been published.

The v1.2.2 publishing logic now checks whether a release is older than the registry's current latest version.

When it is older, the package is published using the previous tag.

That means:

latest continues to represent the newest release.

previous can represent an older release that still needs to exist on the registry.

This is a small piece of release infrastructure, but it makes distribution much more predictable.

RepoDNA is still the same project

These changes do not alter RepoDNA's central design.

RepoDNA remains an open-source, local-first repository intelligence and code archaeology platform.

It can analyze repository structure, languages, architecture, dependencies, Git history, ownership, change hotspots, historical evolution, complexity, security signals, tests, build systems, documentation, and more.

The project is designed around a versioned RepositoryDNA artifact that can be used by the CLI, reports, cards, comparisons, web interface, desktop application, and optional AI explanations.

The important principle remains evidence.

Instead of presenting an unexplained score, RepoDNA is designed to connect findings to files, lines, commits, and measurements.

Try RepoDNA

Install the current release from npm:

npm install --global @sanskarin/repodna@1.2.2

Or explore the project without installing anything:

https://sanskarin.github.io/RepoDNA/

The source code is available here:

https://github.com/sanskarIN/RepoDNA

The v1.2.2 release page contains the current downloads and release information:

https://github.com/sanskarIN/RepoDNA/releases/tag/v1.2.2

The screenshot gallery is also maintained by release, making it possible to compare the interface across RepoDNA's versions.

Final thoughts

Not every useful release needs to be a major feature release.

Sometimes a project gets better by fixing the things that users notice only when they go wrong:

a visual hint that disappears on a long table,

or a package tag that behaves unexpectedly when releases arrive out of order.

RepoDNA v1.2.2 is one of those releases.

A small step, but in the same direction.

Understand your codebase. See its DNA.