AtlasArc

Architecture Report - Printable Version

Vue Core - AtlasArc 1.0.0+d9b43417 - 2026-07-31T21:30:00Z

All selected report sections in one print-ready HTML document.

Section 1 of 4

Architecture Overview

Open this chapter

Key Findings

HighCycles

8 problem cycle groups reported in this report scope.

NeutralCoupling

NCCD is 1.50. Use it as a same-project dependency-shape baseline; inspect cycles and concrete paths before interpreting a change.

NeutralJVM public surface

JVM public-surface metrics are not available for this analysis.

NeutralGovernance

No Safe Havens or repository governance records are active; all findings are treated as active structural findings.

Source Folders Worth a Closer Look

Each one stood out for more than one independent reason in this report.

  1. packages.shared.srcStood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).
  • The report reads package structure and dependency evidence; it does not know what the code is meant to do.
  • Coverage metrics are not loaded, so coverage-dependent risk readings are unavailable.
  • Package exclusions are disabled for this report context.

What This Report Says

Cycle risk is the dominant signal

Read this report as cycle-first evidence: resolve or consciously accept the reported cycle groups before treating lower-level metrics as optimization work.

  • 8 problem cycle groups reported in this report scope.
  • Worth a closer look: packages.shared.src stood out for 2 independent reasons (unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle)).
  • Largest cycle group: Problem cycle 5 with 4 source folders.

Evidence Summary

NCCD1.50

Same-project dependency-shape baseline; compare only on an equivalent analysis basis.

Cycle groups8

Cycle clusters remain in the report scope.

Precise graph statistics remain available below so the report stays auditable.

CCDCumulative Component Dependency231.00
ACDAverage Component Dependency7.45
RACDRelative Average Component Dependency0.25
NCCDNormalized Cumulative Component Dependency1.50
ARVAverage Relative Visibilityn/a
GRVGlobal Relative Visibilityn/a

Architecture Overview Focus

This profile reads the whole model first: cycle posture, architecture units that stood out for more than one strict reason, and any governance context that changes how warnings should be interpreted.

Cycle posture8 groups

Start by comparing the cycle map with the cycle groups table.

Worth a closer lookpackages.shared.src

Stood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).

Governance context0 Safe Havens / 0 debt records

Safe Havens, exclusions, and repository governance shape which findings remain active warnings.

Suggested Next Steps

1Start with Problem cycle 5

4 source folders participate in this architectural cycle group. Use the cycle table and topology figure to decide whether to break the loop or record an explicit governance decision.

2Take a closer look at packages.shared.src

This source folder stood out in more than one part of the report. Stood out for 2 independent reasons: unusually depended on while relying on relatively little (Fan-in 25, Instability 0.04); part of Problem cycle 4 (architectural cycle).

Report Basis

SectionArchitecture Overview
Report basisWhole model
Active lensgraph
Structural intentNormal
FiltersWhole-model defaults; durable governance retained

Structural Map

Topology, cycle-only topology, and Matrix figures show broad source folders structure and cycle evidence from complementary angles.

Rendered as Topology Open

How do source folders and subsystems depend on each other in this report?

Configuration
Focus
project root
Filter
All visible source folders
Heatmap
Off
Encoding
Nodes
Source Folders and grouping folders
Edges
Source Folder dependencies; line width follows dependency weight
Border colour
Cycle, Safe Haven, intentional governance, and debt status from the model
arc-templatespackagesteacupcompiler-corecompiler-domcompiler-sfccompiler-ssrreactivityruntime-coreruntime-domruntime-testserver-renderersharedvuevue-compatsrcsrcsrcsrcsrcsrcsrc distcompattransformsSource filestransformsSource filesscriptstyletemplateSource filestransformsSource filessrccompatcomponentshelpersSource filescomponentsdirectiveshelpersmodulesSource filessrchelpersSource filessrcsrcsrcreact-domlibvue-core
Rendered as Dependency Matrix Open

Which source folders depend on which other source folders?

