AtlasArc

Architecture Overview

Simple Java Mail · AtlasArc 1.0.0+d9b43417 · 2026-07-31T22:25:00Z

A whole-model architecture report for the current analysis.

Key Findings

HighCycles

5 problem cycle groups reported in this report scope.

NeutralCoupling

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

WatchJVM public surface

ARV and GRV describe JVM public-surface breadth: ARV 0.75, GRV 0.72. This surface is broad enough to inspect against package roles, marked public classes, and real callers.

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.

  • 5 problem cycle groups reported in this report scope.
  • Largest cycle group: Problem cycle 1 with 9 packages.

Evidence Summary

NCCD3.02

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

ARV0.75

Unweighted average of package Relative Visibility; each package contributes equally.

GRV0.72

Public JVM classes divided by all JVM classes across the graph.

Cycle groups5

Cycle clusters remain in the report scope.

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

CCDCumulative Component Dependency806.00
ACDAverage Component Dependency14.93
RACDRelative Average Component Dependency0.28
NCCDNormalized Cumulative Component Dependency3.02
ARVAverage Relative Visibility0.75
GRVGlobal Relative Visibility0.72

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 posture5 groups

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

Worth a closer lookNo corroborated package

No package stood out for more than one independent strict reason. Individual diagnostic groups may still contain useful single signals.

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 1

9 packages 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.

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 packages structure and cycle evidence from complementary angles.

Rendered as Topology Open

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

Configuration
Focus
project root
Filter
All visible packages
Heatmap
Off
Encoding
Nodes
Packages and package folders
Edges
Package dependencies; line width follows dependency weight
Border colour
Cycle, Safe Haven, intentional governance, and debt status from the model
authenticated-socks-module.mainbatch-module.maincli-module.maincore-module.maincore-test-module.maindkim-module.mainoutlook-module.mainsimple-java-mail.mainsmime-module.mainspring-module.mainorgorgorgorgorgorgorgorgorgsimplejavamailsimplejavamailsimplejavamailsimplejavamailsimplejavamailsimplejavamailsimplejavamailsimplejavamailsimplejavamailinternalinternalinternalapiinternalinternalinternalconverteremailinternalmailerinternalauthenticatedsockssupportbatchsupportclisupportemailinternalmailerutiloutlooksupportinternalinternalsmimesupportsocks5serverauthenticatedsockssupportclisupportoutlooksupportsmimesupportinternal commonsocks5clientiomsgClassesClassesconcurrentClassescliserializationtherapijavadocvalueinterpretersClassesconfigClassescommonsocks5serverbatchsupportmodelgeneralmodelbuildermodelClassesconfigClassesoutlookClassesconfigconfigmodulesconcurrentClassesClassesdemotestutildkimsupportconvertermodelmimemessageClassesClassesinternalClassesmoduleloaderutilClassesClassesrecipientbuildermodelClassesspringbootsupportspringsupport
Rendered as Dependency Matrix Open

Which packages depend on which other packages?

Configuration
Focus
project root
Filter
All visible packages
Heatmap
Off
Report Matrix
85 → 50 origin rows (ceiling 50)
Target columns
27 carrying dependencies · 0 empty restored · 23 empty omitted
Problem cycles
5 of 5 kept at exact package detail
Printable scale
Estimated 86%
Rollup safeguard
Use less package detail below 55%
Package detail
Up to 3 namespace segments
Encoding
Rows
Origin packages
Columns
Target packages
Cells
Dependency count and cycle/heatmap styling where applicable
  • AtlasArc fitted this report Matrix by combining deeper architecture units and summing dependencies across the resulting boundaries. It prioritized current problem-cycle groups while restoring package detail, then returned as many empty target columns as fit at natural size. Every fitted origin row remains visible; the report’s detailed findings and tables keep their prepared architecture-unit identities.
