Visualize Unity script relationships with an interactive dependency graph. Detect dead code, overloaded classes, and navigate large projects faster with analytics and inspection tools.Script Dependency Insight is a professional Unity Editor tool that scans your project scripts and visually maps code relationships through an interactive dependency graph. It helps developers understand complex architectures, locate over-connected manager classes, identify dead or unused scripts, and navigate large codebases faster.Built for solo developers, teams, and large projects, the tool converts confusing script structures into a clean visual system with searchable nodes, dependency lines, analytics dashboards, and script inspection tools.Whether you're refactoring a messy project, onboarding into an inherited codebase, or optimizing maintainability before release, Script Dependency Insight gives you instant clarity inside the Unity Editor.Technical DetailsUnity Editor extension for Windows/macOSScans C# scripts inside Assets folderDetects script references and relationshipsInteractive graph viewport with zoom and panSearchable dependency nodesInspector panel for selected scriptsAnalytics dashboard with dependency metricsSaved node positionsLightweight editor-only packageNo runtime impact on buildsFeaturesCore ScanningScan all project C# scriptsDetect dependencies between classesUsed By relationship trackingNamespace supportMonoBehaviour and ScriptableObject recognitionInteractive GraphVisual node graphDrag nodesZoom and pan cameraAnimated dependency linesGrid backgroundSearch filteringAuto layout systemInspector PanelSelected script detailsDependency listReferenced by listWarning badgesOpen script buttonPing asset buttonAnalyticsMost referenced scripts dashboardDependency ranking barsProject metrics summaryDead code detectionGod class risk warningsProductivitySaved graph layoutFaster architecture understandingEasier refactoring planningBetter onboarding for teamsSupported OSWindows 10 / 11macOSLinux (Unity Editor supported environments)Link to DocumentationAI was used as a development assistance tool during the creation of this package. It helped with brainstorming features, refining workflow ideas, generating UI/UX suggestions, improving code structure, debugging editor scripts, and accelerating documentation writing.AI was not used as a replacement for development ownership, but as a productivity tool to speed up iteration and polish during the package creation process.