Configuration
Focus
project root
Filter
All visible source folders
Heatmap
Off
Report Matrix
46 origin rows (ceiling 50)
Target columns
25 carrying dependencies · 2 empty restored · 19 empty omitted
Problem cycles
8 of 8 kept at exact package detail
Printable scale
Estimated 100%
Rollup safeguard
Use less package detail below 55%
Encoding
Rows
Origin source folders
Columns
Target source folders
Cells
source file dependency count and cycle/heatmap styling where applicable
  • Every origin row remains visible. After preserving dependency-bearing targets, AtlasArc returned as many empty target columns as fit at natural size.
arc-templates
dist
src
compat
transforms
src
transforms
src
script
style
template
src
transforms
src
src
compat
components
helpers
src
components
directives
helpers
modules
src
helpers
src
vue-core
▼ arc-templates -
  dist -
▼ packages
▼ compiler-core
▼ src - 3 26 7
  compat 3 -
  transforms 61 1 - 12
▼ compiler-dom
▼ src 4 - 10 2
  transforms 9 11 - 3
▼ compiler-sfc
▼ src 3 4 - 18 7 2 1 3
  script 6 5 - 1 4 3
  style 1 1 - 2
  template 2 - 2 3
▼ compiler-ssr
▼ src 4 - 14 1
  transforms 13 19 - 2
▼ reactivity
  src - 8
▼ runtime-core
▼ src 19 - 20 16 17 28
  compat 2 26 - 6 15
  components 1 27 - 1 4
  helpers 3 19 - 8
▼ runtime-dom
▼ src 3 - 2 3 2 5 3
  components 2 - 1 2
  directives 2 - 1 2
  helpers 2 - 2
  modules 4 1 1 1 1 - 4
▼ runtime-test
  src 1 1 4
▼ server-renderer
▼ src 4 - 12 4 1
  helpers 1 6 4 - 7
▼ shared
  src 1 -
▼ vue
▼ vue-compat
  src 1 1 1 5 2
  src 1 3 1
  react-dom
▼ teacup
  lib
  vue-core -

Hierarchy & Size

Composition figures show how code size and source folders are distributed through the selected scope.

Rendered as Composition · Sunburst Open

Where is the analysed codebase concentrated across the source folder hierarchy?

Configuration
Focus
project root
View
Sunburst
Size metric
Lines of code
Heatmap
Off
Encoding
Arc
Source Folder hierarchy segment
Arc size
Relative lines of code
Colour
Hierarchy depth
packages p.runtime-core p.compiler-core p.compiler-sfc p.runtime-dom p.reactivity p.compiler-ssr p.compiler-dom server-renderer packages.shared p.runtime-test p.r.src p.c.src p.c.src p.r.src p.r.src p.c.src p.c.src p.s.src p.shared.src p.r.src p.r.src.compat components p.r.src.helpers transforms p.c.src.compat p.c.src.script p.c.src.style p.c.s.template components directives p.r.src.modules transforms transforms p.s.src.helpers project root
Rendered as Composition · Circle Pack Open

How does the same hierarchy read as nested containment rather than radial depth?

Configuration
Focus
project root
View
Circle Pack
Size metric
Lines of code
Heatmap
Off
Encoding
Circle
Source Folder hierarchy segment
Area
Relative lines of code
Colour
Hierarchy depth
p.s.src directives p.r.s.components p.r.src.helpers p.r.src.modules p.c.src.style p.c.s.template p.runtime-test p.c.src.transforms packages.shared.src compat vue-compat p.c.src.transforms p.vue p.runtime-core.src.components packages.runtime-core.src.compat helpers packages.runtime-dom.src packages.compiler-core.src.transforms packages.reactivity.src packages.compiler-sfc.src.script packages

Governance Summary

Repository documentReady
Revisionmissing
EvidenceFresh
Local view exclusionsNone
Safe Havens0
Intentional records0
Debt records0
Maintenance findings0
CoverageNot loaded

Metric Notes

CCD, ACD, RACD, and NCCD describe structural graph shape. Source Folder diagnostics use fan-in, fan-out, instability, and line count. Dependency scope: source architecture dependencies. Type-only imports are included as source coupling. This analysis did not provide abstractness, arv, distance, grv, relativeVisibility; AtlasArc omits those metrics rather than treating them as zero.

Section 2 of 4

