RepoPilot

cysharp/memorypack · Architecture

A static read of how cysharp/memorypack is wired together — module coupling, layering, and circular dependencies — derived from its import graph.

A
Architecture grade
score 100/100
0
Import cycles
lower is better
43
Modules parsed
95 edges
100%
Layeredness
clean-layer ratio

Most-depended-on modules

These are the highest-fan-in files — change them and the blast radius is largest. Read them first.

  • sandbox/SandboxWebApp/wwwroot/js/memorypack/MemoryPackWriter.js29 importers · radius 30
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/MemoryPackReader.js29 importers · radius 30
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/IMogeUnion.js7 importers · radius 8
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/NestedObject.js6 importers · radius 6
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/SampleUnion1.js4 importers · radius 10
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/SampleUnion2.js4 importers · radius 10
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/Gender.js4 importers · radius 4
  • sandbox/SandboxWebApp/wwwroot/js/memorypack/NoMarkByteEnum.js3 importers · radius 3

Modules (2)

Source directories grouped from the import graph. Each links to a per-module page with its files and how it couples to the rest.

Ask AI about cysharp/memorypack

Grounded in the actual source code. Pick a starter question or write your own.

Or write your own question

Informational only. RepoPilot summarises public signals at the time of analysis; they can be incomplete or stale. Not professional, security, or legal advice.