Skip to content
CodArchthe living map of the architecture
ESEN

FAQ

One of the three Installation paths: the CLI with the web app (npm i -g codarch), the web app alone with Docker, or the desktop app. All three produce the same cc.json with the same checksum.

TypeScript/JavaScript, Java, Python, Go and C#. All of them yield metrics, symbols and imports, and all of them are drawn on the map; the detail is in what codarch analyze analyses. Rust and the .wasm/.node artefacts are measured for the migration lens, which is still JS/TS → Rust. A language outside that list is not analysed: its files do not appear.

No. The web app already comes with npm i -g codarch; codarch serve only opens it and analyses the repo.

No. It analyses through codarch serve, on your machine or inside the Docker container.

Do I need to clone the CodArch repo to use Docker?

Section titled “Do I need to clone the CodArch repo to use Docker?”

No: the ghcr.io/jaminsmoke/codarch-web:latest image and docker run are enough (see Web app). docker compose up --build is only for those who cloned the repository.

Windows or Linux warn that the installer is not signed

Section titled “Windows or Linux warn that the installer is not signed”

That is expected: the installers are unsigned because signing costs money and the project is in alpha. On Windows, SmartScreen may say the app is not from an identified developer: click More info → Run anyway. On Linux, the AppImage needs execute permission (chmod +x codarch-*.AppImage). Always download from the official Releases.

No. Without signing or notarisation Gatekeeper blocks the app and the updater cannot apply it. On macOS use the CLI or Docker.

No. The analysis is local; the web app and the container listen on loopback only, and the MCP is read-only over stdio.

Because the code or the configuration that analyses it changed. It does not depend on the date, the machine or who is looking: the map in the PR, in CI and in the agent is the same.