Cycle Evidence

Open this chapter

Cycle Evidence Briefing

This section separates current problem cycles from governance audit work. Repository decisions remain concise structural context here; their rationale and maintenance history live only in the optional Governance Audit.

Reported groups8
Debt records0
Intentional records0
Safe Havens0
Cycle modeAll cycle groups
Governed edge listIncluded
TypesArchitectural: 5, Nested: 3

All Problem Cycles Overview

One combined downward-layout topology shows how the current problem cycle groups sit together. It is included only when more than one group exists.

Rendered as Topology · Cycles Only Open

Which cycle warnings remain when non-cycle dependency structure is stripped away?

Configuration
Focus
project root
Filter
Cycles only
Heatmap
Off
Encoding
Nodes
Only source folders needed to show reported cycle evidence
Edges
Cycle-participating dependencies after governance rules are applied
Border colour
Problem, Safe Haven, intentional governance, and debt cycle status
  • This overview orients the cycle focus maps below.
packagescompiler-corecompiler-domcompiler-sfccompiler-ssrreactivityruntime-coreruntime-domserver-renderersharedsrcsrcsrcsrcsrcsrcsrc compattransformsSource filestransformsSource filesscriptstyleSource filestransformsSource filessrccompatcomponentshelpersSource filescomponentsdirectivesmodulesSource fileshelpersSource filessrc

Problem Cycles

Each card is one current problem strongly connected component. Every group gets one compact horizontal map. When additional maps are requested, a second map appears only when its focused architecture units or dependency edges strictly extend the compact evidence; layout-only duplicates are suppressed.

Problem cycle 1

Architectural cycle

3 source folders5 cycle edges
packagescompiler-coresrc compattransforms
Source Folders
  • packages.compiler-core.src
  • packages.compiler-core.src.compat
  • packages.compiler-core.src.transforms
Problem cycle 2

Nested cycle

2 source folders2 cycle edges
packagescompiler-domsrc transforms
Source Folders
  • packages.compiler-dom.src
  • packages.compiler-dom.src.transforms
Problem cycle 3

Architectural cycle

3 source folders5 cycle edges
packagescompiler-sfcsrc scriptstyle
Source Folders
  • packages.compiler-sfc.src
  • packages.compiler-sfc.src.script
  • packages.compiler-sfc.src.style
Problem cycle 4

Nested cycle

2 source folders2 cycle edges
packagescompiler-ssrsrc transforms
Source Folders
  • packages.compiler-ssr.src
  • packages.compiler-ssr.src.transforms
Problem cycle 5

Architectural cycle

2 source folders2 cycle edges
packagesreactivityshared srcsrc
Source Folders
  • packages.reactivity.src
  • packages.shared.src
Problem cycle 6

Architectural cycle

4 source folders8 cycle edges
packagesruntime-coresrc compatcomponentshelpers
Source Folders
  • packages.runtime-core.src
  • packages.runtime-core.src.compat
  • packages.runtime-core.src.components
  • packages.runtime-core.src.helpers
Problem cycle 7

Architectural cycle

4 source folders8 cycle edges
packagesruntime-domsrc componentsdirectivesmodules
Source Folders
  • packages.runtime-dom.src
  • packages.runtime-dom.src.components
  • packages.runtime-dom.src.directives
  • packages.runtime-dom.src.modules
Problem cycle 8

Nested cycle

2 source folders2 cycle edges
packagesserver-renderersrc helpers
Source Folders
  • packages.server-renderer.src
  • packages.server-renderer.src.helpers

Problem Cycle Edges

These are the strongest currently reported problem-cycle edges. They are not fully covered by repository governance and are not removed by Safe Havens in this report scope. The Dependency refs value counts acquired source file dependency references aggregated into each source folder-to-source folder edge; it is not a source line number.

