r/devtools • • 17d ago

I’m building an open-source 3D codebase visualization tool for local code analysis

I’m the author of Ephemora Skyline, an open-source 3D codebase visualization tool for local code analysis.What does it do? It turns a local codebase into a 3D city: folders become districts, files become buildings, complexity changes the shape, and security findings point back to evidence in the source.The current main-branch update focuses on trustworthy project understanding:

•Python def and async def declarations are now detected as functions.

•Files inside tool folders are counted instead of silently disappearing from project totals.

•The published package now includes its README, changelog, privacy statement and guides.

•A package check verifies that installed documentation links resolve.

•The running city also received measured improvements to arrival framing, residents, vehicles and accessible teaching boards.

The project is local-first and open source. It is not intended to replace CodeQL, CodeScene or enterprise code-search platforms. The narrower goal is to make software architecture, complexity and security findings easier to orient around before reading the source line by line.I attached a short update GIF.

Repository:https://github.com/MichaelS1011/Ephemora-SkylineQuestion for developers: Does a 3D codebase map help you decide where to investigate next? Which parser state or project count should never be silently omitted?

6 Upvotes

1 comment sorted by

1

u/MichaelS1011 10d ago

How is Ephemora Skyline different from CodeQL, CodeScene or Sourcegraph?

They solve different problems.

GitHub CodeQL is built for semantic security analysis. CodeScene focuses on behavioural code health, hotspots and technical debt. Sourcegraph focuses on enterprise code search and cross-repository navigation.

Ephemora Skyline focuses on a narrower question, where in this codebase should I look next?