openai / go-vncdriver
Static Component Dependencies

An overview of static code dependencies among source code logical components.

Intro

Static code dependencies refer to the relationships between different modules, libraries, or components in a software system that are established at compile-time rather than at runtime. These dependencies are determined by the code itself, meaning that one module directly references another through imports, includes, or explicit references in the code. Examples include:

Learn more...
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 7 components.
  • 36 files, 5,954 LOC (100.0% vs. main code).
  • "flexflate" is biggest, containing 33.71% of LOC.
  • "flexzlib" is smallest, containing 2.44% of LOC.


flexflate2007 LOC (33%) 9 files
vncclient1382 LOC (23%) 8 files
ROOT927 LOC (15%) 8 files
cmd621 LOC (10%) 3 files
gymvnc609 LOC (10%) 5 files
vncgl263 LOC (4%) 1 file
flexzlib145 LOC (2%) 2 files
Static Dependencies
Dependencies among components are static code dependencies among files in different components.
  • Analyzed system has 6 links (arrows) between components.
  • The number on the arrow represents the number of files from referring component that depend on files in referred component.
  • These 6 links contain 8 dependencies.
G gymvnc gymvnc vncclient vncclient gymvnc->vncclient 1 ROOT ROOT cmd cmd cmd->gymvnc 2 cmd->vncclient 2 flexflate flexflate flexzlib flexzlib flexzlib->flexflate 1 vncclient->flexzlib 1 vncgl vncgl vncgl->vncclient 1


Download: SVG DOT (open online Graphviz editor)

Open 2D force graph...
Open 3D force graph...

Show more details about dependencies...





2025-04-14 11:47