Dependency refsCycleCycle governance
Sourcepackages.compiler-core.src.transforms
Targetpackages.compiler-core.src
61NestedProblem
Sourcepackages.runtime-core.src.components
Targetpackages.runtime-core.src
27NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.transforms
26NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src
26NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.compat
20NestedProblem
Sourcepackages.compiler-ssr.src.transforms
Targetpackages.compiler-ssr.src
19NestedProblem
Sourcepackages.runtime-core.src.helpers
Targetpackages.runtime-core.src
19NestedProblem
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.script
18NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.helpers
17NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.components
16NestedProblem
Sourcepackages.compiler-ssr.src
Targetpackages.compiler-ssr.src.transforms
14NestedProblem
Sourcepackages.server-renderer.src
Targetpackages.server-renderer.src.helpers
12NestedProblem
Sourcepackages.compiler-dom.src.transforms
Targetpackages.compiler-dom.src
11NestedProblem
Sourcepackages.compiler-dom.src
Targetpackages.compiler-dom.src.transforms
10NestedProblem
Sourcepackages.reactivity.src
Targetpackages.shared.src
8ArchitecturalProblem
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.style
7NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src.helpers
6ArchitecturalProblem
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-sfc.src
5NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.modules
5NestedProblem
Sourcepackages.server-renderer.src.helpers
Targetpackages.server-renderer.src
4NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.compat
3NestedProblem
Sourcepackages.compiler-core.src.compat
Targetpackages.compiler-core.src
3NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.directives
3NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.components
2NestedProblem
Sourcepackages.compiler-core.src.transforms
Targetpackages.compiler-core.src.compat
1ArchitecturalProblem
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-sfc.src.style
1ArchitecturalProblem
Sourcepackages.compiler-sfc.src.style
Targetpackages.compiler-sfc.src
1NestedProblem
Sourcepackages.runtime-core.src.components
Targetpackages.runtime-core.src.helpers
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.components
Targetpackages.runtime-dom.src.directives
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.directives
Targetpackages.runtime-dom.src.modules
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src
1NestedProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src.components
1ArchitecturalProblem
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-dom.src.directives
1ArchitecturalProblem
Sourcepackages.shared.src
Targetpackages.reactivity.src
1ArchitecturalProblem

Cycle Dependency Matrix

The cycle-only Matrix gives directional source folder-to-source folder dependency evidence complementary to the diagrams.

Rendered as Dependency Matrix · Cycles Only Open

Which reported cycle dependencies remain when non-cycle structure is stripped away?

Configuration
Focus
project root
Filter
Cycles only
Heatmap
Off
Report Matrix
32 origin rows (ceiling 50)
Target columns
22 carrying dependencies · 5 empty restored · 5 empty omitted
Problem cycles
8 of 8 kept at exact package detail
Printable scale
Estimated 100%
Rollup safeguard
Use less package detail below 55%
Encoding
Rows
Origin source folders in reported cycle evidence
Columns
Target source folders in reported cycle evidence
Cells
Cycle-participating dependency count and governance styling
  • Read this Matrix as the directional view of the cycle evidence reported in this chapter.
  • Every origin row remains visible. After preserving dependency-bearing targets, AtlasArc returned as many empty target columns as fit at natural size.
packages
compiler-core
src
compat
transforms
compiler-dom
src
transforms
compiler-sfc
src
script
style
compiler-ssr
src
transforms
src
src
compat
components
helpers
src
components
directives
modules
src
helpers
src
▼ packages -
▼ compiler-core -
▼ src - 3 26
  compat 3 -
  transforms 61 1 -
▼ compiler-dom -
▼ src - 10
  transforms 11 -
▼ compiler-sfc -
▼ src - 18 7
  script 5 - 1
  style 1 -
▼ compiler-ssr -
▼ src - 14
  transforms 19 -
▼ reactivity
  src - 8
▼ runtime-core
▼ src - 20 16 17
  compat 26 - 6
  components 27 - 1
  helpers 19 -
▼ runtime-dom
▼ src - 2 3 5
  components - 1
  directives - 1
  modules 1 1 1 -
▼ server-renderer
▼ src - 12
  helpers 4 -
▼ shared
  src 1 -
Section 3 of 4

Hotspot Risk

Open this chapter

Package Diagnostics Briefing

This chapter separates dependency shape, complexity pressure, and main-sequence distance into explicit diagnostic rules. Start with strict outliers where they exist; a Highest values group is a neutral fallback for orientation, not an AtlasArc problem verdict.