Modules cli-module.main core-module.main core-test-module.main simple-java-mail.main smime-module.main
simplejavamail
clisupport
therapijavadoc
simplejavamail
email
config
model
model
mailer
config
config
config
util
demo
testutil
simplejavamail
converter
internal
mimemessage
email
internal
mailer
internal
util
smimesupport
builder
model
▼ authenticated-socks-module.main / org
▼ simplejavamail
▶ authenticated-socks-module.main / internal 10 8 16
▼ batch-module.main / org
▶ batch-module.main / simplejavamail 5 27
▼ cli-module.main / org
▶ cli-module.main / simplejavamail - 1 9 13 1 2
▼ cli-module.main / internal
▼ clisupport 12 - 6 2 9 79 13 4 15 2 3
  therapijavadoc 2 7 - 3 7
▼ core-module.main / org
▶ core-module.main / simplejavamail - 15 3 3 3 5
▼ core-module.main / api
▼ email 2 - 18 8 1 1 3 14
  config - 11 9
▼ internal
▼ clisupport
  model - 2
▼ smimesupport
  model 5 -
▼ mailer 1 7 1 11 - 9 1
  config 1 1 - 2 2
  config 1 4 17 - 17
▼ internal
  config 41 4 -
▼ util 2 15 1 9 -
  core-test-module.main / demo 9 4 - 2
  testutil 1 5 1 1 -
▼ dkim-module.main / org
▶ dkim-module.main / simplejavamail 3 5 11 7
▼ outlook-module.main / org
▶ outlook-module.main / simplejavamail 28 36 17
▼ simple-java-mail.main / org
▶ simple-java-mail.main / simplejavamail 32 16 24 -
▼ simple-java-mail.main / converter 41 81 1 7 36 7 - 3 39 1 10 2 3
▼ internal 2 1 2 -
  mimemessage 26 147 31 37 4 - 2 1
▼ email 24 - 15
  internal 5 180 51 2 1 3 40 2 82 2 8 1 - 1
▼ mailer 6 88 4 4 4 4 3 - 22
▼ internal 38 139 54 1 42 156 191 32 72 15 2 2 4 3 2 - 13
  util 7 5 5 5 2 2 1 -
▼ smime-module.main / org
▼ simplejavamail
▼ internal
▼ smimesupport 24 50 7 8 4 3 - 16 44
  builder 1 3 2 - 3
  model 18 1 1 -
▼ spring-module.main / org
▶ spring-module.main / simplejavamail 4 86 1

Hierarchy & Size

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

Rendered as Composition · Sunburst Open

Where is the analysed codebase concentrated across the package hierarchy?

Configuration
Focus
project root
View
Sunburst
Size metric
Lines of code
Heatmap
Off
Encoding
Arc
Package hierarchy segment
Arc size
Relative lines of code
Colour
Hierarchy depth
s.main c.main c.main a.main s.main s.main o.main org org org org org org org org simpleja… simpleja… simpleja… simpleja… simpleja… simpleja… simpleja… simpleja… mailer converter o.s.email recipient internal o.s.api internal config internal internal internal springbo… springsu… internal internal internal internal internal modulelo… email mailer internal outlook util modules clisuppo… authenti… smimesup… outlooks… batchsup… util mimemess… config config clisuppo… outlooks… general therapij… valueint… socks5cl… socks5se… model internal converter model model msg io model 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
Package hierarchy segment
Area
Relative lines of code
Colour
Hierarchy depth
smimesupport c.main o.s.recipient therapijavadoc springbootsup… o.s.config springsupport o.s.internal internal o.s.a.email.config o.s.mailer d.main o.s.i.a.socks5client valueinterp… o.s.i.a.socks5server clisupport b.main outlook converter smimesuppo… o.s.api.mailer.config outlooksu… internal authenti… o.s.c.internal.mimemessage general org.simplejavamail.email.internal seria… conf… org.simplejavamail.api org.simplejavamail

Governance Summary

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

Metric Notes

CCD, ACD, RACD, and NCCD describe structural graph shape. Package diagnostics use fan-in, fan-out, instability, and line count. Dependency scope: compiled JVM dependencies. ARV is the unweighted average of package Relative Visibility; GRV is public JVM classes divided by all JVM classes across the graph. They describe public-surface breadth, not actual reachability or a universal architecture-health target.