openai / gym-http-api
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 13 components.
  • 35 files, 2,744 LOC (100.0% vs. main code).
  • "ROOT" is biggest, containing 14.14% of LOC.
  • "binding-Julia" is smallest, containing 1.02% of LOC.


ROOT388 LOC (14%) 3 files
binding-cpp329 LOC (11%) 3 files
binding-hs311 LOC (11%) 9 files
binding-wl286 LOC (10%) 2 files
binding-go278 LOC (10%) 1 file
binding-rust205 LOC (7%) 2 files
binding-swift199 LOC (7%) 2 files
binding-matlab170 LOC (6%) 2 files
binding-js161 LOC (5%) 3 files
binding-lua150 LOC (5%) 2 files
binding-Ruby130 LOC (4%) 2 files
binding-clojure109 LOC (3%) 3 files
binding-Julia28 LOC (1%) 1 file
Static Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2025-04-14 11:46