Eligible Source Folders31
Strict diagnostic groups1
Strictly selected source folders1
Highest values fallbacks2
Cycle source folders22
CoverageNot loaded

Subsystem-Level Architecture

Subsystem figures summarize boundary pressure, internal cohesion, and recursive architecture signals.

Rendered as Subsystems · Boundary Risk Open

Where does boundary pressure concentrate across the visible architecture?

Configuration
Focus
project root
Curated view
Boundary Risk
Filter
All visible source folders
Encoding
Bubble
Package-folder subsystem rollup
X axis
Fan-out
Y axis
Fan-in
Size
Source files
Colour
Instability
  • How to read this graph: each bubble is a visible architecture-boundary rollup. Right means more outgoing boundary dependencies; up means more incoming boundary dependencies; size is total class count.
  • Colour follows instability, so red means outgoing-heavy rather than automatically wrong. Use the figure to find boundary surfaces worth inspecting in Topology or Matrix.
  • Dashed rings mark expanded aggregate boundaries whose visible descendants are also present. Terminal packages or source folders remain valid boundaries and use their own metrics.
Fan-in
0 2 4 6 8 10 12 0 5 10 15 20 25 packages runtime-core src vue-core compiler-core src compiler-sfc src compiler-ssr src compat runtime-dom src
Fan-out
Rendered as Subsystems · Internal Tangles Open

Which subsystem areas contain internal cycle pressure?

Configuration
Focus
project root
Curated view
Internal Tangles
Filter
All visible source folders
Encoding
Bubble
Package-folder subsystem rollup
X axis
cycleCount
Y axis
largestCycle
Size
packageCount
Colour
Cycle status
  • How to read this graph: each bubble is a visible architecture-boundary rollup. Right means more fully contained package-cycle groups; up means the largest contained package cycle is larger; size is package count.
  • Only package cycles fully inside the boundary count here. Terminal-package class/file tangles remain separate Package Internals evidence in Topology. Use the cycle tables, Topology, or Matrix for concrete dependency edges and cross-boundary cycle context.
  • Dashed rings mark expanded aggregate boundaries whose visible descendants are also present. Terminal packages or source folders remain valid boundaries and use their own metrics.
Largest cycle
0 2 4 6 8 0 1 2 3 4 packages runtime-dom src compiler-sfc src runtime-core src compiler-core src compiler-dom src compiler-ssr src server-renderer src
Cycle groups

Source Folder Hotspots

Hotspot figures compare source folders through the available coupling and complexity evidence.

Rendered as Hotspots · Coupling Open

Which leaf source folders stand out by coupling pressure?

Configuration
Items
Leaf source folders
Focus
project root
Scope
Recursive
Preset
Coupling
Encoding
Bubble
One leaf source folder
X axis
Fan-out
Y axis
Fan-in
Size
Lines of code
Colour
Instability
  • Labels are shown for the largest report bubbles; inspect the source folder metrics table for the full ranked list.
Fan-in
0 2 4 6 0 5 10 15 20 25 src src script src transforms src src compat components transforms src
Fan-out

Source Folder Diagnostic Signals

Use these short lists to find unusual dependency shape, complexity pressure, and main-sequence distance without treating every high value as a problem. Each rule is evaluated across the prepared report scope; cycle participation is shown only as context.

Dependency hubs

Which packages carry unusually broad dependency traffic in both directions?

These packages combine a wide consumer blast radius with broad outward knowledge. Understand their role before changing a contract or moving responsibilities.

Nothing in this report scope is separated enough from its peers to count as a statistical outlier. For orientation, the table shows 2 of the strongest eligible examples.

Continue in AtlasArcShow me the backboneIsolate the packages with the widest consumer blast radius and inspect who relies on them.

How AtlasArc selected these rows

Highest values

Rule: Fan-in or Fan-out is above its upper outlier cutoff and the other degree is at or above its 75th percentile.

Population: 31 real leaf architecture units with Fan-in and Fan-out. Result: No strict outlier result; showing 2 of 2 eligible fallback values.

Cutoff: Fan-in > 10.31 (31 eligible values); Fan-out > 7.67 (31 eligible values)

