ARCLUX🐳.A Codebase Analysis Tool That Refuses to Guess

If you've ever stared at a 15,000-file monorepo wondering "what actually breaks if I touch this file," you know the feeling: you either click through imports by hand, or you trust a tool that's quietly guessing. ARCLUX is my answer to that — a dependency graph and impact analysis tool, CLI + web dashboard, built on one non-negotiable rule: every fact it reports has to trace back to real parsed code. An import statement. An export declaration. A resolved path. Not a probability. Not an embedding similarity score. A fact. Why deterministic, on purpose There's a wave of AI-powered "codebase intelligence" tools right now — semantic search, RAG over your repo, agents that summarize what a function does. Those are legitimate, useful tools solving a real problem. ARCLUX solves a different one: can a machine tell you, with zero ambiguity, exactly how your code is structurally connected? No LLM in the loop, no "probably." Just parse → index → graph → impact → detect, every step traceable and reproducible. repository -> parser -> graph -> detectors -> engine -> report | -> rules (framework conventions) -> impact (consumer/dependent tracing) `plaintext What it actually does today Dependency graph — imports, exports, folders, built from static analysis, not guesses Impact analysis — "what's affected if I change file X," traced through the real graph, not a heuristic 18 structural detectors — circular dependencies, dead code, unused exports, duplicate modules, orphan files, ambiguous symbol resolution (a name that resolves to two different definitions — a real bug class, more on that below), and more TypeScript, JavaScript, and Python parsing today, with Go dll Code snippet[KARNEL] ` /** * Copyright 2026 ARCLUX * * Licensed under the Apache License, Version 2.0 (the "License"); * you may not use this file except in compliance with the License. * You may obtain a copy of the License at * * http://www.apache.org/licenses/LICENSE-2.0 */ export interface ServiceHandle { name: string; processId: string; registeredAt: number; } export class ServiceRegistry { private services = new Map(); register(handle: ServiceHandle): void { if (this.services.has(handle.name)) { throw new Error(`ServiceRegistry: service "${handle.name}" is already registered`); } this.services.set(handle.name, handle); } unregister(name: string): boolean { return this.services.delete(name); } resolve(name: string): ServiceHandle | undefined { return this.services.get(name); } list(): ServiceHandle[] { return Array.from(this.services.values()); } } ` Open source, actively worked on, honestly alpha ARCLUX is Apache 2.0, and it's genuinely still alpha — expect stubs, expect rough edges, expect things marked "not yet built" in the project's own progress notes rather than silently pretended to work. If deterministic, verifiable codebase analysis is a problem space you care about, I'd love more eyes on it — issues, PRs, or just poking around and telling me what's missing. 🔗 github.com/GSF-001/ARCLUX