AtlasArc

Hotspot Risk

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

A diagnostic report that separates unusual dependency shape, complexity pressure, main-sequence distance, and coverage context.

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 Packages52
Strict diagnostic groups0
Strictly selected packages0
Highest values fallbacks4
Cycle packages24
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 packages
Encoding
Bubble
Package-folder subsystem rollup
X axis
Fan-out
Y axis
Fan-in
Size
Classes
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 10 20 30 40 50 60 0 20 40 60 80 100 120 core-module.main org simplejavamail api simple-java-mail.… org simplejavamail spring-module.main org simplejavamail springbootsupport mailer cli-module.main org simplejavamail internal internal clisupport email converter internal internal mimemessage mailer internal authenticated-soc… org simplejavamail
Fan-out
Rendered as Subsystems · Visibility Surface Open

Which subsystems expose a large public surface?

Configuration
Focus
project root
Curated view
Visibility Surface
Filter
All visible packages
Encoding
Bubble
Package-folder subsystem rollup
X axis
Relative visibility
Y axis
Abstractness
Size
Classes
Colour
Abstractness
  • How to read this graph: each bubble is a visible architecture-boundary rollup. Right means more visible API surface; up and colour both follow abstractness; size is total class count.
  • This view highlights boundary shape, not direct defect risk. A top/right bubble may be a deliberate public contract area.
  • 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.
Abstractness (A)
0.00 0.20 0.40 0.60 0.80 1.00 0.00 0.20 0.40 0.60 0.80 1.00 core-module.main org simplejavamail api simple-java-mail.… org simplejavamail spring-module.main org simplejavamail springbootsupport mailer cli-module.main org simplejavamail internal internal clisupport email converter internal internal mimemessage mailer internal authenticated-soc… org simplejavamail
Rel. Visibility (RV)
Rendered as Subsystems · Internal Tangles Open

Which subsystem areas contain internal cycle pressure?

Configuration
Focus
project root
Curated view
Internal Tangles
Filter
All visible packages
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 0 0 1 1 1 0 2 4 6 8 internal authenticated-soc… org simplejavamail internal authenticatedsock… internal socks5server batch-module.main org simplejavamail internal batchsupport email authenticatedsock… smimesupport util outlook-module.ma… org simplejavamail internal outlooksupport internal email spring-module.main org simplejavamail core-module.main
Cycle groups

Package Hotspots

Hotspot figures compare packages through the available coupling and complexity evidence.

Rendered as Hotspots · Coupling Open

Which leaf packages stand out by coupling pressure?

Configuration
Items
Leaf packages
Focus
project root
Scope
Recursive
Preset
Coupling
Encoding
Bubble
One leaf package
X axis
Fan-out
Y axis
Fan-in
Size
Lines of code
Colour
Instability
  • Labels are shown for the largest report bubbles; inspect the package metrics table for the full ranked list.
Fan-in
0 5 10 15 0 5 10 15 20 25 internal email internal mimemessage mailer config util socks5client clisupport converter config smimesupport config mailer recipient therapijavadoc springbootsupport springsupport socks5server model valueinterpreters batchsupport outlook converter
Fan-out
Rendered as Hotspots · Visibility Open

Which leaf packages are visible to many callers and far from the main sequence?

Configuration
Items
Leaf packages
Focus
project root
Scope
Recursive
Preset
Visibility
Encoding
Bubble
One leaf package
X axis
Relative visibility
Y axis
Fan-in
Size
Classes
Colour
Distance from main sequence
  • Labels are shown for the largest report bubbles; inspect the package metrics table for the full ranked list.
Fan-in
0.00 0.20 0.40 0.60 0.80 1.00 0 5 10 15 20 25 springbootsupport mimemessage internal email mailer util config config clisupport valueinterpreters model model smimesupport socks5client therapijavadoc modules model internal msg mailer util testutil batchsupport dkimsupport recipient socks5server io cli
Rel. Visibility (RV)
Rendered as Hotspots · Abstractness / Instability Open

Which leaf packages sit far from the main sequence?

Configuration
Items
Leaf packages
Focus
project root
Scope
Recursive
Preset
Zone Map
Encoding
Bubble
One leaf package
X axis
Instability
Y axis
Abstractness
Size
Distance from main sequence
Colour
Distance from main sequence
  • Labels are shown for the largest report bubbles; inspect the package metrics table for the full ranked list.