Diagnostic evidence
Source Folderpackages.runtime-core.src
Fan-in
10
Fan-out
5
Instability
0.33
Cycle
Architectural
Source Folderpackages.runtime-dom.src
Fan-in
5
Fan-out
6
Instability
0.55
Cycle
Architectural

Incoming-heavy packages

Which packages are unusually depended on while relying on relatively little?

These are load-bearing packages whose contracts may affect many callers even though their own outward dependency surface stays comparatively narrow.

AtlasArc found 1 value clearly separated from its peers in this report scope.

Continue in AtlasArcShow me the backboneTrace the callers that make these packages part of the project's backbone.

How AtlasArc selected these rows

Strict outliers

Rule: Fan-in is above its upper outlier cutoff, Instability is at most 0.35, and dependency hubs are excluded.

Population: 28 real leaf architecture units with Instability. Result: 1 qualified; showing 1.

Cutoff: Fan-in > 10.31 (31 eligible values)

Diagnostic evidence
Source Folderpackages.shared.src
Fan-in
25
Fan-out
1
Instability
0.04
Cycle
Architectural

Outgoing-heavy packages

Which packages depend unusually broadly without serving many callers?

These packages know about many parts of the system. They may be healthy coordinators, or responsibilities may have accumulated in one place.

Nothing in this report scope is separated enough from its peers to count as a statistical outlier. For orientation, the table shows 5 of the strongest eligible examples.

Continue in AtlasArcTicking time bombsInspect the outward dependency seams and decide whether the package's responsibility is still coherent.

How AtlasArc selected these rows

Highest values

Rule: Fan-out is above its upper outlier cutoff, Instability is at least 0.65, and dependency hubs are excluded.

Population: 28 real leaf architecture units with Instability. Result: No strict outlier result; showing 5 of 14 eligible fallback values.

Cutoff: Fan-out > 7.67 (31 eligible values)

Diagnostic evidence
Source Folderpackages.compiler-sfc.src
Fan-in
2
Fan-out
7
Instability
0.78
Cycle
Architectural
Source Folderpackages.runtime-dom.src.modules
Fan-in
2
Fan-out
6
Instability
0.75
Cycle
Architectural
Source Folderpackages.compiler-sfc.src.script
Fan-in
1
Fan-out
5
Instability
0.83
Cycle
Architectural
Source Folderpackages.vue-compat.src
Fan-in
0
Fan-out
5
Instability
1.00
Cycle
—
Source Folderpackages.runtime-core.src.compat
Fan-in
2
Fan-out
4
Instability
0.67
Cycle
Architectural
Section 4 of 4

Evidence Appendix

Open this chapter

Evidence Appendix Briefing

Use these capped literal registers when a deeper review or handoff needs the package metrics and dependency rows behind the analytical chapters. For complete machine-readable data, use the applicable CSV, TSV, or View DOT export.

Maximum rows per register50
Eligible source folders31
Eligible dependencies94

Source Folder Metrics Register

Showing 31 of 31 eligible source folders, ordered by Fan-in + Fan-out and then stable identity. The selected maximum limits this review register; it does not truncate the applicable data exports.

Supported metrics
Source Folderpackages.shared.src
Fan-in
25
Fan-out
1
Instability
0.04
Source files
16
LOC
983
Cycle
Architectural
Source Folderpackages.runtime-core.src
Fan-in
10
Fan-out
5
Instability
0.33
Source files
34
LOC
13748
Cycle
Architectural
Source Folderpackages.compiler-dom.src
Fan-in
8
Fan-out
3
Instability
0.27
Source files
6
LOC
432
Cycle
Nested
Source Folderpackages.runtime-dom.src
Fan-in
5
Fan-out
6
Instability
0.55
Source files
5
LOC
2726
Cycle
Architectural
Source Folderpackages.compiler-core.src
Fan-in
6
Fan-out
3
Instability
0.33
Source files
13
LOC
6438
Cycle
Architectural
Source Folderpackages.compiler-sfc.src
Fan-in
2
Fan-out
7
Instability
0.78
Source files
9
LOC
2551
Cycle
Architectural
Source Folderpackages.runtime-dom.src.modules
Fan-in
2
Fan-out
6
Instability
0.75
Source files
5
LOC
523
Cycle
Architectural
Source Folderpackages.reactivity.src
Fan-in
6
Fan-out
1
Instability
0.14
Source files
13
LOC
3573
Cycle
Architectural
Source Folderpackages.compiler-sfc.src.script
Fan-in
1
Fan-out
5
Instability
0.83
Source files
14
LOC
3925
Cycle
Architectural
Source Folderpackages.compiler-ssr.src
Fan-in
3
Fan-out
3
Instability
0.50
Source files
4
LOC
415
Cycle
Nested
Source Folderpackages.runtime-core.src.compat
Fan-in
2
Fan-out
4
Instability
0.67
Source files
17
LOC
2442
Cycle
Architectural
Source Folderpackages.runtime-core.src.helpers
Fan-in
3
Fan-out
3
Instability
0.50
Source files
10
LOC
684
Cycle
Architectural
Source Folderpackages.runtime-dom.src.directives
Fan-in
3
Fan-out
3
Instability
0.50
Source files
3
LOC
575
Cycle
Architectural
Source Folderpackages.compiler-sfc.src.style
Fan-in
2
Fan-out
3
Instability
0.60
Source files
4
LOC
758
Cycle
Architectural
Source Folderpackages.runtime-core.src.components
Fan-in
1
Fan-out
4
Instability
0.80
Source files
4
LOC
2417
Cycle
Architectural
Source Folderpackages.runtime-dom.src.components
Fan-in
2
Fan-out
3
Instability
0.60
Source files
2
LOC
683
Cycle
Architectural
Source Folderpackages.server-renderer.src
Fan-in
1
Fan-out
4
Instability
0.80
Source files
5
LOC
743
Cycle
Nested
Source Folderpackages.server-renderer.src.helpers
Fan-in
1
Fan-out
4
Instability
0.80
Source files
10
LOC
526
Cycle
Nested
Source Folderpackages.vue-compat.src
Fan-in
0
Fan-out
5
Instability
1.00
Source files
6
LOC
182
Cycle
—
Source Folderpackages.compiler-core.src.transforms
Fan-in
1
Fan-out
3
Instability
0.75
Source files
15
LOC
3563
Cycle
Architectural
Source Folderpackages.compiler-dom.src.transforms
Fan-in
1
Fan-out
3
Instability
0.75
Source files
10
LOC
899
Cycle
Nested
Source Folderpackages.compiler-sfc.src.template
Fan-in
1
Fan-out
3
Instability
0.75
Source files
3
LOC
471
Cycle
—
Source Folderpackages.compiler-ssr.src.transforms
Fan-in
1
Fan-out
3
Instability
0.75
Source files
13
LOC
1698
Cycle
Nested
Source Folderpackages.runtime-dom.src.helpers
Fan-in
2
Fan-out
2
Instability
0.50
Source files
2
LOC
129
Cycle
—
Source Folderpackages.compiler-core.src.compat
Fan-in
2
Fan-out
1
Instability
0.33
Source files
2
LOC
314
Cycle
Architectural
Source Folderpackages.runtime-test.src
Fan-in
0
Fan-out
3
Instability
1.00
Source files
5
LOC
372
Cycle
—
Source Folderpackages.vue.src
Fan-in
0
Fan-out
3
Instability
1.00
Source files
3
LOC
127
Cycle
—
Source Foldervue-core
Fan-in
3
Fan-out
0
Instability
0.00
Source files
60
LOC
0
Cycle
—
Source Folderarc-templates.dist
Fan-in
0
Fan-out
0
Instability
—
Source files
1
LOC
0
Cycle
—
Source Folderreact-dom
Fan-in
0
Fan-out
0
Instability
—
Source files
1
LOC
0
Cycle
—
Source Folderteacup.lib
Fan-in
0
Fan-out
0
Instability
—
Source files
1
LOC
0
Cycle
—

Dependency-edge Register

Showing 50 of 94 eligible dependencies, ordered by Dependency refs and then Source and Target. The Dependency refs value counts acquired source file dependency references aggregated into each source folder-to-source folder edge; it is not a source line number.