Abstractness (A)
0.00 0.20 0.40 0.60 0.80 1.00 0.00 0.20 0.40 0.60 0.80 1.00 common io concurrent serialization config util config concurrent moduleloader outlook config general model msg email model modules email config socks5client builder model demo internal model valueinterpreters util builder
Instability (I)

Package 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 5 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: 52 real leaf architecture units with Fan-in and Fan-out. Result: No strict outlier result; showing 5 of 5 eligible fallback values.

Cutoff: Fan-in > 30.18 (52 eligible values); Fan-out > 33.33 (52 eligible values)

Diagnostic evidence
Packagecore-module.mainorg.simplejavamail.internal.modules
Fan-in
12
Fan-out
10
Instability
0.45
Cycle
—
Packagesimple-java-mail.mainorg.simplejavamail.mailer.internal
Fan-in
6
Fan-out
19
Instability
0.76
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.api.email
Fan-in
27
Fan-out
7
Instability
0.21
Cycle
Architectural
Packagesimple-java-mail.mainorg.simplejavamail.email.internal
Fan-in
5
Fan-out
15
Instability
0.75
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.api.mailer
Fan-in
8
Fan-out
6
Instability
0.43
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.

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 AtlasArcShow me the backboneTrace the callers that make these packages part of the project's backbone.

How AtlasArc selected these rows

Highest values

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

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

Cutoff: Fan-in > 30.18 (52 eligible values)

Diagnostic evidence
Packagecore-module.mainorg.simplejavamail.api.email
Fan-in
27
Fan-out
7
Instability
0.21
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.internal.util
Fan-in
27
Fan-out
4
Instability
0.13
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.api.mailer.config
Fan-in
16
Fan-out
4
Instability
0.20
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail
Fan-in
14
Fan-out
0
Instability
0.00
Cycle
—
Packagecore-module.mainorg.simplejavamail.api.email.config
Fan-in
11
Fan-out
2
Instability
0.15
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: 51 real leaf architecture units with Instability. Result: No strict outlier result; showing 5 of 23 eligible fallback values.

Cutoff: Fan-out > 33.33 (52 eligible values)

Diagnostic evidence
Packagesimple-java-mail.mainorg.simplejavamail.mailer.internal
Fan-in
6
Fan-out
19
Instability
0.76
Cycle
Architectural
Packagesimple-java-mail.mainorg.simplejavamail.converter
Fan-in
4
Fan-out
17
Instability
0.81
Cycle
Architectural
Packagesimple-java-mail.mainorg.simplejavamail.email.internal
Fan-in
5
Fan-out
15
Instability
0.75
Cycle
Architectural
Packagesmime-module.mainorg.simplejavamail.internal.smimesupport
Fan-in
1
Fan-out
12
Instability
0.92
Cycle
Architectural
Packagecli-module.mainorg.simplejavamail.internal.clisupport
Fan-in
2
Fan-out
11
Instability
0.85
Cycle
Nested

Main-sequence outliers

Which substantial packages sit unusually far from the main sequence?

These packages combine stability and abstraction in an unusual way for this project. That is a design question to inspect, not an automatic defect.

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 AtlasArcIdentify risky hotspotsPlace these candidates beside size, dependency reach, and other hotspot evidence before prioritizing work.

How AtlasArc selected these rows

Highest values

Rule: Distance is above its upper outlier cutoff and at least 0.50, with total degree or LOC at or above its positive median.

Population: 51 real leaf architecture units with Distance. Result: No strict outlier result; showing 5 of 9 eligible fallback values.

Cutoff: Distance > 1.20 (51 eligible values)

Diagnostic evidence
Packagecore-module.mainorg.simplejavamail.api.email.config
Distance
0.85
Fan-in
11
Fan-out
2
LOC
699
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.internal.util
Distance
0.77
Fan-in
27
Fan-out
4
LOC
905
Cycle
Architectural
Packagesimple-java-mail.mainorg.simplejavamail.internal.moduleloader
Distance
0.67
Fan-in
6
Fan-out
3
LOC
133
Cycle
—
Packagecore-module.mainorg.simplejavamail.internal.config
Distance
0.67
Fan-in
4
Fan-out
2
LOC
57
Cycle
Architectural
Packagecore-module.mainorg.simplejavamail.api.outlook
Distance
0.60
Fan-in
3
Fan-out
2
LOC
243
Cycle
—