Dependency refsCycleCycle governance
Sourcepackages.compiler-core.src.transforms
Targetpackages.compiler-core.src
61NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.shared.src
28——
Sourcepackages.runtime-core.src.components
Targetpackages.runtime-core.src
27NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.transforms
26NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src
26NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.compat
20NestedProblem
Sourcepackages.compiler-ssr.src.transforms
Targetpackages.compiler-ssr.src
19NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.reactivity.src
19——
Sourcepackages.runtime-core.src.helpers
Targetpackages.runtime-core.src
19NestedProblem
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.script
18NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.helpers
17NestedProblem
Sourcepackages.runtime-core.src
Targetpackages.runtime-core.src.components
16NestedProblem
Sourcepackages.runtime-core.src.compat
Targetpackages.shared.src
15——
Sourcepackages.compiler-ssr.src
Targetpackages.compiler-ssr.src.transforms
14NestedProblem
Sourcepackages.compiler-ssr.src.transforms
Targetpackages.compiler-dom.src
13——
Sourcepackages.compiler-core.src.transforms
Targetpackages.shared.src
12——
Sourcepackages.server-renderer.src
Targetpackages.server-renderer.src.helpers
12NestedProblem
Sourcepackages.compiler-dom.src.transforms
Targetpackages.compiler-dom.src
11NestedProblem
Sourcepackages.compiler-dom.src
Targetpackages.compiler-dom.src.transforms
10NestedProblem
Sourcepackages.compiler-dom.src.transforms
Targetpackages.compiler-core.src
9——
Sourcepackages.reactivity.src
Targetpackages.shared.src
8ArchitecturalProblem
Sourcepackages.runtime-core.src.helpers
Targetpackages.shared.src
8——
Sourcepackages.compiler-core.src
Targetpackages.shared.src
7——
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-sfc.src.style
7NestedProblem
Sourcepackages.server-renderer.src.helpers
Targetpackages.shared.src
7——
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-dom.src
6——
Sourcepackages.runtime-core.src.compat
Targetpackages.runtime-core.src.helpers
6ArchitecturalProblem
Sourcepackages.server-renderer.src.helpers
Targetpackages.runtime-dom.src
6——
Sourcepackages.compiler-sfc.src.script
Targetpackages.compiler-sfc.src
5NestedProblem
Sourcepackages.runtime-dom.src
Targetpackages.runtime-dom.src.modules
5NestedProblem
Sourcepackages.vue-compat.src
Targetpackages.runtime-dom.src
5——
Sourcepackages.compiler-dom.src
Targetpackages.compiler-core.src
4——
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-dom.src
4——
Sourcepackages.compiler-sfc.src.script
Targetpackages.shared.src
4——
Sourcepackages.compiler-ssr.src
Targetpackages.compiler-dom.src
4——
Sourcepackages.runtime-core.src.components
Targetpackages.shared.src
4——
Sourcepackages.runtime-dom.src.modules
Targetpackages.runtime-core.src
4——
Sourcepackages.runtime-dom.src.modules
Targetpackages.shared.src
4——
Sourcepackages.runtime-test.src
Targetpackages.shared.src
4——
Sourcepackages.server-renderer.src
Targetpackages.runtime-dom.src
4——
Sourcepackages.server-renderer.src
Targetpackages.shared.src
4——
Sourcepackages.server-renderer.src.helpers
Targetpackages.server-renderer.src
4NestedProblem
Sourcepackages.compiler-core.src
Targetpackages.compiler-core.src.compat
3NestedProblem
Sourcepackages.compiler-core.src.compat
Targetpackages.compiler-core.src
3NestedProblem
Sourcepackages.compiler-dom.src.transforms
Targetpackages.shared.src
3——
Sourcepackages.compiler-sfc.src
Targetpackages.compiler-core.src
3——
Sourcepackages.compiler-sfc.src
Targetpackages.shared.src
3——
Sourcepackages.compiler-sfc.src.script
Targetvue-core
3——
Sourcepackages.compiler-sfc.src.template
Targetvue-core
3——
Sourcepackages.runtime-core.src.helpers
Targetpackages.reactivity.src
3——