Executive summary
masesgroup/JNet falls short of our standard for production because the documentation refers to links that don't exist and the project keeps no record of its design decisions. It scores 53.4 out of 100 and is rated Adequate, and two of its 24 critical findings are security problems.
Maturity, at 46.8, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6.2 points. Bringing the documentation in line with the code comes next, worth about 5.9 points. Raising Maturity to 70 would lift the score to about 59.2.
One password or key is open to anyone who can read the repository. One setting leaves the servers or containers unsafe. Replacing the exposed password or key and correcting the unsafe settings would close both risks. The eight loops of parts of the code that depend on each other need breaking by moving the shared parts into a project of their own.
The product code is 41,905 lines, about €200,000 to rebuild.
If Maturity rose from 46.8 to 70, the lowest score rated Strong, the score would rise from 53.4 to about 59.2.
Rebuild cost: about €200,000 · Estimate
| Cost to rebuild | €65,000 to €340,000, for 1,083 to 3,545 hours of work, about 1.4 person-years for 1 to 3 engineers |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,905 lines of product code |
| Comment lines | The estimate prices 40,166 lines. Comment lines count towards the size of 41,905 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Java.Lang.Annotation | 2 Java.Nio | 3 Java.Time | 4 Java.Util | 5 Java.Math | 6 MASES.JNet.Specific | 7 Java.Security.Cert | 8 Java.Security | 9 Java.Util.Concurrent | 10 Java.Nio.File.Attribute | 11 Java.Nio.File | 12 Java.Nio.Channels | 13 Java.Net | 14 Java.Io | 15 Java.Lang.Reflect | 16 Java.Lang | 17 Java.Awt.ImageNs | 18 Java.Sql | 19 Java.Text | 20 Javax.Management | 21 Javax.Net.Ssl | 22 Javax.Xml.Namespace | 23 Javax.Xml.Transform | 24 Org.W3c.Dom | 25 Org.Xml.Sax | 26 Java.Awt.EventNs | 27 Java.Beans | 28 Javax.Xml.Stream | 29 Javax.Swing.Tree | 30 Javax.Xml.Bind | 31 Javax.Swing.Event | 32 Javax.Swing.Plaf | 33 Javax.Xml.Ws | 34 Javax.Swing | 35 Javax.Xml.Ws.Spi | 36 Javax.Swing.Plaf.Basic | 37 Javax.Swing.Text | 38 Javax.Accessibility | 39 Java.Awt | 40 Javax.Imageio |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Java.Lang.Annotation | 11 | |||||||||||||||||||||||||||||||||||||||
| 2 Java.Nio | 15 | |||||||||||||||||||||||||||||||||||||||
| 3 Java.Time | 8 | 13 | 36 | |||||||||||||||||||||||||||||||||||||
| 4 Java.Util | 4 | 4 | 2 | 1 | 1 | 1 | 45 | 78 | ||||||||||||||||||||||||||||||||
| 5 Java.Math | 1 | 1 | 9 | |||||||||||||||||||||||||||||||||||||
| 6 MASES.JNet.Specific | 7 | 1 | 8 | |||||||||||||||||||||||||||||||||||||
| 7 Java.Security.Cert | 38 | 5 | 21 | 1 | 7 | 44 | ||||||||||||||||||||||||||||||||||
| 8 Java.Security | 2 | 21 | 9 | 3 | 26 | 51 | ||||||||||||||||||||||||||||||||||
| 9 Java.Util.Concurrent | 73 | 1 | 2 | 16 | 49 | |||||||||||||||||||||||||||||||||||
| 10 Java.Nio.File.Attribute | 2 | 1 | 11 | 2 | 1 | 1 | 27 | |||||||||||||||||||||||||||||||||
| 11 Java.Nio.File | 14 | 1 | 2 | 12 | 3 | 4 | 11 | 42 | ||||||||||||||||||||||||||||||||
| 12 Java.Nio.Channels | 18 | 5 | 10 | 2 | 4 | 24 | 10 | 28 | ||||||||||||||||||||||||||||||||
| 13 Java.Net | 16 | 2 | 6 | 3 | 23 | 49 | ||||||||||||||||||||||||||||||||||
| 14 Java.Io | 1 | 3 | 2 | 1 | 3 | 2 | 50 | |||||||||||||||||||||||||||||||||
| 15 Java.Lang.Reflect | 5 | 1 | 1 | 28 | ||||||||||||||||||||||||||||||||||||
| 16 Java.Lang | 13 | 2 | 10 | 1 | 3 | 1 | 1 | 4 | 24 | 10 | ||||||||||||||||||||||||||||||
| 17 Java.Awt.ImageNs | 9 | 1 | 7 | 32 | ||||||||||||||||||||||||||||||||||||
| 18 Java.Sql | 3 | 27 | 10 | 1 | 2 | 10 | 42 | 77 | ||||||||||||||||||||||||||||||||
| 19 Java.Text | 20 | 1 | 4 | 35 | ||||||||||||||||||||||||||||||||||||
| 20 Javax.Management | 4 | 13 | 2 | 3 | 1 | 12 | 5 | 75 | ||||||||||||||||||||||||||||||||
| 21 Javax.Net.Ssl | 1 | 12 | 2 | 10 | 18 | 7 | 2 | 30 | ||||||||||||||||||||||||||||||||
| 22 Javax.Xml.Namespace | 2 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 23 Javax.Xml.Transform | 3 | 1 | 14 | |||||||||||||||||||||||||||||||||||||
| 24 Org.W3c.Dom | 41 | |||||||||||||||||||||||||||||||||||||||
| 25 Org.Xml.Sax | 2 | 2 | 21 | |||||||||||||||||||||||||||||||||||||
| 26 Java.Awt.EventNs | 19 | 26 | 7 | 1 | 29 | |||||||||||||||||||||||||||||||||||
| 27 Java.Beans | 4 | 6 | 3 | 4 | 6 | 39 | 1 | 12 | ||||||||||||||||||||||||||||||||
| 28 Javax.Xml.Stream | 1 | 4 | 22 | 10 | 2 | |||||||||||||||||||||||||||||||||||
| 29 Javax.Swing.Tree | 5 | 4 | 6 | 2 | 3 | 10 | 11 | 12 | ||||||||||||||||||||||||||||||||
| 30 Javax.Xml.Bind | 4 | 6 | 1 | 6 | 18 | 30 | 8 | 7 | 7 | 6 | 8 | |||||||||||||||||||||||||||||
| 31 Javax.Swing.Event | 35 | 24 | 1 | 1 | 4 | 12 | 1 | 3 | 7 | 6 | 5 | |||||||||||||||||||||||||||||
| 32 Javax.Swing.Plaf | 4 | 5 | 1 | 2 | 1 | 18 | 4 | 1 | 27 | |||||||||||||||||||||||||||||||
| 33 Javax.Xml.Ws | 26 | 10 | 3 | 6 | 1 | 1 | 46 | 1 | 5 | 3 | 3 | |||||||||||||||||||||||||||||
| 34 Javax.Swing | 27 | 1 | 2 | 2 | 30 | 110 | 2 | 4 | 40 | 13 | 8 | 59 | 32 | 14 | 44 | 189 | ||||||||||||||||||||||||
| 35 Javax.Xml.Ws.Spi | 2 | 3 | 1 | 2 | 1 | 8 | 2 | 1 | 1 | 1 | 8 | |||||||||||||||||||||||||||||
| 36 Javax.Swing.Plaf.Basic | 1 | 4 | 17 | 31 | 15 | 1 | 21 | 39 | 60 | 6 | 62 | |||||||||||||||||||||||||||||
| 37 Javax.Swing.Text | 12 | 23 | 54 | 6 | 5 | 1 | 23 | 1 | 20 | 1 | 6 | 49 | ||||||||||||||||||||||||||||
| 38 Javax.Accessibility | 3 | 2 | 20 | 2 | 1 | 5 | 20 | |||||||||||||||||||||||||||||||||
| 39 Java.Awt | 20 | 1 | 3 | 34 | 81 | 38 | 5 | 68 | 5 | 15 | ||||||||||||||||||||||||||||||
| 40 Javax.Imageio | 8 | 1 | 4 | 3 | 15 | 6 |
1→16 Java.Lang.Annotation uses Java.Lang part of a loop✕
- Connections
- 11 pairs of types, where a type in Java.Lang.Annotation uses a type in Java.Lang.
- The types involved
Java.Lang.Annotation.Annotation→Java.Lang.ClassJava.Lang.Annotation.AnnotationFormatError→Java.Lang.ErrorJava.Lang.Annotation.AnnotationTypeMismatchException→Java.Lang.RuntimeExceptionJava.Lang.Annotation.ElementType→Java.Lang.EnumJava.Lang.Annotation.ElementType→Java.Lang.StringJava.Lang.Annotation.IAnnotation→Java.Lang.ClassJava.Lang.Annotation.IRepeatable→Java.Lang.ClassJava.Lang.Annotation.IncompleteAnnotationException→Java.Lang.RuntimeExceptionJava.Lang.Annotation.Repeatable→Java.Lang.ClassJava.Lang.Annotation.RetentionPolicy→Java.Lang.EnumJava.Lang.Annotation.RetentionPolicy→Java.Lang.String
- Direction
- Java.Lang.Annotation uses Java.Lang, so a change to Java.Lang can break Java.Lang.Annotation, while a change to Java.Lang.Annotation can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
2→16 Java.Nio uses Java.Lang part of a loop✕
- Connections
- 15 pairs of types, where a type in Java.Nio uses a type in Java.Lang.
- The types involved
Java.Nio.BufferOverflowException→Java.Lang.RuntimeExceptionJava.Nio.BufferUnderflowException→Java.Lang.RuntimeExceptionJava.Nio.ByteBuffer→Java.Lang.ComparableJava.Nio.CharBuffer→Java.Lang.AppendableJava.Nio.CharBuffer→Java.Lang.CharSequenceJava.Nio.CharBuffer→Java.Lang.ComparableJava.Nio.CharBuffer→Java.Lang.ReadableJava.Nio.CharBuffer→Java.Lang.StringJava.Nio.DoubleBuffer→Java.Lang.ComparableJava.Nio.FloatBuffer→Java.Lang.ComparableJava.Nio.IntBuffer→Java.Lang.ComparableJava.Nio.InvalidMarkException→Java.Lang.IllegalStateExceptionJava.Nio.LongBuffer→Java.Lang.ComparableJava.Nio.ReadOnlyBufferException→Java.Lang.UnsupportedOperationExceptionJava.Nio.ShortBuffer→Java.Lang.Comparable
- Direction
- Java.Nio uses Java.Lang, so a change to Java.Lang can break Java.Nio, while a change to Java.Nio can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→4 Java.Time uses Java.Util part of a loop✕
- Connections
- 8 pairs of types, where a type in Java.Time uses a type in Java.Util.
- The types involved
Java.Time.DayOfWeek→Java.Util.LocaleJava.Time.Duration→Java.Util.ListJava.Time.Month→Java.Util.LocaleJava.Time.OffsetDateTime→Java.Util.ComparatorJava.Time.Period→Java.Util.ListJava.Time.ZoneId→Java.Util.LocaleJava.Time.ZoneId→Java.Util.MapJava.Time.ZoneId→Java.Util.Set
- Direction
- Java.Time uses Java.Util, so a change to Java.Util can break Java.Time, while a change to Java.Time can't break Java.Util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→14 Java.Time uses Java.Io part of a loop✕
- Connections
- 13 pairs of types, where a type in Java.Time uses a type in Java.Io.
- The types involved
Java.Time.Duration→Java.Io.SerializableJava.Time.Instant→Java.Io.SerializableJava.Time.LocalDate→Java.Io.SerializableJava.Time.LocalDateTime→Java.Io.SerializableJava.Time.LocalTime→Java.Io.SerializableJava.Time.MonthDay→Java.Io.SerializableJava.Time.OffsetDateTime→Java.Io.SerializableJava.Time.OffsetTime→Java.Io.SerializableJava.Time.Period→Java.Io.SerializableJava.Time.Year→Java.Io.SerializableJava.Time.YearMonth→Java.Io.SerializableJava.Time.ZoneId→Java.Io.SerializableJava.Time.ZonedDateTime→Java.Io.Serializable
- Direction
- Java.Time uses Java.Io, so a change to Java.Io can break Java.Time, while a change to Java.Time can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
3→16 Java.Time uses Java.Lang part of a loop✕
- Connections
- 36 pairs of types, where a type in Java.Time uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Time.DateTimeException→Java.Lang.RuntimeExceptionJava.Time.DayOfWeek→Java.Lang.EnumJava.Time.DayOfWeek→Java.Lang.StringJava.Time.Duration→Java.Lang.CharSequenceJava.Time.Duration→Java.Lang.ComparableJava.Time.Instant→Java.Lang.CharSequenceJava.Time.Instant→Java.Lang.ComparableJava.Time.LocalDate→Java.Lang.CharSequenceJava.Time.LocalDate→Java.Lang.StringJava.Time.LocalDateTime→Java.Lang.CharSequenceJava.Time.LocalDateTime→Java.Lang.StringJava.Time.LocalTime→Java.Lang.CharSequenceJava.Time.LocalTime→Java.Lang.ComparableJava.Time.LocalTime→Java.Lang.StringJava.Time.Month→Java.Lang.EnumJava.Time.Month→Java.Lang.StringJava.Time.MonthDay→Java.Lang.CharSequenceJava.Time.MonthDay→Java.Lang.ComparableJava.Time.MonthDay→Java.Lang.StringJava.Time.OffsetDateTime→Java.Lang.CharSequenceJava.Time.OffsetDateTime→Java.Lang.ComparableJava.Time.OffsetDateTime→Java.Lang.StringJava.Time.OffsetTime→Java.Lang.CharSequenceJava.Time.OffsetTime→Java.Lang.ComparableJava.Time.OffsetTime→Java.Lang.String
- Direction
- Java.Time uses Java.Lang, so a change to Java.Lang can break Java.Time, while a change to Java.Time can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→2 Java.Util uses Java.Nio✕
- Connections
- 4 pairs of types, where a type in Java.Util uses a type in Java.Nio.
- The types involved
Java.Util.BitSet→Java.Nio.ByteBufferJava.Util.BitSet→Java.Nio.LongBufferJava.Util.Decoder→Java.Nio.ByteBufferJava.Util.Encoder→Java.Nio.ByteBuffer
- Direction
- Java.Util uses Java.Nio, so a change to Java.Nio can break Java.Util, while a change to Java.Util can't break Java.Nio.
- Position
- Below the diagonal: Java.Util uses a module listed above it, which is the healthy direction.
4→3 Java.Util uses Java.Time✕
- Connections
- 4 pairs of types, where a type in Java.Util uses a type in Java.Time.
- The types involved
Java.Util.Calendar→Java.Time.InstantJava.Util.Date→Java.Time.InstantJava.Util.GregorianCalendar→Java.Time.ZonedDateTimeJava.Util.TimeZone→Java.Time.ZoneId
- Direction
- Java.Util uses Java.Time, so a change to Java.Time can break Java.Util, while a change to Java.Util can't break Java.Time.
- Position
- Below the diagonal: Java.Util uses a module listed above it, which is the healthy direction.
4→5 Java.Util uses Java.Math part of a loop✕
- Connections
- 2 pairs of types, where a type in Java.Util uses a type in Java.Math.
- The types involved
Java.Util.Scanner→Java.Math.BigDecimalJava.Util.Scanner→Java.Math.BigInteger
- Direction
- Java.Util uses Java.Math, so a change to Java.Math can break Java.Util, while a change to Java.Util can't break Java.Math.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→8 Java.Util uses Java.Security part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Util uses a type in Java.Security.
- The types involved
Java.Util.PropertyPermission→Java.Security.BasicPermission
- Direction
- Java.Util uses Java.Security, so a change to Java.Security can break Java.Util, while a change to Java.Util can't break Java.Security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→11 Java.Util uses Java.Nio.File part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Util uses a type in Java.Nio.File.
- The types involved
Java.Util.Scanner→Java.Nio.File.Path
- Direction
- Java.Util uses Java.Nio.File, so a change to Java.Nio.File can break Java.Util, while a change to Java.Util can't break Java.Nio.File.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→12 Java.Util uses Java.Nio.Channels part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Util uses a type in Java.Nio.Channels.
- The types involved
Java.Util.Scanner→Java.Nio.Channels.ReadableByteChannel
- Direction
- Java.Util uses Java.Nio.Channels, so a change to Java.Nio.Channels can break Java.Util, while a change to Java.Util can't break Java.Nio.Channels.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→14 Java.Util uses Java.Io part of a loop✕
- Connections
- 45 pairs of types, where a type in Java.Util uses a type in Java.Io. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Util.ArrayDeque→Java.Io.SerializableJava.Util.ArrayList→Java.Io.SerializableJava.Util.BitSet→Java.Io.SerializableJava.Util.Calendar→Java.Io.SerializableJava.Util.Currency→Java.Io.SerializableJava.Util.Date→Java.Io.SerializableJava.Util.Decoder→Java.Io.InputStreamJava.Util.Encoder→Java.Io.OutputStreamJava.Util.EnumMap→Java.Io.SerializableJava.Util.EnumSet→Java.Io.SerializableJava.Util.EventObject→Java.Io.SerializableJava.Util.Formatter→Java.Io.CloseableJava.Util.Formatter→Java.Io.FileJava.Util.Formatter→Java.Io.FlushableJava.Util.Formatter→Java.Io.IOExceptionJava.Util.Formatter→Java.Io.OutputStreamJava.Util.Formatter→Java.Io.PrintStreamJava.Util.HashMap→Java.Io.SerializableJava.Util.HashSet→Java.Io.SerializableJava.Util.Hashtable→Java.Io.SerializableJava.Util.IdentityHashMap→Java.Io.SerializableJava.Util.InvalidPropertiesFormatException→Java.Io.IOExceptionJava.Util.LinkedList→Java.Io.SerializableJava.Util.Locale→Java.Io.SerializableJava.Util.PriorityQueue→Java.Io.Serializable
- Direction
- Java.Util uses Java.Io, so a change to Java.Io can break Java.Util, while a change to Java.Util can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
4→16 Java.Util uses Java.Lang part of a loop✕
- Connections
- 78 pairs of types, where a type in Java.Util uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Util.AbstractList→Java.Lang.ObjectJava.Util.ArrayDeque→Java.Lang.CloneableJava.Util.ArrayList→Java.Lang.CloneableJava.Util.Arrays→Java.Lang.ClassJava.Util.Arrays→Java.Lang.StringJava.Util.BigDecimalLayoutForm→Java.Lang.EnumJava.Util.BigDecimalLayoutForm→Java.Lang.StringJava.Util.BitSet→Java.Lang.CloneableJava.Util.Builder→Java.Lang.StringJava.Util.Calendar→Java.Lang.CloneableJava.Util.Calendar→Java.Lang.ComparableJava.Util.Calendar→Java.Lang.IntegerJava.Util.Calendar→Java.Lang.StringJava.Util.Category→Java.Lang.EnumJava.Util.Category→Java.Lang.StringJava.Util.Collection→Java.Lang.IterableJava.Util.Collections→Java.Lang.BooleanJava.Util.Collections→Java.Lang.ClassJava.Util.ConcurrentModificationException→Java.Lang.RuntimeExceptionJava.Util.Control→Java.Lang.ClassLoaderJava.Util.Control→Java.Lang.StringJava.Util.Currency→Java.Lang.StringJava.Util.Date→Java.Lang.CloneableJava.Util.Date→Java.Lang.ComparableJava.Util.Date→Java.Lang.String
- Direction
- Java.Util uses Java.Lang, so a change to Java.Lang can break Java.Util, while a change to Java.Util can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→4 Java.Math uses Java.Util✕
- Connections
- 1 pair of types, where a type in Java.Math uses a type in Java.Util.
- The types involved
Java.Math.BigInteger→Java.Util.Random
- Direction
- Java.Math uses Java.Util, so a change to Java.Util can break Java.Math, while a change to Java.Math can't break Java.Util.
- Position
- Below the diagonal: Java.Math uses a module listed above it, which is the healthy direction.
5→14 Java.Math uses Java.Io part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Math uses a type in Java.Io.
- The types involved
Java.Math.MathContext→Java.Io.Serializable
- Direction
- Java.Math uses Java.Io, so a change to Java.Io can break Java.Math, while a change to Java.Math can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
5→16 Java.Math uses Java.Lang part of a loop✕
- Connections
- 9 pairs of types, where a type in Java.Math uses a type in Java.Lang.
- The types involved
Java.Math.BigDecimal→Java.Lang.ComparableJava.Math.BigDecimal→Java.Lang.NumberJava.Math.BigDecimal→Java.Lang.StringJava.Math.BigInteger→Java.Lang.ComparableJava.Math.BigInteger→Java.Lang.NumberJava.Math.BigInteger→Java.Lang.StringJava.Math.MathContext→Java.Lang.StringJava.Math.RoundingMode→Java.Lang.EnumJava.Math.RoundingMode→Java.Lang.String
- Direction
- Java.Math uses Java.Lang, so a change to Java.Lang can break Java.Math, while a change to Java.Math can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
6→2 MASES.JNet.Specific uses Java.Nio✕
- Connections
- 7 pairs of types, where a type in MASES.JNet.Specific uses a type in Java.Nio.
- The types involved
MASES.JNet.Specific.JNetHelper→Java.Nio.ByteBufferMASES.JNet.Specific.JNetHelper→Java.Nio.CharBufferMASES.JNet.Specific.JNetHelper→Java.Nio.DoubleBufferMASES.JNet.Specific.JNetHelper→Java.Nio.FloatBufferMASES.JNet.Specific.JNetHelper→Java.Nio.IntBufferMASES.JNet.Specific.JNetHelper→Java.Nio.LongBufferMASES.JNet.Specific.JNetHelper→Java.Nio.ShortBuffer
- Direction
- MASES.JNet.Specific uses Java.Nio, so a change to Java.Nio can break MASES.JNet.Specific, while a change to MASES.JNet.Specific can't break Java.Nio.
- Position
- Below the diagonal: MASES.JNet.Specific uses a module listed above it, which is the healthy direction.
6→4 MASES.JNet.Specific uses Java.Util✕
- Connections
- 1 pair of types, where a type in MASES.JNet.Specific uses a type in Java.Util.
- The types involved
MASES.JNet.Specific.JNetHelper→Java.Util.List
- Direction
- MASES.JNet.Specific uses Java.Util, so a change to Java.Util can break MASES.JNet.Specific, while a change to MASES.JNet.Specific can't break Java.Util.
- Position
- Below the diagonal: MASES.JNet.Specific uses a module listed above it, which is the healthy direction.
6→16 MASES.JNet.Specific uses Java.Lang part of a loop✕
- Connections
- 8 pairs of types, where a type in MASES.JNet.Specific uses a type in Java.Lang.
- The types involved
MASES.JNet.Specific.JNetHelper→Java.Lang.ByteMASES.JNet.Specific.JNetHelper→Java.Lang.CharacterMASES.JNet.Specific.JNetHelper→Java.Lang.ClassMASES.JNet.Specific.JNetHelper→Java.Lang.DoubleMASES.JNet.Specific.JNetHelper→Java.Lang.FloatMASES.JNet.Specific.JNetHelper→Java.Lang.IntegerMASES.JNet.Specific.JNetHelper→Java.Lang.LongMASES.JNet.Specific.JNetHelper→Java.Lang.Short
- Direction
- MASES.JNet.Specific uses Java.Lang, so a change to Java.Lang can break MASES.JNet.Specific, while a change to MASES.JNet.Specific can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→4 Java.Security.Cert uses Java.Util✕
- Connections
- 38 pairs of types, where a type in Java.Security.Cert uses a type in Java.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Security.Cert.CertPath→Java.Util.IteratorJava.Security.Cert.CertPath→Java.Util.ListJava.Security.Cert.CertStore→Java.Util.CollectionJava.Security.Cert.CertStoreSpi→Java.Util.CollectionJava.Security.Cert.CertificateFactory→Java.Util.CollectionJava.Security.Cert.CertificateFactory→Java.Util.IteratorJava.Security.Cert.CertificateFactory→Java.Util.ListJava.Security.Cert.CertificateFactorySpi→Java.Util.CollectionJava.Security.Cert.CertificateFactorySpi→Java.Util.IteratorJava.Security.Cert.CertificateFactorySpi→Java.Util.ListJava.Security.Cert.CollectionCertStoreParameters→Java.Util.CollectionJava.Security.Cert.IPolicyNode→Java.Util.IteratorJava.Security.Cert.IPolicyNode→Java.Util.SetJava.Security.Cert.IX509Extension→Java.Util.SetJava.Security.Cert.PKIXBuilderParameters→Java.Util.SetJava.Security.Cert.PKIXCertPathChecker→Java.Util.CollectionJava.Security.Cert.PKIXCertPathChecker→Java.Util.SetJava.Security.Cert.PKIXParameters→Java.Util.DateJava.Security.Cert.PKIXParameters→Java.Util.ListJava.Security.Cert.PKIXParameters→Java.Util.SetJava.Security.Cert.PKIXRevocationChecker→Java.Util.ListJava.Security.Cert.PKIXRevocationChecker→Java.Util.MapJava.Security.Cert.PKIXRevocationChecker→Java.Util.SetJava.Security.Cert.PolicyNode→Java.Util.IteratorJava.Security.Cert.PolicyNode→Java.Util.Set
- Direction
- Java.Security.Cert uses Java.Util, so a change to Java.Util can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Util.
- Position
- Below the diagonal: Java.Security.Cert uses a module listed above it, which is the healthy direction.
7→5 Java.Security.Cert uses Java.Math✕
- Connections
- 5 pairs of types, where a type in Java.Security.Cert uses a type in Java.Math.
- The types involved
Java.Security.Cert.X509CRL→Java.Math.BigIntegerJava.Security.Cert.X509CRLEntry→Java.Math.BigIntegerJava.Security.Cert.X509CRLSelector→Java.Math.BigIntegerJava.Security.Cert.X509CertSelector→Java.Math.BigIntegerJava.Security.Cert.X509Certificate→Java.Math.BigInteger
- Direction
- Java.Security.Cert uses Java.Math, so a change to Java.Math can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Math.
- Position
- Below the diagonal: Java.Security.Cert uses a module listed above it, which is the healthy direction.
7→8 Java.Security.Cert uses Java.Security part of a loop✕
- Connections
- 21 pairs of types, where a type in Java.Security.Cert uses a type in Java.Security.
- The types involved
Java.Security.Cert.CRLException→Java.Security.GeneralSecurityExceptionJava.Security.Cert.CertPathBuilder→Java.Security.ProviderJava.Security.Cert.CertPathBuilderException→Java.Security.GeneralSecurityExceptionJava.Security.Cert.CertPathValidator→Java.Security.ProviderJava.Security.Cert.CertPathValidatorException→Java.Security.GeneralSecurityExceptionJava.Security.Cert.CertStore→Java.Security.ProviderJava.Security.Cert.CertStoreException→Java.Security.GeneralSecurityExceptionJava.Security.Cert.Certificate→Java.Security.ProviderJava.Security.Cert.Certificate→Java.Security.PublicKeyJava.Security.Cert.CertificateException→Java.Security.GeneralSecurityExceptionJava.Security.Cert.CertificateFactory→Java.Security.ProviderJava.Security.Cert.PKIXBuilderParameters→Java.Security.KeyStoreJava.Security.Cert.PKIXCertPathBuilderResult→Java.Security.PublicKeyJava.Security.Cert.PKIXCertPathValidatorResult→Java.Security.PublicKeyJava.Security.Cert.PKIXParameters→Java.Security.KeyStoreJava.Security.Cert.TrustAnchor→Java.Security.PublicKeyJava.Security.Cert.X509CRL→Java.Security.PrincipalJava.Security.Cert.X509CRL→Java.Security.ProviderJava.Security.Cert.X509CRL→Java.Security.PublicKeyJava.Security.Cert.X509CertSelector→Java.Security.PublicKeyJava.Security.Cert.X509Certificate→Java.Security.Principal
- Direction
- Java.Security.Cert uses Java.Security, so a change to Java.Security can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Security.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→13 Java.Security.Cert uses Java.Net part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Security.Cert uses a type in Java.Net.
- The types involved
Java.Security.Cert.PKIXRevocationChecker→Java.Net.URI
- Direction
- Java.Security.Cert uses Java.Net, so a change to Java.Net can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Net.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→14 Java.Security.Cert uses Java.Io part of a loop✕
- Connections
- 7 pairs of types, where a type in Java.Security.Cert uses a type in Java.Io.
- The types involved
Java.Security.Cert.CertPath→Java.Io.SerializableJava.Security.Cert.Certificate→Java.Io.SerializableJava.Security.Cert.CertificateFactory→Java.Io.InputStreamJava.Security.Cert.CertificateFactorySpi→Java.Io.InputStreamJava.Security.Cert.Extension→Java.Io.OutputStreamJava.Security.Cert.IExtension→Java.Io.OutputStreamJava.Security.Cert.Reason→Java.Io.Serializable
- Direction
- Java.Security.Cert uses Java.Io, so a change to Java.Io can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→16 Java.Security.Cert uses Java.Lang part of a loop✕
- Connections
- 44 pairs of types, where a type in Java.Security.Cert uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Security.Cert.BasicReason→Java.Lang.EnumJava.Security.Cert.BasicReason→Java.Lang.StringJava.Security.Cert.CRL→Java.Lang.StringJava.Security.Cert.CRLReason→Java.Lang.EnumJava.Security.Cert.CRLReason→Java.Lang.StringJava.Security.Cert.CRLSelector→Java.Lang.CloneableJava.Security.Cert.CertPath→Java.Lang.StringJava.Security.Cert.CertPathBuilder→Java.Lang.StringJava.Security.Cert.CertPathBuilderResult→Java.Lang.CloneableJava.Security.Cert.CertPathParameters→Java.Lang.CloneableJava.Security.Cert.CertPathValidator→Java.Lang.StringJava.Security.Cert.CertPathValidatorResult→Java.Lang.CloneableJava.Security.Cert.CertSelector→Java.Lang.CloneableJava.Security.Cert.CertStore→Java.Lang.StringJava.Security.Cert.CertStoreParameters→Java.Lang.CloneableJava.Security.Cert.Certificate→Java.Lang.StringJava.Security.Cert.CertificateFactory→Java.Lang.StringJava.Security.Cert.CertificateFactorySpi→Java.Lang.StringJava.Security.Cert.Extension→Java.Lang.StringJava.Security.Cert.ICRLSelector→Java.Lang.ICloneableJava.Security.Cert.ICertPathBuilderResult→Java.Lang.ICloneableJava.Security.Cert.ICertPathParameters→Java.Lang.ICloneableJava.Security.Cert.ICertPathValidatorResult→Java.Lang.ICloneableJava.Security.Cert.ICertSelector→Java.Lang.ICloneableJava.Security.Cert.ICertStoreParameters→Java.Lang.ICloneable
- Direction
- Java.Security.Cert uses Java.Lang, so a change to Java.Lang can break Java.Security.Cert, while a change to Java.Security.Cert can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→2 Java.Security uses Java.Nio✕
- Connections
- 2 pairs of types, where a type in Java.Security uses a type in Java.Nio.
- The types involved
Java.Security.MessageDigest→Java.Nio.ByteBufferJava.Security.Signature→Java.Nio.ByteBuffer
- Direction
- Java.Security uses Java.Nio, so a change to Java.Nio can break Java.Security, while a change to Java.Security can't break Java.Nio.
- Position
- Below the diagonal: Java.Security uses a module listed above it, which is the healthy direction.
8→4 Java.Security uses Java.Util✕
- Connections
- 21 pairs of types, where a type in Java.Security uses a type in Java.Util.
- The types involved
Java.Security.AlgorithmConstraints→Java.Util.SetJava.Security.DomainLoadStoreParameter→Java.Util.MapJava.Security.Entry→Java.Util.SetJava.Security.IAlgorithmConstraints→Java.Util.SetJava.Security.IdentityScope→Java.Util.EnumerationJava.Security.KeyStore→Java.Util.DateJava.Security.KeyStore→Java.Util.EnumerationJava.Security.KeyStoreSpi→Java.Util.DateJava.Security.KeyStoreSpi→Java.Util.EnumerationJava.Security.PermissionCollection→Java.Util.EnumerationJava.Security.PrivateKeyEntry→Java.Util.SetJava.Security.Provider→Java.Util.PropertiesJava.Security.Provider→Java.Util.SetJava.Security.SecretKeyEntry→Java.Util.SetJava.Security.SecureRandom→Java.Util.RandomJava.Security.Security→Java.Util.MapJava.Security.Security→Java.Util.SetJava.Security.Service→Java.Util.ListJava.Security.Service→Java.Util.MapJava.Security.Timestamp→Java.Util.DateJava.Security.TrustedCertificateEntry→Java.Util.Set
- Direction
- Java.Security uses Java.Util, so a change to Java.Util can break Java.Security, while a change to Java.Security can't break Java.Util.
- Position
- Below the diagonal: Java.Security uses a module listed above it, which is the healthy direction.
8→7 Java.Security uses Java.Security.Cert✕
- Connections
- 9 pairs of types, where a type in Java.Security uses a type in Java.Security.Cert.
- The types involved
Java.Security.CodeSigner→Java.Security.Cert.CertPathJava.Security.CodeSource→Java.Security.Cert.CertificateJava.Security.KeyStore→Java.Security.Cert.CertificateJava.Security.KeyStoreSpi→Java.Security.Cert.CertificateJava.Security.PrivateKeyEntry→Java.Security.Cert.CertificateJava.Security.Signature→Java.Security.Cert.CertificateJava.Security.Timestamp→Java.Security.Cert.CertPathJava.Security.TrustedCertificateEntry→Java.Security.Cert.CertificateJava.Security.UnresolvedPermission→Java.Security.Cert.Certificate
- Direction
- Java.Security uses Java.Security.Cert, so a change to Java.Security.Cert can break Java.Security, while a change to Java.Security can't break Java.Security.Cert.
- Position
- Below the diagonal: Java.Security uses a module listed above it, which is the healthy direction.
8→13 Java.Security uses Java.Net part of a loop✕
- Connections
- 3 pairs of types, where a type in Java.Security uses a type in Java.Net.
- The types involved
Java.Security.CodeSource→Java.Net.URLJava.Security.DomainLoadStoreParameter→Java.Net.URIJava.Security.URIParameter→Java.Net.URI
- Direction
- Java.Security uses Java.Net, so a change to Java.Net can break Java.Security, while a change to Java.Security can't break Java.Net.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→14 Java.Security uses Java.Io part of a loop✕
- Connections
- 26 pairs of types, where a type in Java.Security uses a type in Java.Io. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Security.Builder→Java.Io.FileJava.Security.Certificate→Java.Io.InputStreamJava.Security.Certificate→Java.Io.OutputStreamJava.Security.CodeSigner→Java.Io.SerializableJava.Security.CodeSource→Java.Io.SerializableJava.Security.DigestInputStream→Java.Io.FilterInputStreamJava.Security.DigestInputStream→Java.Io.InputStreamJava.Security.DigestOutputStream→Java.Io.FilterOutputStreamJava.Security.DigestOutputStream→Java.Io.OutputStreamJava.Security.GuardedObject→Java.Io.SerializableJava.Security.ICertificate→Java.Io.InputStreamJava.Security.ICertificate→Java.Io.OutputStreamJava.Security.IKey→Java.Io.ISerializableJava.Security.Identity→Java.Io.SerializableJava.Security.Key→Java.Io.SerializableJava.Security.KeyPair→Java.Io.SerializableJava.Security.KeyRep→Java.Io.SerializableJava.Security.KeyStore→Java.Io.InputStreamJava.Security.KeyStore→Java.Io.OutputStreamJava.Security.KeyStoreSpi→Java.Io.InputStreamJava.Security.KeyStoreSpi→Java.Io.OutputStreamJava.Security.Permission→Java.Io.SerializableJava.Security.PermissionCollection→Java.Io.SerializableJava.Security.SecureRandomSpi→Java.Io.SerializableJava.Security.SignedObject→Java.Io.Serializable
- Direction
- Java.Security uses Java.Io, so a change to Java.Io can break Java.Security, while a change to Java.Security can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→16 Java.Security uses Java.Lang part of a loop✕
- Connections
- 51 pairs of types, where a type in Java.Security uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Security.AccessControlException→Java.Lang.SecurityExceptionJava.Security.AlgorithmConstraints→Java.Lang.StringJava.Security.AlgorithmParameterGenerator→Java.Lang.StringJava.Security.AlgorithmParameters→Java.Lang.ClassJava.Security.AlgorithmParameters→Java.Lang.StringJava.Security.AllPermission→Java.Lang.StringJava.Security.Attribute→Java.Lang.StringJava.Security.BasicPermission→Java.Lang.StringJava.Security.Builder→Java.Lang.StringJava.Security.Certificate→Java.Lang.StringJava.Security.CryptoPrimitive→Java.Lang.EnumJava.Security.CryptoPrimitive→Java.Lang.StringJava.Security.DomainLoadStoreParameter→Java.Lang.StringJava.Security.GeneralSecurityException→Java.Lang.ExceptionJava.Security.IAlgorithmConstraints→Java.Lang.StringJava.Security.ICertificate→Java.Lang.StringJava.Security.IKey→Java.Lang.StringJava.Security.IPrincipal→Java.Lang.StringJava.Security.Identity→Java.Lang.StringJava.Security.IdentityScope→Java.Lang.StringJava.Security.InvalidParameterException→Java.Lang.IllegalArgumentExceptionJava.Security.Key→Java.Lang.StringJava.Security.KeyFactory→Java.Lang.ClassJava.Security.KeyFactory→Java.Lang.StringJava.Security.KeyPairGenerator→Java.Lang.String
- Direction
- Java.Security uses Java.Lang, so a change to Java.Lang can break Java.Security, while a change to Java.Security can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→4 Java.Util.Concurrent uses Java.Util✕
- Connections
- 73 pairs of types, where a type in Java.Util.Concurrent uses a type in Java.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Util.Concurrent.AbstractExecutorService→Java.Util.CollectionJava.Util.Concurrent.AbstractExecutorService→Java.Util.ListJava.Util.Concurrent.ArrayBlockingQueue→Java.Util.AbstractQueueJava.Util.Concurrent.ArrayBlockingQueue→Java.Util.CollectionJava.Util.Concurrent.BlockingDeque→Java.Util.DequeJava.Util.Concurrent.BlockingDeque→Java.Util.IteratorJava.Util.Concurrent.BlockingQueue→Java.Util.CollectionJava.Util.Concurrent.BlockingQueue→Java.Util.QueueJava.Util.Concurrent.ConcurrentHashMap→Java.Util.AbstractMapJava.Util.Concurrent.ConcurrentHashMap→Java.Util.EntryJava.Util.Concurrent.ConcurrentHashMap→Java.Util.EnumerationJava.Util.Concurrent.ConcurrentHashMap→Java.Util.MapJava.Util.Concurrent.ConcurrentLinkedDeque→Java.Util.AbstractCollectionJava.Util.Concurrent.ConcurrentLinkedDeque→Java.Util.CollectionJava.Util.Concurrent.ConcurrentLinkedDeque→Java.Util.DequeJava.Util.Concurrent.ConcurrentLinkedDeque→Java.Util.IteratorJava.Util.Concurrent.ConcurrentLinkedQueue→Java.Util.AbstractQueueJava.Util.Concurrent.ConcurrentLinkedQueue→Java.Util.CollectionJava.Util.Concurrent.ConcurrentMap→Java.Util.MapJava.Util.Concurrent.ConcurrentNavigableMap→Java.Util.NavigableMapJava.Util.Concurrent.ConcurrentNavigableMap→Java.Util.NavigableSetJava.Util.Concurrent.ConcurrentNavigableMap→Java.Util.SetJava.Util.Concurrent.ConcurrentNavigableMap→Java.Util.SortedMapJava.Util.Concurrent.ConcurrentSkipListMap→Java.Util.AbstractMapJava.Util.Concurrent.ConcurrentSkipListMap→Java.Util.Comparator
- Direction
- Java.Util.Concurrent uses Java.Util, so a change to Java.Util can break Java.Util.Concurrent, while a change to Java.Util.Concurrent can't break Java.Util.
- Position
- Below the diagonal: Java.Util.Concurrent uses a module listed above it, which is the healthy direction.
9→6 Java.Util.Concurrent uses MASES.JNet.Specific✕
- Connections
- 1 pair of types, where a type in Java.Util.Concurrent uses a type in MASES.JNet.Specific.
- The types involved
Java.Util.Concurrent.Callable→MASES.JNet.Specific.JNetEventData
- Direction
- Java.Util.Concurrent uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Java.Util.Concurrent, while a change to Java.Util.Concurrent can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Java.Util.Concurrent uses a module listed above it, which is the healthy direction.
9→8 Java.Util.Concurrent uses Java.Security✕
- Connections
- 2 pairs of types, where a type in Java.Util.Concurrent uses a type in Java.Security.
- The types involved
Java.Util.Concurrent.Executors→Java.Security.PrivilegedActionJava.Util.Concurrent.Executors→Java.Security.PrivilegedExceptionAction
- Direction
- Java.Util.Concurrent uses Java.Security, so a change to Java.Security can break Java.Util.Concurrent, while a change to Java.Util.Concurrent can't break Java.Security.
- Position
- Below the diagonal: Java.Util.Concurrent uses a module listed above it, which is the healthy direction.
9→14 Java.Util.Concurrent uses Java.Io part of a loop✕
- Connections
- 16 pairs of types, where a type in Java.Util.Concurrent uses a type in Java.Io.
- The types involved
Java.Util.Concurrent.ArrayBlockingQueue→Java.Io.SerializableJava.Util.Concurrent.ConcurrentHashMap→Java.Io.SerializableJava.Util.Concurrent.ConcurrentLinkedDeque→Java.Io.SerializableJava.Util.Concurrent.ConcurrentLinkedQueue→Java.Io.SerializableJava.Util.Concurrent.ConcurrentSkipListMap→Java.Io.SerializableJava.Util.Concurrent.ConcurrentSkipListSet→Java.Io.SerializableJava.Util.Concurrent.CopyOnWriteArrayList→Java.Io.SerializableJava.Util.Concurrent.CopyOnWriteArraySet→Java.Io.SerializableJava.Util.Concurrent.ForkJoinTask→Java.Io.SerializableJava.Util.Concurrent.KeySetView→Java.Io.SerializableJava.Util.Concurrent.LinkedBlockingDeque→Java.Io.SerializableJava.Util.Concurrent.LinkedBlockingQueue→Java.Io.SerializableJava.Util.Concurrent.LinkedTransferQueue→Java.Io.SerializableJava.Util.Concurrent.PriorityBlockingQueue→Java.Io.SerializableJava.Util.Concurrent.Semaphore→Java.Io.SerializableJava.Util.Concurrent.SynchronousQueue→Java.Io.Serializable
- Direction
- Java.Util.Concurrent uses Java.Io, so a change to Java.Io can break Java.Util.Concurrent, while a change to Java.Util.Concurrent can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→16 Java.Util.Concurrent uses Java.Lang part of a loop✕
- Connections
- 49 pairs of types, where a type in Java.Util.Concurrent uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Util.Concurrent.AbortPolicy→Java.Lang.RunnableJava.Util.Concurrent.AbstractExecutorService→Java.Lang.RunnableJava.Util.Concurrent.BrokenBarrierException→Java.Lang.ExceptionJava.Util.Concurrent.CallerRunsPolicy→Java.Lang.RunnableJava.Util.Concurrent.CancellationException→Java.Lang.IllegalStateExceptionJava.Util.Concurrent.CompletableFuture→Java.Lang.RunnableJava.Util.Concurrent.CompletionException→Java.Lang.RuntimeExceptionJava.Util.Concurrent.CompletionService→Java.Lang.RunnableJava.Util.Concurrent.CompletionStage→Java.Lang.RunnableJava.Util.Concurrent.ConcurrentSkipListMap→Java.Lang.CloneableJava.Util.Concurrent.ConcurrentSkipListSet→Java.Lang.CloneableJava.Util.Concurrent.CopyOnWriteArrayList→Java.Lang.CloneableJava.Util.Concurrent.CyclicBarrier→Java.Lang.RunnableJava.Util.Concurrent.Delayed→Java.Lang.ComparableJava.Util.Concurrent.DiscardOldestPolicy→Java.Lang.RunnableJava.Util.Concurrent.DiscardPolicy→Java.Lang.RunnableJava.Util.Concurrent.ExecutionException→Java.Lang.ExceptionJava.Util.Concurrent.Executor→Java.Lang.RunnableJava.Util.Concurrent.ExecutorCompletionService→Java.Lang.RunnableJava.Util.Concurrent.ExecutorService→Java.Lang.RunnableJava.Util.Concurrent.Executors→Java.Lang.RunnableJava.Util.Concurrent.ForkJoinPool→Java.Lang.UncaughtExceptionHandlerJava.Util.Concurrent.ForkJoinTask→Java.Lang.RunnableJava.Util.Concurrent.ForkJoinTask→Java.Lang.ThrowableJava.Util.Concurrent.ForkJoinWorkerThread→Java.Lang.Thread
- Direction
- Java.Util.Concurrent uses Java.Lang, so a change to Java.Lang can break Java.Util.Concurrent, while a change to Java.Util.Concurrent can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→2 Java.Nio.File.Attribute uses Java.Nio✕
- Connections
- 2 pairs of types, where a type in Java.Nio.File.Attribute uses a type in Java.Nio.
- The types involved
Java.Nio.File.Attribute.IUserDefinedFileAttributeView→Java.Nio.ByteBufferJava.Nio.File.Attribute.UserDefinedFileAttributeView→Java.Nio.ByteBuffer
- Direction
- Java.Nio.File.Attribute uses Java.Nio, so a change to Java.Nio can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Nio.
- Position
- Below the diagonal: Java.Nio.File.Attribute uses a module listed above it, which is the healthy direction.
10→3 Java.Nio.File.Attribute uses Java.Time✕
- Connections
- 1 pair of types, where a type in Java.Nio.File.Attribute uses a type in Java.Time.
- The types involved
Java.Nio.File.Attribute.FileTime→Java.Time.Instant
- Direction
- Java.Nio.File.Attribute uses Java.Time, so a change to Java.Time can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Time.
- Position
- Below the diagonal: Java.Nio.File.Attribute uses a module listed above it, which is the healthy direction.
10→4 Java.Nio.File.Attribute uses Java.Util✕
- Connections
- 11 pairs of types, where a type in Java.Nio.File.Attribute uses a type in Java.Util.
- The types involved
Java.Nio.File.Attribute.AclEntry→Java.Util.SetJava.Nio.File.Attribute.AclFileAttributeView→Java.Util.ListJava.Nio.File.Attribute.Builder→Java.Util.SetJava.Nio.File.Attribute.IAclFileAttributeView→Java.Util.ListJava.Nio.File.Attribute.IPosixFileAttributeView→Java.Util.SetJava.Nio.File.Attribute.IPosixFileAttributes→Java.Util.SetJava.Nio.File.Attribute.IUserDefinedFileAttributeView→Java.Util.ListJava.Nio.File.Attribute.PosixFileAttributeView→Java.Util.SetJava.Nio.File.Attribute.PosixFileAttributes→Java.Util.SetJava.Nio.File.Attribute.PosixFilePermissions→Java.Util.SetJava.Nio.File.Attribute.UserDefinedFileAttributeView→Java.Util.List
- Direction
- Java.Nio.File.Attribute uses Java.Util, so a change to Java.Util can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Util.
- Position
- Below the diagonal: Java.Nio.File.Attribute uses a module listed above it, which is the healthy direction.
10→8 Java.Nio.File.Attribute uses Java.Security✕
- Connections
- 2 pairs of types, where a type in Java.Nio.File.Attribute uses a type in Java.Security.
- The types involved
Java.Nio.File.Attribute.IUserPrincipal→Java.Security.IPrincipalJava.Nio.File.Attribute.UserPrincipal→Java.Security.Principal
- Direction
- Java.Nio.File.Attribute uses Java.Security, so a change to Java.Security can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Security.
- Position
- Below the diagonal: Java.Nio.File.Attribute uses a module listed above it, which is the healthy direction.
10→9 Java.Nio.File.Attribute uses Java.Util.Concurrent✕
- Connections
- 1 pair of types, where a type in Java.Nio.File.Attribute uses a type in Java.Util.Concurrent.
- The types involved
Java.Nio.File.Attribute.FileTime→Java.Util.Concurrent.TimeUnit
- Direction
- Java.Nio.File.Attribute uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Java.Nio.File.Attribute uses a module listed above it, which is the healthy direction.
10→14 Java.Nio.File.Attribute uses Java.Io part of a loop✕
- Connections
- 1 pair of types, where a type in Java.Nio.File.Attribute uses a type in Java.Io.
- The types involved
Java.Nio.File.Attribute.UserPrincipalNotFoundException→Java.Io.IOException
- Direction
- Java.Nio.File.Attribute uses Java.Io, so a change to Java.Io can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→16 Java.Nio.File.Attribute uses Java.Lang part of a loop✕
- Connections
- 27 pairs of types, where a type in Java.Nio.File.Attribute uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Nio.File.Attribute.AclEntryFlag→Java.Lang.EnumJava.Nio.File.Attribute.AclEntryFlag→Java.Lang.StringJava.Nio.File.Attribute.AclEntryPermission→Java.Lang.EnumJava.Nio.File.Attribute.AclEntryPermission→Java.Lang.StringJava.Nio.File.Attribute.AclEntryType→Java.Lang.EnumJava.Nio.File.Attribute.AclEntryType→Java.Lang.StringJava.Nio.File.Attribute.AclFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.AttributeView→Java.Lang.StringJava.Nio.File.Attribute.BasicFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.DosFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.FileAttribute→Java.Lang.StringJava.Nio.File.Attribute.FileOwnerAttributeView→Java.Lang.StringJava.Nio.File.Attribute.FileTime→Java.Lang.ComparableJava.Nio.File.Attribute.IAclFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IBasicFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IDosFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IFileAttribute→Java.Lang.StringJava.Nio.File.Attribute.IFileOwnerAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IPosixFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.IUserDefinedFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.PosixFileAttributeView→Java.Lang.StringJava.Nio.File.Attribute.PosixFilePermission→Java.Lang.EnumJava.Nio.File.Attribute.PosixFilePermission→Java.Lang.StringJava.Nio.File.Attribute.PosixFilePermissions→Java.Lang.String
- Direction
- Java.Nio.File.Attribute uses Java.Lang, so a change to Java.Lang can break Java.Nio.File.Attribute, while a change to Java.Nio.File.Attribute can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→4 Java.Nio.File uses Java.Util✕
- Connections
- 14 pairs of types, where a type in Java.Nio.File uses a type in Java.Util.
- The types involved
Java.Nio.File.DirectoryIteratorException→Java.Util.ConcurrentModificationExceptionJava.Nio.File.DirectoryStream→Java.Util.IteratorJava.Nio.File.FileSystem→Java.Util.SetJava.Nio.File.FileSystems→Java.Util.MapJava.Nio.File.Files→Java.Util.ListJava.Nio.File.Files→Java.Util.MapJava.Nio.File.Files→Java.Util.SetJava.Nio.File.IDirectoryStream→Java.Util.IteratorJava.Nio.File.IPath→Java.Util.IteratorJava.Nio.File.ISecureDirectoryStream→Java.Util.SetJava.Nio.File.IWatchKey→Java.Util.ListJava.Nio.File.Path→Java.Util.IteratorJava.Nio.File.SecureDirectoryStream→Java.Util.SetJava.Nio.File.WatchKey→Java.Util.List
- Direction
- Java.Nio.File uses Java.Util, so a change to Java.Util can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Util.
- Position
- Below the diagonal: Java.Nio.File uses a module listed above it, which is the healthy direction.
11→8 Java.Nio.File uses Java.Security✕
- Connections
- 1 pair of types, where a type in Java.Nio.File uses a type in Java.Security.
- The types involved
Java.Nio.File.LinkPermission→Java.Security.BasicPermission
- Direction
- Java.Nio.File uses Java.Security, so a change to Java.Security can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Security.
- Position
- Below the diagonal: Java.Nio.File uses a module listed above it, which is the healthy direction.
11→9 Java.Nio.File uses Java.Util.Concurrent✕
- Connections
- 2 pairs of types, where a type in Java.Nio.File uses a type in Java.Util.Concurrent.
- The types involved
Java.Nio.File.IWatchService→Java.Util.Concurrent.TimeUnitJava.Nio.File.WatchService→Java.Util.Concurrent.TimeUnit
- Direction
- Java.Nio.File uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Java.Nio.File uses a module listed above it, which is the healthy direction.
11→10 Java.Nio.File uses Java.Nio.File.Attribute✕
- Connections
- 12 pairs of types, where a type in Java.Nio.File uses a type in Java.Nio.File.Attribute.
- The types involved
Java.Nio.File.FileSystem→Java.Nio.File.Attribute.UserPrincipalLookupServiceJava.Nio.File.FileVisitor→Java.Nio.File.Attribute.BasicFileAttributesJava.Nio.File.Files→Java.Nio.File.Attribute.BasicFileAttributesJava.Nio.File.Files→Java.Nio.File.Attribute.FileAttributeJava.Nio.File.Files→Java.Nio.File.Attribute.FileTimeJava.Nio.File.Files→Java.Nio.File.Attribute.PosixFilePermissionJava.Nio.File.Files→Java.Nio.File.Attribute.UserPrincipalJava.Nio.File.IFileVisitor→Java.Nio.File.Attribute.BasicFileAttributesJava.Nio.File.ISecureDirectoryStream→Java.Nio.File.Attribute.FileAttributeJava.Nio.File.SecureDirectoryStream→Java.Nio.File.Attribute.FileAttributeJava.Nio.File.SecureDirectoryStream→Java.Nio.File.Attribute.FileAttributeViewJava.Nio.File.SimpleFileVisitor→Java.Nio.File.Attribute.BasicFileAttributes
- Direction
- Java.Nio.File uses Java.Nio.File.Attribute, so a change to Java.Nio.File.Attribute can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Nio.File.Attribute.
- Position
- Below the diagonal: Java.Nio.File uses a module listed above it, which is the healthy direction.
11→12 Java.Nio.File uses Java.Nio.Channels part of a loop✕
- Connections
- 3 pairs of types, where a type in Java.Nio.File uses a type in Java.Nio.Channels.
- The types involved
Java.Nio.File.Files→Java.Nio.Channels.SeekableByteChannelJava.Nio.File.ISecureDirectoryStream→Java.Nio.Channels.SeekableByteChannelJava.Nio.File.SecureDirectoryStream→Java.Nio.Channels.SeekableByteChannel
- Direction
- Java.Nio.File uses Java.Nio.Channels, so a change to Java.Nio.Channels can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Nio.Channels.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→13 Java.Nio.File uses Java.Net part of a loop✕
- Connections
- 4 pairs of types, where a type in Java.Nio.File uses a type in Java.Net.
- The types involved
Java.Nio.File.FileSystems→Java.Net.URIJava.Nio.File.IPath→Java.Net.URIJava.Nio.File.Path→Java.Net.URIJava.Nio.File.Paths→Java.Net.URI
- Direction
- Java.Nio.File uses Java.Net, so a change to Java.Net can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Net.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→14 Java.Nio.File uses Java.Io part of a loop✕
- Connections
- 11 pairs of types, where a type in Java.Nio.File uses a type in Java.Io.
- The types involved
Java.Nio.File.DirectoryStream→Java.Io.CloseableJava.Nio.File.FileSystem→Java.Io.CloseableJava.Nio.File.FileSystemException→Java.Io.IOExceptionJava.Nio.File.Files→Java.Io.BufferedReaderJava.Nio.File.Files→Java.Io.BufferedWriterJava.Nio.File.Files→Java.Io.InputStreamJava.Nio.File.Files→Java.Io.OutputStreamJava.Nio.File.IPath→Java.Io.FileJava.Nio.File.IWatchService→Java.Io.ICloseableJava.Nio.File.Path→Java.Io.FileJava.Nio.File.WatchService→Java.Io.Closeable
- Direction
- Java.Nio.File uses Java.Io, so a change to Java.Io can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→16 Java.Nio.File uses Java.Lang part of a loop✕
- Connections
- 42 pairs of types, where a type in Java.Nio.File uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Nio.File.AccessMode→Java.Lang.EnumJava.Nio.File.AccessMode→Java.Lang.StringJava.Nio.File.ClosedDirectoryStreamException→Java.Lang.IllegalStateExceptionJava.Nio.File.ClosedFileSystemException→Java.Lang.IllegalStateExceptionJava.Nio.File.ClosedWatchServiceException→Java.Lang.IllegalStateExceptionJava.Nio.File.DirectoryStream→Java.Lang.IterableJava.Nio.File.FileStore→Java.Lang.ClassJava.Nio.File.FileStore→Java.Lang.StringJava.Nio.File.FileSystem→Java.Lang.IterableJava.Nio.File.FileSystem→Java.Lang.StringJava.Nio.File.FileSystemAlreadyExistsException→Java.Lang.RuntimeExceptionJava.Nio.File.FileSystemNotFoundException→Java.Lang.RuntimeExceptionJava.Nio.File.FileSystems→Java.Lang.ClassLoaderJava.Nio.File.FileSystems→Java.Lang.StringJava.Nio.File.FileVisitOption→Java.Lang.EnumJava.Nio.File.FileVisitOption→Java.Lang.StringJava.Nio.File.FileVisitResult→Java.Lang.EnumJava.Nio.File.FileVisitResult→Java.Lang.StringJava.Nio.File.Files→Java.Lang.ClassJava.Nio.File.Files→Java.Lang.IterableJava.Nio.File.Files→Java.Lang.StringJava.Nio.File.IPath→Java.Lang.StringJava.Nio.File.ISecureDirectoryStream→Java.Lang.ClassJava.Nio.File.InvalidPathException→Java.Lang.IllegalArgumentExceptionJava.Nio.File.Kind→Java.Lang.Class
- Direction
- Java.Nio.File uses Java.Lang, so a change to Java.Lang can break Java.Nio.File, while a change to Java.Nio.File can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→2 Java.Nio.Channels uses Java.Nio✕
- Connections
- 18 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Nio.
- The types involved
Java.Nio.Channels.AsynchronousByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.AsynchronousFileChannel→Java.Nio.ByteBufferJava.Nio.Channels.AsynchronousSocketChannel→Java.Nio.ByteBufferJava.Nio.Channels.DatagramChannel→Java.Nio.ByteBufferJava.Nio.Channels.FileChannel→Java.Nio.ByteBufferJava.Nio.Channels.FileChannel→Java.Nio.MappedByteBufferJava.Nio.Channels.GatheringByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.IAsynchronousByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.IGatheringByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.IReadableByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.IScatteringByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.ISeekableByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.IWritableByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.ReadableByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.ScatteringByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.SeekableByteChannel→Java.Nio.ByteBufferJava.Nio.Channels.SocketChannel→Java.Nio.ByteBufferJava.Nio.Channels.WritableByteChannel→Java.Nio.ByteBuffer
- Direction
- Java.Nio.Channels uses Java.Nio, so a change to Java.Nio can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Nio.
- Position
- Below the diagonal: Java.Nio.Channels uses a module listed above it, which is the healthy direction.
12→4 Java.Nio.Channels uses Java.Util✕
- Connections
- 5 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Util.
- The types involved
Java.Nio.Channels.AsynchronousFileChannel→Java.Util.SetJava.Nio.Channels.FileChannel→Java.Util.SetJava.Nio.Channels.INetworkChannel→Java.Util.SetJava.Nio.Channels.NetworkChannel→Java.Util.SetJava.Nio.Channels.Selector→Java.Util.Set
- Direction
- Java.Nio.Channels uses Java.Util, so a change to Java.Util can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Util.
- Position
- Below the diagonal: Java.Nio.Channels uses a module listed above it, which is the healthy direction.
12→9 Java.Nio.Channels uses Java.Util.Concurrent✕
- Connections
- 10 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Util.Concurrent.
- The types involved
Java.Nio.Channels.AsynchronousByteChannel→Java.Util.Concurrent.FutureJava.Nio.Channels.AsynchronousChannelGroup→Java.Util.Concurrent.ExecutorServiceJava.Nio.Channels.AsynchronousChannelGroup→Java.Util.Concurrent.ThreadFactoryJava.Nio.Channels.AsynchronousChannelGroup→Java.Util.Concurrent.TimeUnitJava.Nio.Channels.AsynchronousFileChannel→Java.Util.Concurrent.ExecutorServiceJava.Nio.Channels.AsynchronousFileChannel→Java.Util.Concurrent.FutureJava.Nio.Channels.AsynchronousServerSocketChannel→Java.Util.Concurrent.FutureJava.Nio.Channels.AsynchronousSocketChannel→Java.Util.Concurrent.FutureJava.Nio.Channels.AsynchronousSocketChannel→Java.Util.Concurrent.TimeUnitJava.Nio.Channels.IAsynchronousByteChannel→Java.Util.Concurrent.Future
- Direction
- Java.Nio.Channels uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Java.Nio.Channels uses a module listed above it, which is the healthy direction.
12→10 Java.Nio.Channels uses Java.Nio.File.Attribute✕
- Connections
- 2 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Nio.File.Attribute.
- The types involved
Java.Nio.Channels.AsynchronousFileChannel→Java.Nio.File.Attribute.FileAttributeJava.Nio.Channels.FileChannel→Java.Nio.File.Attribute.FileAttribute
- Direction
- Java.Nio.Channels uses Java.Nio.File.Attribute, so a change to Java.Nio.File.Attribute can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Nio.File.Attribute.
- Position
- Below the diagonal: Java.Nio.Channels uses a module listed above it, which is the healthy direction.
12→11 Java.Nio.Channels uses Java.Nio.File✕
- Connections
- 4 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Nio.File.
- The types involved
Java.Nio.Channels.AsynchronousFileChannel→Java.Nio.File.OpenOptionJava.Nio.Channels.AsynchronousFileChannel→Java.Nio.File.PathJava.Nio.Channels.FileChannel→Java.Nio.File.OpenOptionJava.Nio.Channels.FileChannel→Java.Nio.File.Path
- Direction
- Java.Nio.Channels uses Java.Nio.File, so a change to Java.Nio.File can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Nio.File.
- Position
- Below the diagonal: Java.Nio.Channels uses a module listed above it, which is the healthy direction.
12→13 Java.Nio.Channels uses Java.Net part of a loop✕
- Connections
- 24 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Net.
- The types involved
Java.Nio.Channels.AsynchronousServerSocketChannel→Java.Net.SocketAddressJava.Nio.Channels.AsynchronousServerSocketChannel→Java.Net.SocketOptionJava.Nio.Channels.AsynchronousSocketChannel→Java.Net.SocketAddressJava.Nio.Channels.AsynchronousSocketChannel→Java.Net.SocketOptionJava.Nio.Channels.DatagramChannel→Java.Net.DatagramSocketJava.Nio.Channels.DatagramChannel→Java.Net.ProtocolFamilyJava.Nio.Channels.DatagramChannel→Java.Net.SocketAddressJava.Nio.Channels.DatagramChannel→Java.Net.SocketOptionJava.Nio.Channels.IMulticastChannel→Java.Net.InetAddressJava.Nio.Channels.IMulticastChannel→Java.Net.NetworkInterfaceJava.Nio.Channels.INetworkChannel→Java.Net.SocketAddressJava.Nio.Channels.INetworkChannel→Java.Net.SocketOptionJava.Nio.Channels.MembershipKey→Java.Net.InetAddressJava.Nio.Channels.MembershipKey→Java.Net.NetworkInterfaceJava.Nio.Channels.MulticastChannel→Java.Net.InetAddressJava.Nio.Channels.MulticastChannel→Java.Net.NetworkInterfaceJava.Nio.Channels.NetworkChannel→Java.Net.SocketAddressJava.Nio.Channels.NetworkChannel→Java.Net.SocketOptionJava.Nio.Channels.ServerSocketChannel→Java.Net.ServerSocketJava.Nio.Channels.ServerSocketChannel→Java.Net.SocketAddressJava.Nio.Channels.ServerSocketChannel→Java.Net.SocketOptionJava.Nio.Channels.SocketChannel→Java.Net.SocketJava.Nio.Channels.SocketChannel→Java.Net.SocketAddressJava.Nio.Channels.SocketChannel→Java.Net.SocketOption
- Direction
- Java.Nio.Channels uses Java.Net, so a change to Java.Net can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Net.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→14 Java.Nio.Channels uses Java.Io part of a loop✕
- Connections
- 10 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Io.
- The types involved
Java.Nio.Channels.Channel→Java.Io.CloseableJava.Nio.Channels.Channels→Java.Io.InputStreamJava.Nio.Channels.Channels→Java.Io.OutputStreamJava.Nio.Channels.Channels→Java.Io.ReaderJava.Nio.Channels.Channels→Java.Io.WriterJava.Nio.Channels.ClosedChannelException→Java.Io.IOExceptionJava.Nio.Channels.FileLockInterruptionException→Java.Io.IOExceptionJava.Nio.Channels.IChannel→Java.Io.ICloseableJava.Nio.Channels.InterruptedByTimeoutException→Java.Io.IOExceptionJava.Nio.Channels.Selector→Java.Io.Closeable
- Direction
- Java.Nio.Channels uses Java.Io, so a change to Java.Io can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→16 Java.Nio.Channels uses Java.Lang part of a loop✕
- Connections
- 28 pairs of types, where a type in Java.Nio.Channels uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Nio.Channels.AcceptPendingException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.AlreadyBoundException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.AlreadyConnectedException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.AsynchronousByteChannel→Java.Lang.IntegerJava.Nio.Channels.AsynchronousFileChannel→Java.Lang.IntegerJava.Nio.Channels.AsynchronousSocketChannel→Java.Lang.IntegerJava.Nio.Channels.AsynchronousSocketChannel→Java.Lang.LongJava.Nio.Channels.AsynchronousSocketChannel→Java.Lang.VoidJava.Nio.Channels.CancelledKeyException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.Channels→Java.Lang.StringJava.Nio.Channels.ClosedSelectorException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.ConnectionPendingException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.FileLock→Java.Lang.AutoCloseableJava.Nio.Channels.IAsynchronousByteChannel→Java.Lang.IntegerJava.Nio.Channels.IllegalBlockingModeException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.IllegalChannelGroupException→Java.Lang.IllegalArgumentExceptionJava.Nio.Channels.IllegalSelectorException→Java.Lang.IllegalArgumentExceptionJava.Nio.Channels.NoConnectionPendingException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.NonReadableChannelException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.NonWritableChannelException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.NotYetBoundException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.NotYetConnectedException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.OverlappingFileLockException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.ReadPendingException→Java.Lang.IllegalStateExceptionJava.Nio.Channels.ShutdownChannelGroupException→Java.Lang.IllegalStateException
- Direction
- Java.Nio.Channels uses Java.Lang, so a change to Java.Lang can break Java.Nio.Channels, while a change to Java.Nio.Channels can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→4 Java.Net uses Java.Util✕
- Connections
- 16 pairs of types, where a type in Java.Net uses a type in Java.Util.
- The types involved
Java.Net.CacheResponse→Java.Util.ListJava.Net.CacheResponse→Java.Util.MapJava.Net.CookieHandler→Java.Util.ListJava.Net.CookieHandler→Java.Util.MapJava.Net.CookieStore→Java.Util.ListJava.Net.HttpCookie→Java.Util.ListJava.Net.ICookieStore→Java.Util.ListJava.Net.NetworkInterface→Java.Util.EnumerationJava.Net.NetworkInterface→Java.Util.ListJava.Net.ProxySelector→Java.Util.ListJava.Net.ResponseCache→Java.Util.ListJava.Net.ResponseCache→Java.Util.MapJava.Net.SecureCacheResponse→Java.Util.ListJava.Net.URLClassLoader→Java.Util.EnumerationJava.Net.URLConnection→Java.Util.ListJava.Net.URLConnection→Java.Util.Map
- Direction
- Java.Net uses Java.Util, so a change to Java.Util can break Java.Net, while a change to Java.Net can't break Java.Util.
- Position
- Below the diagonal: Java.Net uses a module listed above it, which is the healthy direction.
13→7 Java.Net uses Java.Security.Cert✕
- Connections
- 2 pairs of types, where a type in Java.Net uses a type in Java.Security.Cert.
- The types involved
Java.Net.JarURLConnection→Java.Security.Cert.CertificateJava.Net.SecureCacheResponse→Java.Security.Cert.Certificate
- Direction
- Java.Net uses Java.Security.Cert, so a change to Java.Security.Cert can break Java.Net, while a change to Java.Net can't break Java.Security.Cert.
- Position
- Below the diagonal: Java.Net uses a module listed above it, which is the healthy direction.
13→8 Java.Net uses Java.Security✕
- Connections
- 6 pairs of types, where a type in Java.Net uses a type in Java.Security.
- The types involved
Java.Net.NetPermission→Java.Security.BasicPermissionJava.Net.SecureCacheResponse→Java.Security.PrincipalJava.Net.SocketPermission→Java.Security.PermissionJava.Net.URLClassLoader→Java.Security.SecureClassLoaderJava.Net.URLConnection→Java.Security.PermissionJava.Net.URLPermission→Java.Security.Permission
- Direction
- Java.Net uses Java.Security, so a change to Java.Security can break Java.Net, while a change to Java.Net can't break Java.Security.
- Position
- Below the diagonal: Java.Net uses a module listed above it, which is the healthy direction.
13→12 Java.Net uses Java.Nio.Channels✕
- Connections
- 3 pairs of types, where a type in Java.Net uses a type in Java.Nio.Channels.
- The types involved
Java.Net.DatagramSocket→Java.Nio.Channels.DatagramChannelJava.Net.ServerSocket→Java.Nio.Channels.ServerSocketChannelJava.Net.Socket→Java.Nio.Channels.SocketChannel
- Direction
- Java.Net uses Java.Nio.Channels, so a change to Java.Nio.Channels can break Java.Net, while a change to Java.Net can't break Java.Nio.Channels.
- Position
- Below the diagonal: Java.Net uses a module listed above it, which is the healthy direction.
13→14 Java.Net uses Java.Io part of a loop✕
- Connections
- 23 pairs of types, where a type in Java.Net uses a type in Java.Io.
- The types involved
Java.Net.CacheRequest→Java.Io.OutputStreamJava.Net.CacheResponse→Java.Io.InputStreamJava.Net.DatagramSocket→Java.Io.CloseableJava.Net.HttpRetryException→Java.Io.IOExceptionJava.Net.HttpURLConnection→Java.Io.InputStreamJava.Net.InetAddress→Java.Io.SerializableJava.Net.MalformedURLException→Java.Io.IOExceptionJava.Net.ProtocolException→Java.Io.IOExceptionJava.Net.ServerSocket→Java.Io.CloseableJava.Net.Socket→Java.Io.CloseableJava.Net.Socket→Java.Io.InputStreamJava.Net.Socket→Java.Io.OutputStreamJava.Net.SocketAddress→Java.Io.SerializableJava.Net.SocketException→Java.Io.IOExceptionJava.Net.SocketTimeoutException→Java.Io.InterruptedIOExceptionJava.Net.URI→Java.Io.SerializableJava.Net.URL→Java.Io.InputStreamJava.Net.URL→Java.Io.SerializableJava.Net.URLClassLoader→Java.Io.CloseableJava.Net.URLConnection→Java.Io.InputStreamJava.Net.URLConnection→Java.Io.OutputStreamJava.Net.UnknownHostException→Java.Io.IOExceptionJava.Net.UnknownServiceException→Java.Io.IOException
- Direction
- Java.Net uses Java.Io, so a change to Java.Io can break Java.Net, while a change to Java.Net can't break Java.Io.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→16 Java.Net uses Java.Lang part of a loop✕
- Connections
- 49 pairs of types, where a type in Java.Net uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Net.Authenticator→Java.Lang.StringJava.Net.CacheResponse→Java.Lang.StringJava.Net.ContentHandler→Java.Lang.ClassJava.Net.ContentHandlerFactory→Java.Lang.StringJava.Net.CookieHandler→Java.Lang.StringJava.Net.FileNameMap→Java.Lang.StringJava.Net.HttpCookie→Java.Lang.CloneableJava.Net.HttpCookie→Java.Lang.StringJava.Net.HttpURLConnection→Java.Lang.StringJava.Net.IContentHandlerFactory→Java.Lang.StringJava.Net.IDN→Java.Lang.StringJava.Net.IFileNameMap→Java.Lang.StringJava.Net.IProtocolFamily→Java.Lang.StringJava.Net.ISocketOption→Java.Lang.ClassJava.Net.ISocketOption→Java.Lang.StringJava.Net.IURLStreamHandlerFactory→Java.Lang.StringJava.Net.Inet6Address→Java.Lang.StringJava.Net.InetAddress→Java.Lang.StringJava.Net.InetSocketAddress→Java.Lang.StringJava.Net.JarURLConnection→Java.Lang.StringJava.Net.NetPermission→Java.Lang.StringJava.Net.NetworkInterface→Java.Lang.StringJava.Net.PasswordAuthentication→Java.Lang.StringJava.Net.ProtocolFamily→Java.Lang.StringJava.Net.RequestorType→Java.Lang.Enum
- Direction
- Java.Net uses Java.Lang, so a change to Java.Lang can break Java.Net, while a change to Java.Net can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→2 Java.Io uses Java.Nio✕
- Connections
- 1 pair of types, where a type in Java.Io uses a type in Java.Nio.
- The types involved
Java.Io.Reader→Java.Nio.CharBuffer
- Direction
- Java.Io uses Java.Nio, so a change to Java.Nio can break Java.Io, while a change to Java.Io can't break Java.Nio.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→4 Java.Io uses Java.Util✕
- Connections
- 3 pairs of types, where a type in Java.Io uses a type in Java.Util.
- The types involved
Java.Io.PrintStream→Java.Util.LocaleJava.Io.PrintWriter→Java.Util.LocaleJava.Io.SequenceInputStream→Java.Util.Enumeration
- Direction
- Java.Io uses Java.Util, so a change to Java.Util can break Java.Io, while a change to Java.Io can't break Java.Util.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→8 Java.Io uses Java.Security✕
- Connections
- 2 pairs of types, where a type in Java.Io uses a type in Java.Security.
- The types involved
Java.Io.FilePermission→Java.Security.PermissionJava.Io.SerializablePermission→Java.Security.BasicPermission
- Direction
- Java.Io uses Java.Security, so a change to Java.Security can break Java.Io, while a change to Java.Io can't break Java.Security.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→11 Java.Io uses Java.Nio.File✕
- Connections
- 1 pair of types, where a type in Java.Io uses a type in Java.Nio.File.
- The types involved
Java.Io.File→Java.Nio.File.Path
- Direction
- Java.Io uses Java.Nio.File, so a change to Java.Nio.File can break Java.Io, while a change to Java.Io can't break Java.Nio.File.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→12 Java.Io uses Java.Nio.Channels✕
- Connections
- 3 pairs of types, where a type in Java.Io uses a type in Java.Nio.Channels.
- The types involved
Java.Io.FileInputStream→Java.Nio.Channels.FileChannelJava.Io.FileOutputStream→Java.Nio.Channels.FileChannelJava.Io.RandomAccessFile→Java.Nio.Channels.FileChannel
- Direction
- Java.Io uses Java.Nio.Channels, so a change to Java.Nio.Channels can break Java.Io, while a change to Java.Io can't break Java.Nio.Channels.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→13 Java.Io uses Java.Net✕
- Connections
- 2 pairs of types, where a type in Java.Io uses a type in Java.Net.
- The types involved
Java.Io.File→Java.Net.URIJava.Io.File→Java.Net.URL
- Direction
- Java.Io uses Java.Net, so a change to Java.Net can break Java.Io, while a change to Java.Io can't break Java.Net.
- Position
- Below the diagonal: Java.Io uses a module listed above it, which is the healthy direction.
14→16 Java.Io uses Java.Lang part of a loop✕
- Connections
- 50 pairs of types, where a type in Java.Io uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Io.BufferedReader→Java.Lang.StringJava.Io.ByteArrayOutputStream→Java.Lang.StringJava.Io.Closeable→Java.Lang.AutoCloseableJava.Io.Console→Java.Lang.StringJava.Io.DataInput→Java.Lang.StringJava.Io.DataInputStream→Java.Lang.StringJava.Io.DataOutput→Java.Lang.StringJava.Io.DataOutputStream→Java.Lang.StringJava.Io.File→Java.Lang.ComparableJava.Io.File→Java.Lang.StringJava.Io.FileInputStream→Java.Lang.StringJava.Io.FileOutputStream→Java.Lang.StringJava.Io.FilePermission→Java.Lang.StringJava.Io.FileReader→Java.Lang.StringJava.Io.FileWriter→Java.Lang.StringJava.Io.FilenameFilter→Java.Lang.StringJava.Io.GetField→Java.Lang.StringJava.Io.ICloseable→Java.Lang.IAutoCloseableJava.Io.IDataInput→Java.Lang.StringJava.Io.IDataOutput→Java.Lang.StringJava.Io.IFilenameFilter→Java.Lang.StringJava.Io.IOError→Java.Lang.ErrorJava.Io.IOException→Java.Lang.ExceptionJava.Io.InputStreamReader→Java.Lang.StringJava.Io.ObjectInput→Java.Lang.AutoCloseable
- Direction
- Java.Io uses Java.Lang, so a change to Java.Lang can break Java.Io, while a change to Java.Io can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→1 Java.Lang.Reflect uses Java.Lang.Annotation✕
- Connections
- 5 pairs of types, where a type in Java.Lang.Reflect uses a type in Java.Lang.Annotation.
- The types involved
Java.Lang.Reflect.AccessibleObject→Java.Lang.Annotation.AnnotationJava.Lang.Reflect.AnnotatedElement→Java.Lang.Annotation.AnnotationJava.Lang.Reflect.Executable→Java.Lang.Annotation.AnnotationJava.Lang.Reflect.IAnnotatedElement→Java.Lang.Annotation.AnnotationJava.Lang.Reflect.Parameter→Java.Lang.Annotation.Annotation
- Direction
- Java.Lang.Reflect uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Java.Lang.Reflect, while a change to Java.Lang.Reflect can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Java.Lang.Reflect uses a module listed above it, which is the healthy direction.
15→8 Java.Lang.Reflect uses Java.Security✕
- Connections
- 1 pair of types, where a type in Java.Lang.Reflect uses a type in Java.Security.
- The types involved
Java.Lang.Reflect.ReflectPermission→Java.Security.BasicPermission
- Direction
- Java.Lang.Reflect uses Java.Security, so a change to Java.Security can break Java.Lang.Reflect, while a change to Java.Lang.Reflect can't break Java.Security.
- Position
- Below the diagonal: Java.Lang.Reflect uses a module listed above it, which is the healthy direction.
15→14 Java.Lang.Reflect uses Java.Io✕
- Connections
- 1 pair of types, where a type in Java.Lang.Reflect uses a type in Java.Io.
- The types involved
Java.Lang.Reflect.Proxy→Java.Io.Serializable
- Direction
- Java.Lang.Reflect uses Java.Io, so a change to Java.Io can break Java.Lang.Reflect, while a change to Java.Lang.Reflect can't break Java.Io.
- Position
- Below the diagonal: Java.Lang.Reflect uses a module listed above it, which is the healthy direction.
15→16 Java.Lang.Reflect uses Java.Lang part of a loop✕
- Connections
- 28 pairs of types, where a type in Java.Lang.Reflect uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Lang.Reflect.AccessibleObject→Java.Lang.ClassJava.Lang.Reflect.AnnotatedElement→Java.Lang.ClassJava.Lang.Reflect.Array→Java.Lang.ClassJava.Lang.Reflect.Executable→Java.Lang.ClassJava.Lang.Reflect.Executable→Java.Lang.StringJava.Lang.Reflect.Field→Java.Lang.ClassJava.Lang.Reflect.Field→Java.Lang.StringJava.Lang.Reflect.GenericSignatureFormatError→Java.Lang.ClassFormatErrorJava.Lang.Reflect.IAnnotatedElement→Java.Lang.ClassJava.Lang.Reflect.IMember→Java.Lang.ClassJava.Lang.Reflect.IMember→Java.Lang.StringJava.Lang.Reflect.IType→Java.Lang.StringJava.Lang.Reflect.ITypeVariable→Java.Lang.StringJava.Lang.Reflect.InvocationTargetException→Java.Lang.ReflectiveOperationExceptionJava.Lang.Reflect.MalformedParameterizedTypeException→Java.Lang.RuntimeExceptionJava.Lang.Reflect.MalformedParametersException→Java.Lang.RuntimeExceptionJava.Lang.Reflect.Member→Java.Lang.ClassJava.Lang.Reflect.Member→Java.Lang.StringJava.Lang.Reflect.Method→Java.Lang.ClassJava.Lang.Reflect.Modifier→Java.Lang.StringJava.Lang.Reflect.Parameter→Java.Lang.ClassJava.Lang.Reflect.Parameter→Java.Lang.StringJava.Lang.Reflect.Proxy→Java.Lang.ClassJava.Lang.Reflect.Proxy→Java.Lang.ClassLoaderJava.Lang.Reflect.ReflectPermission→Java.Lang.String
- Direction
- Java.Lang.Reflect uses Java.Lang, so a change to Java.Lang can break Java.Lang.Reflect, while a change to Java.Lang.Reflect can't break Java.Lang.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→1 Java.Lang uses Java.Lang.Annotation✕
- Connections
- 13 pairs of types, where a type in Java.Lang uses a type in Java.Lang.Annotation.
- The types involved
Java.Lang.Class→Java.Lang.Annotation.AnnotationJava.Lang.Deprecated→Java.Lang.Annotation.AnnotationJava.Lang.FunctionalInterface→Java.Lang.Annotation.AnnotationJava.Lang.IDeprecated→Java.Lang.Annotation.IAnnotationJava.Lang.IFunctionalInterface→Java.Lang.Annotation.IAnnotationJava.Lang.IOverride→Java.Lang.Annotation.IAnnotationJava.Lang.ISafeVarargs→Java.Lang.Annotation.IAnnotationJava.Lang.ISuppressWarnings→Java.Lang.Annotation.IAnnotationJava.Lang.Module→Java.Lang.Annotation.AnnotationJava.Lang.Override→Java.Lang.Annotation.AnnotationJava.Lang.Package→Java.Lang.Annotation.AnnotationJava.Lang.SafeVarargs→Java.Lang.Annotation.AnnotationJava.Lang.SuppressWarnings→Java.Lang.Annotation.Annotation
- Direction
- Java.Lang uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Java.Lang, while a change to Java.Lang can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→2 Java.Lang uses Java.Nio✕
- Connections
- 2 pairs of types, where a type in Java.Lang uses a type in Java.Nio.
- The types involved
Java.Lang.IReadable→Java.Nio.CharBufferJava.Lang.Readable→Java.Nio.CharBuffer
- Direction
- Java.Lang uses Java.Nio, so a change to Java.Nio can break Java.Lang, while a change to Java.Lang can't break Java.Nio.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→4 Java.Lang uses Java.Util✕
- Connections
- 10 pairs of types, where a type in Java.Lang uses a type in Java.Util.
- The types involved
Java.Lang.ClassLoader→Java.Util.EnumerationJava.Lang.IIterable→Java.Util.IteratorJava.Lang.Iterable→Java.Util.IteratorJava.Lang.ProcessBuilder→Java.Util.ListJava.Lang.ProcessBuilder→Java.Util.MapJava.Lang.String→Java.Util.ComparatorJava.Lang.String→Java.Util.LocaleJava.Lang.System→Java.Util.MapJava.Lang.System→Java.Util.PropertiesJava.Lang.Thread→Java.Util.Map
- Direction
- Java.Lang uses Java.Util, so a change to Java.Util can break Java.Lang, while a change to Java.Lang can't break Java.Util.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→6 Java.Lang uses MASES.JNet.Specific✕
- Connections
- 1 pair of types, where a type in Java.Lang uses a type in MASES.JNet.Specific.
- The types involved
Java.Lang.Runnable→MASES.JNet.Specific.JNetEventData
- Direction
- Java.Lang uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Java.Lang, while a change to Java.Lang can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→8 Java.Lang uses Java.Security✕
- Connections
- 3 pairs of types, where a type in Java.Lang uses a type in Java.Security.
- The types involved
Java.Lang.Class→Java.Security.ProtectionDomainJava.Lang.RuntimePermission→Java.Security.BasicPermissionJava.Lang.SecurityManager→Java.Security.Permission
- Direction
- Java.Lang uses Java.Security, so a change to Java.Security can break Java.Lang, while a change to Java.Lang can't break Java.Security.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→9 Java.Lang uses Java.Util.Concurrent✕
- Connections
- 1 pair of types, where a type in Java.Lang uses a type in Java.Util.Concurrent.
- The types involved
Java.Lang.Process→Java.Util.Concurrent.TimeUnit
- Direction
- Java.Lang uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Java.Lang, while a change to Java.Lang can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→12 Java.Lang uses Java.Nio.Channels✕
- Connections
- 1 pair of types, where a type in Java.Lang uses a type in Java.Nio.Channels.
- The types involved
Java.Lang.System→Java.Nio.Channels.Channel
- Direction
- Java.Lang uses Java.Nio.Channels, so a change to Java.Nio.Channels can break Java.Lang, while a change to Java.Lang can't break Java.Nio.Channels.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→13 Java.Lang uses Java.Net✕
- Connections
- 4 pairs of types, where a type in Java.Lang uses a type in Java.Net.
- The types involved
Java.Lang.Class→Java.Net.URLJava.Lang.ClassLoader→Java.Net.URLJava.Lang.Package→Java.Net.URLJava.Lang.SecurityManager→Java.Net.InetAddress
- Direction
- Java.Lang uses Java.Net, so a change to Java.Net can break Java.Lang, while a change to Java.Lang can't break Java.Net.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→14 Java.Lang uses Java.Io✕
- Connections
- 24 pairs of types, where a type in Java.Lang uses a type in Java.Io.
- The types involved
Java.Lang.Boolean→Java.Io.SerializableJava.Lang.Character→Java.Io.SerializableJava.Lang.Class→Java.Io.InputStreamJava.Lang.Class→Java.Io.SerializableJava.Lang.ClassLoader→Java.Io.InputStreamJava.Lang.Enum→Java.Io.SerializableJava.Lang.Number→Java.Io.SerializableJava.Lang.Process→Java.Io.InputStreamJava.Lang.Process→Java.Io.OutputStreamJava.Lang.ProcessBuilder→Java.Io.FileJava.Lang.Redirect→Java.Io.FileJava.Lang.Runtime→Java.Io.FileJava.Lang.Runtime→Java.Io.InputStreamJava.Lang.Runtime→Java.Io.OutputStreamJava.Lang.SecurityManager→Java.Io.FileDescriptorJava.Lang.StackTraceElement→Java.Io.SerializableJava.Lang.String→Java.Io.SerializableJava.Lang.StringBuffer→Java.Io.SerializableJava.Lang.StringBuilder→Java.Io.SerializableJava.Lang.System→Java.Io.ConsoleJava.Lang.System→Java.Io.InputStreamJava.Lang.System→Java.Io.PrintStreamJava.Lang.Throwable→Java.Io.PrintStreamJava.Lang.Throwable→Java.Io.PrintWriter
- Direction
- Java.Lang uses Java.Io, so a change to Java.Io can break Java.Lang, while a change to Java.Lang can't break Java.Io.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
16→15 Java.Lang uses Java.Lang.Reflect✕
- Connections
- 10 pairs of types, where a type in Java.Lang uses a type in Java.Lang.Reflect.
- The types involved
Java.Lang.Class→Java.Lang.Reflect.AnnotatedElementJava.Lang.Class→Java.Lang.Reflect.AnnotatedTypeJava.Lang.Class→Java.Lang.Reflect.ConstructorJava.Lang.Class→Java.Lang.Reflect.FieldJava.Lang.Class→Java.Lang.Reflect.GenericDeclarationJava.Lang.Class→Java.Lang.Reflect.IGenericDeclarationJava.Lang.Class→Java.Lang.Reflect.MethodJava.Lang.Class→Java.Lang.Reflect.TypeJava.Lang.Class→Java.Lang.Reflect.TypeVariableJava.Lang.Package→Java.Lang.Reflect.AnnotatedElement
- Direction
- Java.Lang uses Java.Lang.Reflect, so a change to Java.Lang.Reflect can break Java.Lang, while a change to Java.Lang can't break Java.Lang.Reflect.
- Position
- Below the diagonal: Java.Lang uses a module listed above it, which is the healthy direction.
17→4 Java.Awt.ImageNs uses Java.Util✕
- Connections
- 9 pairs of types, where a type in Java.Awt.ImageNs uses a type in Java.Util.
- The types involved
Java.Awt.ImageNs.BufferedImage→Java.Util.HashtableJava.Awt.ImageNs.BufferedImage→Java.Util.VectorJava.Awt.ImageNs.IImageConsumer→Java.Util.HashtableJava.Awt.ImageNs.IRenderedImage→Java.Util.VectorJava.Awt.ImageNs.ImageConsumer→Java.Util.HashtableJava.Awt.ImageNs.ImageFilter→Java.Util.HashtableJava.Awt.ImageNs.MemoryImageSource→Java.Util.HashtableJava.Awt.ImageNs.PixelGrabber→Java.Util.HashtableJava.Awt.ImageNs.RenderedImage→Java.Util.Vector
- Direction
- Java.Awt.ImageNs uses Java.Util, so a change to Java.Util can break Java.Awt.ImageNs, while a change to Java.Awt.ImageNs can't break Java.Util.
- Position
- Below the diagonal: Java.Awt.ImageNs uses a module listed above it, which is the healthy direction.
17→5 Java.Awt.ImageNs uses Java.Math✕
- Connections
- 1 pair of types, where a type in Java.Awt.ImageNs uses a type in Java.Math.
- The types involved
Java.Awt.ImageNs.IndexColorModel→Java.Math.BigInteger
- Direction
- Java.Awt.ImageNs uses Java.Math, so a change to Java.Math can break Java.Awt.ImageNs, while a change to Java.Awt.ImageNs can't break Java.Math.
- Position
- Below the diagonal: Java.Awt.ImageNs uses a module listed above it, which is the healthy direction.
17→16 Java.Awt.ImageNs uses Java.Lang✕
- Connections
- 7 pairs of types, where a type in Java.Awt.ImageNs uses a type in Java.Lang.
- The types involved
Java.Awt.ImageNs.BufferedImage→Java.Lang.StringJava.Awt.ImageNs.IRenderedImage→Java.Lang.StringJava.Awt.ImageNs.ImageFilter→Java.Lang.CloneableJava.Awt.ImageNs.ImagingOpException→Java.Lang.RuntimeExceptionJava.Awt.ImageNs.Kernel→Java.Lang.CloneableJava.Awt.ImageNs.RasterFormatException→Java.Lang.RuntimeExceptionJava.Awt.ImageNs.RenderedImage→Java.Lang.String
- Direction
- Java.Awt.ImageNs uses Java.Lang, so a change to Java.Lang can break Java.Awt.ImageNs, while a change to Java.Awt.ImageNs can't break Java.Lang.
- Position
- Below the diagonal: Java.Awt.ImageNs uses a module listed above it, which is the healthy direction.
17→39 Java.Awt.ImageNs uses Java.Awt part of a loop✕
- Connections
- 32 pairs of types, where a type in Java.Awt.ImageNs uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.ImageNs.AffineTransformOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.BandCombineOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.BufferStrategy→Java.Awt.BufferCapabilitiesJava.Awt.ImageNs.BufferStrategy→Java.Awt.GraphicsJava.Awt.ImageNs.BufferedImage→Java.Awt.Graphics2DJava.Awt.ImageNs.BufferedImage→Java.Awt.ImageJava.Awt.ImageNs.BufferedImage→Java.Awt.PointJava.Awt.ImageNs.BufferedImage→Java.Awt.RectangleJava.Awt.ImageNs.BufferedImage→Java.Awt.TransparencyJava.Awt.ImageNs.BufferedImageOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.ColorConvertOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.ColorModel→Java.Awt.TransparencyJava.Awt.ImageNs.ConvolveOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.IBufferedImageOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.IImageObserver→Java.Awt.ImageJava.Awt.ImageNs.IRasterOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.IRenderedImage→Java.Awt.RectangleJava.Awt.ImageNs.IWritableRenderedImage→Java.Awt.PointJava.Awt.ImageNs.ImageObserver→Java.Awt.ImageJava.Awt.ImageNs.LookupOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.PixelGrabber→Java.Awt.ImageJava.Awt.ImageNs.Raster→Java.Awt.PointJava.Awt.ImageNs.Raster→Java.Awt.RectangleJava.Awt.ImageNs.RasterOp→Java.Awt.RenderingHintsJava.Awt.ImageNs.RenderedImage→Java.Awt.Rectangle
- Direction
- Java.Awt.ImageNs uses Java.Awt, so a change to Java.Awt can break Java.Awt.ImageNs, while a change to Java.Awt.ImageNs can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→3 Java.Sql uses Java.Time✕
- Connections
- 3 pairs of types, where a type in Java.Sql uses a type in Java.Time.
- The types involved
Java.Sql.Date→Java.Time.LocalDateJava.Sql.Time→Java.Time.LocalTimeJava.Sql.Timestamp→Java.Time.LocalDateTime
- Direction
- Java.Sql uses Java.Time, so a change to Java.Time can break Java.Sql, while a change to Java.Sql can't break Java.Time.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→4 Java.Sql uses Java.Util✕
- Connections
- 27 pairs of types, where a type in Java.Sql uses a type in Java.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Sql.Array→Java.Util.MapJava.Sql.CallableStatement→Java.Util.CalendarJava.Sql.CallableStatement→Java.Util.MapJava.Sql.Connection→Java.Util.MapJava.Sql.Connection→Java.Util.PropertiesJava.Sql.Date→Java.Util.DateJava.Sql.Driver→Java.Util.PropertiesJava.Sql.DriverManager→Java.Util.EnumerationJava.Sql.DriverManager→Java.Util.PropertiesJava.Sql.IArray→Java.Util.MapJava.Sql.ICallableStatement→Java.Util.CalendarJava.Sql.ICallableStatement→Java.Util.MapJava.Sql.IConnection→Java.Util.MapJava.Sql.IConnection→Java.Util.PropertiesJava.Sql.IDriver→Java.Util.PropertiesJava.Sql.IPreparedStatement→Java.Util.CalendarJava.Sql.IRef→Java.Util.MapJava.Sql.IResultSet→Java.Util.CalendarJava.Sql.IResultSet→Java.Util.MapJava.Sql.IStruct→Java.Util.MapJava.Sql.PreparedStatement→Java.Util.CalendarJava.Sql.Ref→Java.Util.MapJava.Sql.ResultSet→Java.Util.CalendarJava.Sql.ResultSet→Java.Util.MapJava.Sql.Struct→Java.Util.Map
- Direction
- Java.Sql uses Java.Util, so a change to Java.Util can break Java.Sql, while a change to Java.Sql can't break Java.Util.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→5 Java.Sql uses Java.Math✕
- Connections
- 10 pairs of types, where a type in Java.Sql uses a type in Java.Math.
- The types involved
Java.Sql.CallableStatement→Java.Math.BigDecimalJava.Sql.ICallableStatement→Java.Math.BigDecimalJava.Sql.IPreparedStatement→Java.Math.BigDecimalJava.Sql.IResultSet→Java.Math.BigDecimalJava.Sql.ISQLInput→Java.Math.BigDecimalJava.Sql.ISQLOutput→Java.Math.BigDecimalJava.Sql.PreparedStatement→Java.Math.BigDecimalJava.Sql.ResultSet→Java.Math.BigDecimalJava.Sql.SQLInput→Java.Math.BigDecimalJava.Sql.SQLOutput→Java.Math.BigDecimal
- Direction
- Java.Sql uses Java.Math, so a change to Java.Math can break Java.Sql, while a change to Java.Sql can't break Java.Math.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→8 Java.Sql uses Java.Security✕
- Connections
- 1 pair of types, where a type in Java.Sql uses a type in Java.Security.
- The types involved
Java.Sql.SQLPermission→Java.Security.BasicPermission
- Direction
- Java.Sql uses Java.Security, so a change to Java.Security can break Java.Sql, while a change to Java.Sql can't break Java.Security.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→9 Java.Sql uses Java.Util.Concurrent✕
- Connections
- 2 pairs of types, where a type in Java.Sql uses a type in Java.Util.Concurrent.
- The types involved
Java.Sql.Connection→Java.Util.Concurrent.ExecutorJava.Sql.IConnection→Java.Util.Concurrent.Executor
- Direction
- Java.Sql uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Java.Sql, while a change to Java.Sql can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→13 Java.Sql uses Java.Net✕
- Connections
- 10 pairs of types, where a type in Java.Sql uses a type in Java.Net.
- The types involved
Java.Sql.CallableStatement→Java.Net.URLJava.Sql.ICallableStatement→Java.Net.URLJava.Sql.IPreparedStatement→Java.Net.URLJava.Sql.IResultSet→Java.Net.URLJava.Sql.ISQLInput→Java.Net.URLJava.Sql.ISQLOutput→Java.Net.URLJava.Sql.PreparedStatement→Java.Net.URLJava.Sql.ResultSet→Java.Net.URLJava.Sql.SQLInput→Java.Net.URLJava.Sql.SQLOutput→Java.Net.URL
- Direction
- Java.Sql uses Java.Net, so a change to Java.Net can break Java.Sql, while a change to Java.Sql can't break Java.Net.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→14 Java.Sql uses Java.Io✕
- Connections
- 42 pairs of types, where a type in Java.Sql uses a type in Java.Io. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Sql.Blob→Java.Io.InputStreamJava.Sql.Blob→Java.Io.OutputStreamJava.Sql.CallableStatement→Java.Io.InputStreamJava.Sql.CallableStatement→Java.Io.ReaderJava.Sql.Clob→Java.Io.InputStreamJava.Sql.Clob→Java.Io.OutputStreamJava.Sql.Clob→Java.Io.ReaderJava.Sql.Clob→Java.Io.WriterJava.Sql.DriverManager→Java.Io.PrintStreamJava.Sql.DriverManager→Java.Io.PrintWriterJava.Sql.IBlob→Java.Io.InputStreamJava.Sql.IBlob→Java.Io.OutputStreamJava.Sql.ICallableStatement→Java.Io.InputStreamJava.Sql.ICallableStatement→Java.Io.ReaderJava.Sql.IClob→Java.Io.InputStreamJava.Sql.IClob→Java.Io.OutputStreamJava.Sql.IClob→Java.Io.ReaderJava.Sql.IClob→Java.Io.WriterJava.Sql.IPreparedStatement→Java.Io.InputStreamJava.Sql.IPreparedStatement→Java.Io.ReaderJava.Sql.IResultSet→Java.Io.InputStreamJava.Sql.IResultSet→Java.Io.ReaderJava.Sql.ISQLInput→Java.Io.InputStreamJava.Sql.ISQLInput→Java.Io.ReaderJava.Sql.ISQLOutput→Java.Io.InputStream
- Direction
- Java.Sql uses Java.Io, so a change to Java.Io can break Java.Sql, while a change to Java.Sql can't break Java.Io.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
18→16 Java.Sql uses Java.Lang✕
- Connections
- 77 pairs of types, where a type in Java.Sql uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Sql.Array→Java.Lang.ClassJava.Sql.Array→Java.Lang.StringJava.Sql.CallableStatement→Java.Lang.ClassJava.Sql.CallableStatement→Java.Lang.StringJava.Sql.ClientInfoStatus→Java.Lang.EnumJava.Sql.ClientInfoStatus→Java.Lang.StringJava.Sql.Clob→Java.Lang.StringJava.Sql.Connection→Java.Lang.AutoCloseableJava.Sql.Connection→Java.Lang.ClassJava.Sql.Connection→Java.Lang.StringJava.Sql.DatabaseMetaData→Java.Lang.StringJava.Sql.Date→Java.Lang.StringJava.Sql.Driver→Java.Lang.StringJava.Sql.DriverManager→Java.Lang.StringJava.Sql.DriverPropertyInfo→Java.Lang.StringJava.Sql.IArray→Java.Lang.ClassJava.Sql.IArray→Java.Lang.StringJava.Sql.ICallableStatement→Java.Lang.ClassJava.Sql.ICallableStatement→Java.Lang.StringJava.Sql.IClob→Java.Lang.StringJava.Sql.IConnection→Java.Lang.ClassJava.Sql.IConnection→Java.Lang.StringJava.Sql.IDatabaseMetaData→Java.Lang.StringJava.Sql.IDriver→Java.Lang.StringJava.Sql.IParameterMetaData→Java.Lang.String
- Direction
- Java.Sql uses Java.Lang, so a change to Java.Lang can break Java.Sql, while a change to Java.Sql can't break Java.Lang.
- Position
- Below the diagonal: Java.Sql uses a module listed above it, which is the healthy direction.
19→4 Java.Text uses Java.Util✕
- Connections
- 20 pairs of types, where a type in Java.Text uses a type in Java.Util.
- The types involved
Java.Text.AttributedCharacterIterator→Java.Util.MapJava.Text.AttributedCharacterIterator→Java.Util.SetJava.Text.AttributedString→Java.Util.MapJava.Text.BreakIterator→Java.Util.LocaleJava.Text.Collator→Java.Util.ComparatorJava.Text.Collator→Java.Util.LocaleJava.Text.DateFormat→Java.Util.CalendarJava.Text.DateFormat→Java.Util.DateJava.Text.DateFormat→Java.Util.LocaleJava.Text.DateFormat→Java.Util.TimeZoneJava.Text.DateFormatSymbols→Java.Util.LocaleJava.Text.DecimalFormatSymbols→Java.Util.CurrencyJava.Text.DecimalFormatSymbols→Java.Util.LocaleJava.Text.IAttributedCharacterIterator→Java.Util.MapJava.Text.IAttributedCharacterIterator→Java.Util.SetJava.Text.MessageFormat→Java.Util.LocaleJava.Text.NumberFormat→Java.Util.CurrencyJava.Text.NumberFormat→Java.Util.LocaleJava.Text.SimpleDateFormat→Java.Util.DateJava.Text.SimpleDateFormat→Java.Util.Locale
- Direction
- Java.Text uses Java.Util, so a change to Java.Util can break Java.Text, while a change to Java.Text can't break Java.Util.
- Position
- Below the diagonal: Java.Text uses a module listed above it, which is the healthy direction.
19→5 Java.Text uses Java.Math✕
- Connections
- 1 pair of types, where a type in Java.Text uses a type in Java.Math.
- The types involved
Java.Text.NumberFormat→Java.Math.RoundingMode
- Direction
- Java.Text uses Java.Math, so a change to Java.Math can break Java.Text, while a change to Java.Text can't break Java.Math.
- Position
- Below the diagonal: Java.Text uses a module listed above it, which is the healthy direction.
19→14 Java.Text uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Java.Text uses a type in Java.Io.
- The types involved
Java.Text.Attribute→Java.Io.SerializableJava.Text.DateFormatSymbols→Java.Io.SerializableJava.Text.DecimalFormatSymbols→Java.Io.SerializableJava.Text.Format→Java.Io.Serializable
- Direction
- Java.Text uses Java.Io, so a change to Java.Io can break Java.Text, while a change to Java.Text can't break Java.Io.
- Position
- Below the diagonal: Java.Text uses a module listed above it, which is the healthy direction.
19→16 Java.Text uses Java.Lang✕
- Connections
- 35 pairs of types, where a type in Java.Text uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Text.AttributedString→Java.Lang.StringJava.Text.Bidi→Java.Lang.StringJava.Text.BreakIterator→Java.Lang.CloneableJava.Text.BreakIterator→Java.Lang.StringJava.Text.CharacterIterator→Java.Lang.CloneableJava.Text.ChoiceFormat→Java.Lang.StringJava.Text.CollationElementIterator→Java.Lang.StringJava.Text.CollationKey→Java.Lang.ComparableJava.Text.CollationKey→Java.Lang.StringJava.Text.Collator→Java.Lang.CloneableJava.Text.Collator→Java.Lang.StringJava.Text.DateFormat→Java.Lang.StringJava.Text.DateFormat→Java.Lang.StringBufferJava.Text.DateFormatSymbols→Java.Lang.CloneableJava.Text.DateFormatSymbols→Java.Lang.StringJava.Text.DecimalFormat→Java.Lang.StringJava.Text.DecimalFormatSymbols→Java.Lang.CloneableJava.Text.DecimalFormatSymbols→Java.Lang.StringJava.Text.Form→Java.Lang.EnumJava.Text.Form→Java.Lang.StringJava.Text.Format→Java.Lang.CloneableJava.Text.Format→Java.Lang.StringJava.Text.Format→Java.Lang.StringBufferJava.Text.ICharacterIterator→Java.Lang.ICloneableJava.Text.MessageFormat→Java.Lang.String
- Direction
- Java.Text uses Java.Lang, so a change to Java.Lang can break Java.Text, while a change to Java.Text can't break Java.Lang.
- Position
- Below the diagonal: Java.Text uses a module listed above it, which is the healthy direction.
20→1 Javax.Management uses Java.Lang.Annotation✕
- Connections
- 4 pairs of types, where a type in Javax.Management uses a type in Java.Lang.Annotation.
- The types involved
Javax.Management.DescriptorKey→Java.Lang.Annotation.AnnotationJavax.Management.IDescriptorKey→Java.Lang.Annotation.IAnnotationJavax.Management.IMXBean→Java.Lang.Annotation.IAnnotationJavax.Management.MXBean→Java.Lang.Annotation.Annotation
- Direction
- Javax.Management uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Javax.Management, while a change to Javax.Management can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→4 Javax.Management uses Java.Util✕
- Connections
- 13 pairs of types, where a type in Javax.Management uses a type in Java.Util.
- The types involved
Javax.Management.AttributeChangeNotificationFilter→Java.Util.VectorJavax.Management.AttributeList→Java.Util.ArrayListJavax.Management.AttributeList→Java.Util.ListJavax.Management.IMBeanServer→Java.Util.SetJavax.Management.IMBeanServerConnection→Java.Util.SetJavax.Management.ImmutableDescriptor→Java.Util.MapJavax.Management.MBeanServer→Java.Util.SetJavax.Management.MBeanServerConnection→Java.Util.SetJavax.Management.MBeanServerFactory→Java.Util.ArrayListJavax.Management.Notification→Java.Util.EventObjectJavax.Management.NotificationFilterSupport→Java.Util.VectorJavax.Management.NotificationListener→Java.Util.EventListenerJavax.Management.ObjectName→Java.Util.Hashtable
- Direction
- Javax.Management uses Java.Util, so a change to Java.Util can break Javax.Management, while a change to Javax.Management can't break Java.Util.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→6 Javax.Management uses MASES.JNet.Specific✕
- Connections
- 2 pairs of types, where a type in Javax.Management uses a type in MASES.JNet.Specific.
- The types involved
Javax.Management.NotificationFilter→MASES.JNet.Specific.JNetEventDataJavax.Management.NotificationListener→MASES.JNet.Specific.JNetEventData
- Direction
- Javax.Management uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Javax.Management, while a change to Javax.Management can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→8 Javax.Management uses Java.Security✕
- Connections
- 3 pairs of types, where a type in Javax.Management uses a type in Java.Security.
- The types involved
Javax.Management.MBeanPermission→Java.Security.PermissionJavax.Management.MBeanServerPermission→Java.Security.BasicPermissionJavax.Management.MBeanTrustPermission→Java.Security.BasicPermission
- Direction
- Javax.Management uses Java.Security, so a change to Java.Security can break Javax.Management, while a change to Javax.Management can't break Java.Security.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→9 Javax.Management uses Java.Util.Concurrent✕
- Connections
- 1 pair of types, where a type in Javax.Management uses a type in Java.Util.Concurrent.
- The types involved
Javax.Management.NotificationBroadcasterSupport→Java.Util.Concurrent.Executor
- Direction
- Javax.Management uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Javax.Management, while a change to Javax.Management can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→14 Javax.Management uses Java.Io✕
- Connections
- 12 pairs of types, where a type in Javax.Management uses a type in Java.Io.
- The types involved
Javax.Management.Attribute→Java.Io.SerializableJavax.Management.Descriptor→Java.Io.SerializableJavax.Management.IMBeanServer→Java.Io.ObjectInputStreamJavax.Management.IQueryExp→Java.Io.ISerializableJavax.Management.IValueExp→Java.Io.ISerializableJavax.Management.MBeanFeatureInfo→Java.Io.SerializableJavax.Management.MBeanInfo→Java.Io.SerializableJavax.Management.MBeanServer→Java.Io.ObjectInputStreamJavax.Management.ObjectInstance→Java.Io.SerializableJavax.Management.QueryEval→Java.Io.SerializableJavax.Management.QueryExp→Java.Io.SerializableJavax.Management.ValueExp→Java.Io.Serializable
- Direction
- Javax.Management uses Java.Io, so a change to Java.Io can break Javax.Management, while a change to Javax.Management can't break Java.Io.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→15 Javax.Management uses Java.Lang.Reflect✕
- Connections
- 5 pairs of types, where a type in Javax.Management uses a type in Java.Lang.Reflect.
- The types involved
Javax.Management.MBeanAttributeInfo→Java.Lang.Reflect.MethodJavax.Management.MBeanConstructorInfo→Java.Lang.Reflect.ConstructorJavax.Management.MBeanOperationInfo→Java.Lang.Reflect.MethodJavax.Management.MBeanServerInvocationHandler→Java.Lang.Reflect.InvocationHandlerJavax.Management.MBeanServerInvocationHandler→Java.Lang.Reflect.Method
- Direction
- Javax.Management uses Java.Lang.Reflect, so a change to Java.Lang.Reflect can break Javax.Management, while a change to Javax.Management can't break Java.Lang.Reflect.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
20→16 Javax.Management uses Java.Lang✕
- Connections
- 75 pairs of types, where a type in Javax.Management uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Management.Attribute→Java.Lang.StringJavax.Management.AttributeChangeNotification→Java.Lang.StringJavax.Management.AttributeChangeNotificationFilter→Java.Lang.StringJavax.Management.AttributeValueExp→Java.Lang.StringJavax.Management.BadAttributeValueExpException→Java.Lang.ExceptionJavax.Management.BadBinaryOpValueExpException→Java.Lang.ExceptionJavax.Management.BadStringOperationException→Java.Lang.ExceptionJavax.Management.DefaultLoaderRepository→Java.Lang.ClassJavax.Management.DefaultLoaderRepository→Java.Lang.ClassLoaderJavax.Management.DefaultLoaderRepository→Java.Lang.StringJavax.Management.Descriptor→Java.Lang.CloneableJavax.Management.Descriptor→Java.Lang.StringJavax.Management.DescriptorKey→Java.Lang.StringJavax.Management.DynamicMBean→Java.Lang.StringJavax.Management.IDescriptor→Java.Lang.StringJavax.Management.IDescriptorKey→Java.Lang.StringJavax.Management.IDynamicMBean→Java.Lang.StringJavax.Management.IMBeanRegistration→Java.Lang.BooleanJavax.Management.IMBeanServer→Java.Lang.ClassLoaderJavax.Management.IMBeanServer→Java.Lang.IntegerJavax.Management.IMBeanServer→Java.Lang.StringJavax.Management.IMBeanServerConnection→Java.Lang.IntegerJavax.Management.IMBeanServerConnection→Java.Lang.StringJavax.Management.IMBeanServerDelegateMBean→Java.Lang.StringJavax.Management.ImmutableDescriptor→Java.Lang.String
- Direction
- Javax.Management uses Java.Lang, so a change to Java.Lang can break Javax.Management, while a change to Javax.Management can't break Java.Lang.
- Position
- Below the diagonal: Javax.Management uses a module listed above it, which is the healthy direction.
21→2 Javax.Net.Ssl uses Java.Nio✕
- Connections
- 1 pair of types, where a type in Javax.Net.Ssl uses a type in Java.Nio.
- The types involved
Javax.Net.Ssl.SSLEngine→Java.Nio.ByteBuffer
- Direction
- Javax.Net.Ssl uses Java.Nio, so a change to Java.Nio can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Nio.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→4 Javax.Net.Ssl uses Java.Util✕
- Connections
- 12 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Util.
- The types involved
Javax.Net.Ssl.ExtendedSSLSession→Java.Util.ListJavax.Net.Ssl.HandshakeCompletedEvent→Java.Util.EventObjectJavax.Net.Ssl.HandshakeCompletedListener→Java.Util.EventListenerJavax.Net.Ssl.ISSLSessionContext→Java.Util.EnumerationJavax.Net.Ssl.KeyStoreBuilderParameters→Java.Util.ListJavax.Net.Ssl.SSLEngine→Java.Util.ListJavax.Net.Ssl.SSLParameters→Java.Util.CollectionJavax.Net.Ssl.SSLParameters→Java.Util.ListJavax.Net.Ssl.SSLSessionBindingEvent→Java.Util.EventObjectJavax.Net.Ssl.SSLSessionBindingListener→Java.Util.EventListenerJavax.Net.Ssl.SSLSessionContext→Java.Util.EnumerationJavax.Net.Ssl.SSLSocket→Java.Util.List
- Direction
- Javax.Net.Ssl uses Java.Util, so a change to Java.Util can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Util.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→6 Javax.Net.Ssl uses MASES.JNet.Specific✕
- Connections
- 2 pairs of types, where a type in Javax.Net.Ssl uses a type in MASES.JNet.Specific.
- The types involved
Javax.Net.Ssl.HandshakeCompletedListener→MASES.JNet.Specific.JNetEventDataJavax.Net.Ssl.SSLSessionBindingListener→MASES.JNet.Specific.JNetEventData
- Direction
- Javax.Net.Ssl uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→7 Javax.Net.Ssl uses Java.Security.Cert✕
- Connections
- 10 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Security.Cert.
- The types involved
Javax.Net.Ssl.CertPathTrustManagerParameters→Java.Security.Cert.CertPathParametersJavax.Net.Ssl.HandshakeCompletedEvent→Java.Security.Cert.CertificateJavax.Net.Ssl.HttpsURLConnection→Java.Security.Cert.CertificateJavax.Net.Ssl.ISSLSession→Java.Security.Cert.CertificateJavax.Net.Ssl.IX509KeyManager→Java.Security.Cert.X509CertificateJavax.Net.Ssl.IX509TrustManager→Java.Security.Cert.X509CertificateJavax.Net.Ssl.SSLSession→Java.Security.Cert.CertificateJavax.Net.Ssl.X509ExtendedTrustManager→Java.Security.Cert.X509CertificateJavax.Net.Ssl.X509KeyManager→Java.Security.Cert.X509CertificateJavax.Net.Ssl.X509TrustManager→Java.Security.Cert.X509Certificate
- Direction
- Javax.Net.Ssl uses Java.Security.Cert, so a change to Java.Security.Cert can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Security.Cert.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→8 Javax.Net.Ssl uses Java.Security✕
- Connections
- 18 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Security.
- The types involved
Javax.Net.Ssl.HandshakeCompletedEvent→Java.Security.PrincipalJavax.Net.Ssl.HttpsURLConnection→Java.Security.PrincipalJavax.Net.Ssl.ISSLSession→Java.Security.PrincipalJavax.Net.Ssl.IX509KeyManager→Java.Security.PrincipalJavax.Net.Ssl.IX509KeyManager→Java.Security.PrivateKeyJavax.Net.Ssl.KeyManagerFactory→Java.Security.KeyStoreJavax.Net.Ssl.KeyManagerFactory→Java.Security.ProviderJavax.Net.Ssl.KeyStoreBuilderParameters→Java.Security.BuilderJavax.Net.Ssl.SSLContext→Java.Security.ProviderJavax.Net.Ssl.SSLContext→Java.Security.SecureRandomJavax.Net.Ssl.SSLParameters→Java.Security.AlgorithmConstraintsJavax.Net.Ssl.SSLPermission→Java.Security.BasicPermissionJavax.Net.Ssl.SSLSession→Java.Security.PrincipalJavax.Net.Ssl.TrustManagerFactory→Java.Security.KeyStoreJavax.Net.Ssl.TrustManagerFactory→Java.Security.ProviderJavax.Net.Ssl.X509ExtendedKeyManager→Java.Security.PrincipalJavax.Net.Ssl.X509KeyManager→Java.Security.PrincipalJavax.Net.Ssl.X509KeyManager→Java.Security.PrivateKey
- Direction
- Javax.Net.Ssl uses Java.Security, so a change to Java.Security can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Security.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→13 Javax.Net.Ssl uses Java.Net✕
- Connections
- 7 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Net.
- The types involved
Javax.Net.Ssl.HttpsURLConnection→Java.Net.HttpURLConnectionJavax.Net.Ssl.IX509KeyManager→Java.Net.SocketJavax.Net.Ssl.SSLServerSocket→Java.Net.ServerSocketJavax.Net.Ssl.SSLSocket→Java.Net.SocketJavax.Net.Ssl.SSLSocketFactory→Java.Net.SocketJavax.Net.Ssl.X509ExtendedTrustManager→Java.Net.SocketJavax.Net.Ssl.X509KeyManager→Java.Net.Socket
- Direction
- Javax.Net.Ssl uses Java.Net, so a change to Java.Net can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Net.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→14 Javax.Net.Ssl uses Java.Io✕
- Connections
- 2 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Io.
- The types involved
Javax.Net.Ssl.SSLException→Java.Io.IOExceptionJavax.Net.Ssl.SSLSocketFactory→Java.Io.InputStream
- Direction
- Javax.Net.Ssl uses Java.Io, so a change to Java.Io can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Io.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
21→16 Javax.Net.Ssl uses Java.Lang✕
- Connections
- 30 pairs of types, where a type in Javax.Net.Ssl uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Net.Ssl.ExtendedSSLSession→Java.Lang.StringJavax.Net.Ssl.HandshakeCompletedEvent→Java.Lang.StringJavax.Net.Ssl.HandshakeStatus→Java.Lang.EnumJavax.Net.Ssl.HandshakeStatus→Java.Lang.StringJavax.Net.Ssl.HostnameVerifier→Java.Lang.StringJavax.Net.Ssl.HttpsURLConnection→Java.Lang.StringJavax.Net.Ssl.IHostnameVerifier→Java.Lang.StringJavax.Net.Ssl.ISSLSession→Java.Lang.StringJavax.Net.Ssl.IX509KeyManager→Java.Lang.StringJavax.Net.Ssl.IX509TrustManager→Java.Lang.StringJavax.Net.Ssl.KeyManagerFactory→Java.Lang.StringJavax.Net.Ssl.SNIHostName→Java.Lang.StringJavax.Net.Ssl.SSLContext→Java.Lang.StringJavax.Net.Ssl.SSLEngine→Java.Lang.RunnableJavax.Net.Ssl.SSLEngine→Java.Lang.StringJavax.Net.Ssl.SSLParameters→Java.Lang.StringJavax.Net.Ssl.SSLPermission→Java.Lang.StringJavax.Net.Ssl.SSLServerSocket→Java.Lang.StringJavax.Net.Ssl.SSLServerSocketFactory→Java.Lang.StringJavax.Net.Ssl.SSLSession→Java.Lang.StringJavax.Net.Ssl.SSLSessionBindingEvent→Java.Lang.StringJavax.Net.Ssl.SSLSocket→Java.Lang.StringJavax.Net.Ssl.SSLSocketFactory→Java.Lang.StringJavax.Net.Ssl.Status→Java.Lang.EnumJavax.Net.Ssl.Status→Java.Lang.String
- Direction
- Javax.Net.Ssl uses Java.Lang, so a change to Java.Lang can break Javax.Net.Ssl, while a change to Javax.Net.Ssl can't break Java.Lang.
- Position
- Below the diagonal: Javax.Net.Ssl uses a module listed above it, which is the healthy direction.
22→4 Javax.Xml.Namespace uses Java.Util✕
- Connections
- 2 pairs of types, where a type in Javax.Xml.Namespace uses a type in Java.Util.
- The types involved
Javax.Xml.Namespace.INamespaceContext→Java.Util.IteratorJavax.Xml.Namespace.NamespaceContext→Java.Util.Iterator
- Direction
- Javax.Xml.Namespace uses Java.Util, so a change to Java.Util can break Javax.Xml.Namespace, while a change to Javax.Xml.Namespace can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Namespace uses a module listed above it, which is the healthy direction.
22→14 Javax.Xml.Namespace uses Java.Io✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Namespace uses a type in Java.Io.
- The types involved
Javax.Xml.Namespace.QName→Java.Io.Serializable
- Direction
- Javax.Xml.Namespace uses Java.Io, so a change to Java.Io can break Javax.Xml.Namespace, while a change to Javax.Xml.Namespace can't break Java.Io.
- Position
- Below the diagonal: Javax.Xml.Namespace uses a module listed above it, which is the healthy direction.
22→16 Javax.Xml.Namespace uses Java.Lang✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Namespace uses a type in Java.Lang.
- The types involved
Javax.Xml.Namespace.INamespaceContext→Java.Lang.StringJavax.Xml.Namespace.NamespaceContext→Java.Lang.StringJavax.Xml.Namespace.QName→Java.Lang.String
- Direction
- Javax.Xml.Namespace uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Namespace, while a change to Javax.Xml.Namespace can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Namespace uses a module listed above it, which is the healthy direction.
23→4 Javax.Xml.Transform uses Java.Util✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Transform uses a type in Java.Util.
- The types involved
Javax.Xml.Transform.ITemplates→Java.Util.PropertiesJavax.Xml.Transform.Templates→Java.Util.PropertiesJavax.Xml.Transform.Transformer→Java.Util.Properties
- Direction
- Javax.Xml.Transform uses Java.Util, so a change to Java.Util can break Javax.Xml.Transform, while a change to Javax.Xml.Transform can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Transform uses a module listed above it, which is the healthy direction.
23→6 Javax.Xml.Transform uses MASES.JNet.Specific✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Transform uses a type in MASES.JNet.Specific.
- The types involved
Javax.Xml.Transform.ErrorListener→MASES.JNet.Specific.JNetEventData
- Direction
- Javax.Xml.Transform uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Javax.Xml.Transform, while a change to Javax.Xml.Transform can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Javax.Xml.Transform uses a module listed above it, which is the healthy direction.
23→16 Javax.Xml.Transform uses Java.Lang✕
- Connections
- 14 pairs of types, where a type in Javax.Xml.Transform uses a type in Java.Lang.
- The types involved
Javax.Xml.Transform.IResult→Java.Lang.StringJavax.Xml.Transform.ISource→Java.Lang.StringJavax.Xml.Transform.ISourceLocator→Java.Lang.StringJavax.Xml.Transform.IURIResolver→Java.Lang.StringJavax.Xml.Transform.OutputKeys→Java.Lang.StringJavax.Xml.Transform.Result→Java.Lang.StringJavax.Xml.Transform.Source→Java.Lang.StringJavax.Xml.Transform.SourceLocator→Java.Lang.StringJavax.Xml.Transform.Transformer→Java.Lang.StringJavax.Xml.Transform.TransformerException→Java.Lang.ExceptionJavax.Xml.Transform.TransformerFactory→Java.Lang.ClassLoaderJavax.Xml.Transform.TransformerFactory→Java.Lang.StringJavax.Xml.Transform.TransformerFactoryConfigurationError→Java.Lang.ErrorJavax.Xml.Transform.URIResolver→Java.Lang.String
- Direction
- Javax.Xml.Transform uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Transform, while a change to Javax.Xml.Transform can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Transform uses a module listed above it, which is the healthy direction.
24→16 Org.W3c.Dom uses Java.Lang✕
- Connections
- 41 pairs of types, where a type in Org.W3c.Dom uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Org.W3c.Dom.Attr→Java.Lang.StringOrg.W3c.Dom.CharacterData→Java.Lang.StringOrg.W3c.Dom.DOMConfiguration→Java.Lang.StringOrg.W3c.Dom.DOMError→Java.Lang.StringOrg.W3c.Dom.DOMException→Java.Lang.RuntimeExceptionOrg.W3c.Dom.DOMImplementation→Java.Lang.StringOrg.W3c.Dom.DOMImplementationSource→Java.Lang.StringOrg.W3c.Dom.DOMLocator→Java.Lang.StringOrg.W3c.Dom.DOMStringList→Java.Lang.StringOrg.W3c.Dom.Document→Java.Lang.StringOrg.W3c.Dom.DocumentType→Java.Lang.StringOrg.W3c.Dom.Element→Java.Lang.StringOrg.W3c.Dom.Entity→Java.Lang.StringOrg.W3c.Dom.IAttr→Java.Lang.StringOrg.W3c.Dom.ICharacterData→Java.Lang.StringOrg.W3c.Dom.IDOMConfiguration→Java.Lang.StringOrg.W3c.Dom.IDOMError→Java.Lang.StringOrg.W3c.Dom.IDOMImplementation→Java.Lang.StringOrg.W3c.Dom.IDOMImplementationSource→Java.Lang.StringOrg.W3c.Dom.IDOMLocator→Java.Lang.StringOrg.W3c.Dom.IDOMStringList→Java.Lang.StringOrg.W3c.Dom.IDocument→Java.Lang.StringOrg.W3c.Dom.IDocumentType→Java.Lang.StringOrg.W3c.Dom.IElement→Java.Lang.StringOrg.W3c.Dom.IEntity→Java.Lang.String
- Direction
- Org.W3c.Dom uses Java.Lang, so a change to Java.Lang can break Org.W3c.Dom, while a change to Org.W3c.Dom can't break Java.Lang.
- Position
- Below the diagonal: Org.W3c.Dom uses a module listed above it, which is the healthy direction.
25→4 Org.Xml.Sax uses Java.Util✕
- Connections
- 2 pairs of types, where a type in Org.Xml.Sax uses a type in Java.Util.
- The types involved
Org.Xml.Sax.IParser→Java.Util.LocaleOrg.Xml.Sax.Parser→Java.Util.Locale
- Direction
- Org.Xml.Sax uses Java.Util, so a change to Java.Util can break Org.Xml.Sax, while a change to Org.Xml.Sax can't break Java.Util.
- Position
- Below the diagonal: Org.Xml.Sax uses a module listed above it, which is the healthy direction.
25→14 Org.Xml.Sax uses Java.Io✕
- Connections
- 2 pairs of types, where a type in Org.Xml.Sax uses a type in Java.Io.
- The types involved
Org.Xml.Sax.InputSource→Java.Io.InputStreamOrg.Xml.Sax.InputSource→Java.Io.Reader
- Direction
- Org.Xml.Sax uses Java.Io, so a change to Java.Io can break Org.Xml.Sax, while a change to Org.Xml.Sax can't break Java.Io.
- Position
- Below the diagonal: Org.Xml.Sax uses a module listed above it, which is the healthy direction.
25→16 Org.Xml.Sax uses Java.Lang✕
- Connections
- 21 pairs of types, where a type in Org.Xml.Sax uses a type in Java.Lang.
- The types involved
Org.Xml.Sax.AttributeList→Java.Lang.StringOrg.Xml.Sax.Attributes→Java.Lang.StringOrg.Xml.Sax.ContentHandler→Java.Lang.StringOrg.Xml.Sax.DTDHandler→Java.Lang.StringOrg.Xml.Sax.DocumentHandler→Java.Lang.StringOrg.Xml.Sax.EntityResolver→Java.Lang.StringOrg.Xml.Sax.HandlerBase→Java.Lang.StringOrg.Xml.Sax.IAttributeList→Java.Lang.StringOrg.Xml.Sax.IAttributes→Java.Lang.StringOrg.Xml.Sax.IContentHandler→Java.Lang.StringOrg.Xml.Sax.IDTDHandler→Java.Lang.StringOrg.Xml.Sax.IDocumentHandler→Java.Lang.StringOrg.Xml.Sax.IEntityResolver→Java.Lang.StringOrg.Xml.Sax.ILocator→Java.Lang.StringOrg.Xml.Sax.IParser→Java.Lang.StringOrg.Xml.Sax.IXMLReader→Java.Lang.StringOrg.Xml.Sax.InputSource→Java.Lang.StringOrg.Xml.Sax.Locator→Java.Lang.StringOrg.Xml.Sax.Parser→Java.Lang.StringOrg.Xml.Sax.SAXException→Java.Lang.ExceptionOrg.Xml.Sax.XMLReader→Java.Lang.String
- Direction
- Org.Xml.Sax uses Java.Lang, so a change to Java.Lang can break Org.Xml.Sax, while a change to Org.Xml.Sax can't break Java.Lang.
- Position
- Below the diagonal: Org.Xml.Sax uses a module listed above it, which is the healthy direction.
26→4 Java.Awt.EventNs uses Java.Util✕
- Connections
- 19 pairs of types, where a type in Java.Awt.EventNs uses a type in Java.Util.
- The types involved
Java.Awt.EventNs.AWTEventListener→Java.Util.EventListenerJava.Awt.EventNs.AWTEventListenerProxy→Java.Util.EventListenerProxyJava.Awt.EventNs.ActionListener→Java.Util.EventListenerJava.Awt.EventNs.AdjustmentListener→Java.Util.EventListenerJava.Awt.EventNs.ComponentListener→Java.Util.EventListenerJava.Awt.EventNs.ContainerListener→Java.Util.EventListenerJava.Awt.EventNs.FocusListener→Java.Util.EventListenerJava.Awt.EventNs.HierarchyBoundsListener→Java.Util.EventListenerJava.Awt.EventNs.HierarchyListener→Java.Util.EventListenerJava.Awt.EventNs.InputMethodListener→Java.Util.EventListenerJava.Awt.EventNs.ItemListener→Java.Util.EventListenerJava.Awt.EventNs.KeyListener→Java.Util.EventListenerJava.Awt.EventNs.MouseListener→Java.Util.EventListenerJava.Awt.EventNs.MouseMotionListener→Java.Util.EventListenerJava.Awt.EventNs.MouseWheelListener→Java.Util.EventListenerJava.Awt.EventNs.TextListener→Java.Util.EventListenerJava.Awt.EventNs.WindowFocusListener→Java.Util.EventListenerJava.Awt.EventNs.WindowListener→Java.Util.EventListenerJava.Awt.EventNs.WindowStateListener→Java.Util.EventListener
- Direction
- Java.Awt.EventNs uses Java.Util, so a change to Java.Util can break Java.Awt.EventNs, while a change to Java.Awt.EventNs can't break Java.Util.
- Position
- Below the diagonal: Java.Awt.EventNs uses a module listed above it, which is the healthy direction.
26→6 Java.Awt.EventNs uses MASES.JNet.Specific✕
- Connections
- 26 pairs of types, where a type in Java.Awt.EventNs uses a type in MASES.JNet.Specific. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.EventNs.AWTEventListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ActionListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.AdjustmentListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ComponentAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ComponentListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ContainerAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ContainerListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.FocusAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.FocusListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.HierarchyBoundsAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.HierarchyBoundsListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.HierarchyListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.InputMethodListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.ItemListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.KeyAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.KeyListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.MouseAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.MouseListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.MouseMotionAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.MouseMotionListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.MouseWheelListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.TextListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.WindowAdapter→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.WindowFocusListener→MASES.JNet.Specific.JNetEventDataJava.Awt.EventNs.WindowListener→MASES.JNet.Specific.JNetEventData
- Direction
- Java.Awt.EventNs uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Java.Awt.EventNs, while a change to Java.Awt.EventNs can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Java.Awt.EventNs uses a module listed above it, which is the healthy direction.
26→16 Java.Awt.EventNs uses Java.Lang✕
- Connections
- 7 pairs of types, where a type in Java.Awt.EventNs uses a type in Java.Lang.
- The types involved
Java.Awt.EventNs.ActionEvent→Java.Lang.StringJava.Awt.EventNs.InputEvent→Java.Lang.StringJava.Awt.EventNs.InvocationEvent→Java.Lang.ExceptionJava.Awt.EventNs.InvocationEvent→Java.Lang.RunnableJava.Awt.EventNs.InvocationEvent→Java.Lang.ThrowableJava.Awt.EventNs.KeyEvent→Java.Lang.StringJava.Awt.EventNs.MouseEvent→Java.Lang.String
- Direction
- Java.Awt.EventNs uses Java.Lang, so a change to Java.Lang can break Java.Awt.EventNs, while a change to Java.Awt.EventNs can't break Java.Lang.
- Position
- Below the diagonal: Java.Awt.EventNs uses a module listed above it, which is the healthy direction.
26→19 Java.Awt.EventNs uses Java.Text✕
- Connections
- 1 pair of types, where a type in Java.Awt.EventNs uses a type in Java.Text.
- The types involved
Java.Awt.EventNs.InputMethodEvent→Java.Text.AttributedCharacterIterator
- Direction
- Java.Awt.EventNs uses Java.Text, so a change to Java.Text can break Java.Awt.EventNs, while a change to Java.Awt.EventNs can't break Java.Text.
- Position
- Below the diagonal: Java.Awt.EventNs uses a module listed above it, which is the healthy direction.
26→39 Java.Awt.EventNs uses Java.Awt part of a loop✕
- Connections
- 29 pairs of types, where a type in Java.Awt.EventNs uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.EventNs.AWTEventListener→Java.Awt.AWTEventJava.Awt.EventNs.AWTEventListenerDirect→Java.Awt.AWTEventJava.Awt.EventNs.AWTEventListenerProxy→Java.Awt.AWTEventJava.Awt.EventNs.ActionEvent→Java.Awt.AWTEventJava.Awt.EventNs.AdjustmentEvent→Java.Awt.AWTEventJava.Awt.EventNs.AdjustmentEvent→Java.Awt.AdjustableJava.Awt.EventNs.ComponentEvent→Java.Awt.AWTEventJava.Awt.EventNs.ComponentEvent→Java.Awt.ComponentJava.Awt.EventNs.ContainerEvent→Java.Awt.ComponentJava.Awt.EventNs.ContainerEvent→Java.Awt.ContainerJava.Awt.EventNs.FocusEvent→Java.Awt.ComponentJava.Awt.EventNs.HierarchyEvent→Java.Awt.AWTEventJava.Awt.EventNs.HierarchyEvent→Java.Awt.ComponentJava.Awt.EventNs.HierarchyEvent→Java.Awt.ContainerJava.Awt.EventNs.IAWTEventListener→Java.Awt.AWTEventJava.Awt.EventNs.InputMethodEvent→Java.Awt.AWTEventJava.Awt.EventNs.InputMethodEvent→Java.Awt.ComponentJava.Awt.EventNs.InvocationEvent→Java.Awt.AWTEventJava.Awt.EventNs.InvocationEvent→Java.Awt.ActiveEventJava.Awt.EventNs.ItemEvent→Java.Awt.AWTEventJava.Awt.EventNs.ItemEvent→Java.Awt.ItemSelectableJava.Awt.EventNs.KeyEvent→Java.Awt.ComponentJava.Awt.EventNs.MouseEvent→Java.Awt.ComponentJava.Awt.EventNs.MouseEvent→Java.Awt.PointJava.Awt.EventNs.MouseWheelEvent→Java.Awt.Component
- Direction
- Java.Awt.EventNs uses Java.Awt, so a change to Java.Awt can break Java.Awt.EventNs, while a change to Java.Awt.EventNs can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→1 Java.Beans uses Java.Lang.Annotation✕
- Connections
- 4 pairs of types, where a type in Java.Beans uses a type in Java.Lang.Annotation.
- The types involved
Java.Beans.ConstructorProperties→Java.Lang.Annotation.AnnotationJava.Beans.IConstructorProperties→Java.Lang.Annotation.IAnnotationJava.Beans.ITransient→Java.Lang.Annotation.IAnnotationJava.Beans.Transient→Java.Lang.Annotation.Annotation
- Direction
- Java.Beans uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Java.Beans, while a change to Java.Beans can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→4 Java.Beans uses Java.Util✕
- Connections
- 6 pairs of types, where a type in Java.Beans uses a type in Java.Util.
- The types involved
Java.Beans.FeatureDescriptor→Java.Util.EnumerationJava.Beans.PropertyChangeEvent→Java.Util.EventObjectJava.Beans.PropertyChangeListener→Java.Util.EventListenerJava.Beans.PropertyChangeListenerProxy→Java.Util.EventListenerProxyJava.Beans.VetoableChangeListener→Java.Util.EventListenerJava.Beans.VetoableChangeListenerProxy→Java.Util.EventListenerProxy
- Direction
- Java.Beans uses Java.Util, so a change to Java.Util can break Java.Beans, while a change to Java.Beans can't break Java.Util.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→6 Java.Beans uses MASES.JNet.Specific✕
- Connections
- 3 pairs of types, where a type in Java.Beans uses a type in MASES.JNet.Specific.
- The types involved
Java.Beans.ExceptionListener→MASES.JNet.Specific.JNetEventDataJava.Beans.PropertyChangeListener→MASES.JNet.Specific.JNetEventDataJava.Beans.VetoableChangeListener→MASES.JNet.Specific.JNetEventData
- Direction
- Java.Beans uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Java.Beans, while a change to Java.Beans can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→14 Java.Beans uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Java.Beans uses a type in Java.Io.
- The types involved
Java.Beans.PropertyChangeSupport→Java.Io.SerializableJava.Beans.VetoableChangeSupport→Java.Io.SerializableJava.Beans.XMLDecoder→Java.Io.InputStreamJava.Beans.XMLEncoder→Java.Io.OutputStream
- Direction
- Java.Beans uses Java.Io, so a change to Java.Io can break Java.Beans, while a change to Java.Beans can't break Java.Io.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→15 Java.Beans uses Java.Lang.Reflect✕
- Connections
- 6 pairs of types, where a type in Java.Beans uses a type in Java.Lang.Reflect.
- The types involved
Java.Beans.EventHandler→Java.Lang.Reflect.InvocationHandlerJava.Beans.EventHandler→Java.Lang.Reflect.MethodJava.Beans.EventSetDescriptor→Java.Lang.Reflect.MethodJava.Beans.IndexedPropertyDescriptor→Java.Lang.Reflect.MethodJava.Beans.MethodDescriptor→Java.Lang.Reflect.MethodJava.Beans.PropertyDescriptor→Java.Lang.Reflect.Method
- Direction
- Java.Beans uses Java.Lang.Reflect, so a change to Java.Lang.Reflect can break Java.Beans, while a change to Java.Beans can't break Java.Lang.Reflect.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→16 Java.Beans uses Java.Lang✕
- Connections
- 39 pairs of types, where a type in Java.Beans uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Beans.BeanDescriptor→Java.Lang.ClassJava.Beans.Beans→Java.Lang.ClassJava.Beans.Beans→Java.Lang.ClassLoaderJava.Beans.Beans→Java.Lang.StringJava.Beans.ConstructorProperties→Java.Lang.StringJava.Beans.DefaultPersistenceDelegate→Java.Lang.StringJava.Beans.DesignMode→Java.Lang.StringJava.Beans.Encoder→Java.Lang.ClassJava.Beans.EventHandler→Java.Lang.ClassJava.Beans.EventHandler→Java.Lang.StringJava.Beans.EventSetDescriptor→Java.Lang.ClassJava.Beans.EventSetDescriptor→Java.Lang.StringJava.Beans.FeatureDescriptor→Java.Lang.StringJava.Beans.IConstructorProperties→Java.Lang.StringJava.Beans.IPropertyEditor→Java.Lang.StringJava.Beans.IndexedPropertyChangeEvent→Java.Lang.StringJava.Beans.IndexedPropertyDescriptor→Java.Lang.ClassJava.Beans.IndexedPropertyDescriptor→Java.Lang.StringJava.Beans.IntrospectionException→Java.Lang.ExceptionJava.Beans.Introspector→Java.Lang.ClassJava.Beans.Introspector→Java.Lang.StringJava.Beans.PropertyChangeEvent→Java.Lang.StringJava.Beans.PropertyChangeListenerProxy→Java.Lang.StringJava.Beans.PropertyChangeSupport→Java.Lang.StringJava.Beans.PropertyDescriptor→Java.Lang.Class
- Direction
- Java.Beans uses Java.Lang, so a change to Java.Lang can break Java.Beans, while a change to Java.Beans can't break Java.Lang.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→25 Java.Beans uses Org.Xml.Sax✕
- Connections
- 1 pair of types, where a type in Java.Beans uses a type in Org.Xml.Sax.
- The types involved
Java.Beans.XMLDecoder→Org.Xml.Sax.InputSource
- Direction
- Java.Beans uses Org.Xml.Sax, so a change to Org.Xml.Sax can break Java.Beans, while a change to Java.Beans can't break Org.Xml.Sax.
- Position
- Below the diagonal: Java.Beans uses a module listed above it, which is the healthy direction.
27→39 Java.Beans uses Java.Awt part of a loop✕
- Connections
- 12 pairs of types, where a type in Java.Beans uses a type in Java.Awt.
- The types involved
Java.Beans.BeanInfo→Java.Awt.ImageJava.Beans.IBeanInfo→Java.Awt.ImageJava.Beans.IPropertyEditor→Java.Awt.ComponentJava.Beans.IPropertyEditor→Java.Awt.GraphicsJava.Beans.IPropertyEditor→Java.Awt.RectangleJava.Beans.PropertyEditor→Java.Awt.ComponentJava.Beans.PropertyEditor→Java.Awt.GraphicsJava.Beans.PropertyEditor→Java.Awt.RectangleJava.Beans.PropertyEditorSupport→Java.Awt.ComponentJava.Beans.PropertyEditorSupport→Java.Awt.GraphicsJava.Beans.PropertyEditorSupport→Java.Awt.RectangleJava.Beans.SimpleBeanInfo→Java.Awt.Image
- Direction
- Java.Beans uses Java.Awt, so a change to Java.Awt can break Java.Beans, while a change to Java.Beans can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→4 Javax.Xml.Stream uses Java.Util✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Stream uses a type in Java.Util.
- The types involved
Javax.Xml.Stream.XMLEventFactory→Java.Util.Iterator
- Direction
- Javax.Xml.Stream uses Java.Util, so a change to Java.Util can break Javax.Xml.Stream, while a change to Javax.Xml.Stream can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Stream uses a module listed above it, which is the healthy direction.
28→14 Javax.Xml.Stream uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Javax.Xml.Stream uses a type in Java.Io.
- The types involved
Javax.Xml.Stream.XMLInputFactory→Java.Io.InputStreamJavax.Xml.Stream.XMLInputFactory→Java.Io.ReaderJavax.Xml.Stream.XMLOutputFactory→Java.Io.OutputStreamJavax.Xml.Stream.XMLOutputFactory→Java.Io.Writer
- Direction
- Javax.Xml.Stream uses Java.Io, so a change to Java.Io can break Javax.Xml.Stream, while a change to Javax.Xml.Stream can't break Java.Io.
- Position
- Below the diagonal: Javax.Xml.Stream uses a module listed above it, which is the healthy direction.
28→16 Javax.Xml.Stream uses Java.Lang✕
- Connections
- 22 pairs of types, where a type in Javax.Xml.Stream uses a type in Java.Lang.
- The types involved
Javax.Xml.Stream.FactoryConfigurationError→Java.Lang.ErrorJavax.Xml.Stream.ILocation→Java.Lang.StringJavax.Xml.Stream.IXMLEventReader→Java.Lang.StringJavax.Xml.Stream.IXMLEventWriter→Java.Lang.StringJavax.Xml.Stream.IXMLReporter→Java.Lang.StringJavax.Xml.Stream.IXMLResolver→Java.Lang.StringJavax.Xml.Stream.IXMLStreamReader→Java.Lang.StringJavax.Xml.Stream.IXMLStreamWriter→Java.Lang.StringJavax.Xml.Stream.Location→Java.Lang.StringJavax.Xml.Stream.XMLEventFactory→Java.Lang.ClassLoaderJavax.Xml.Stream.XMLEventFactory→Java.Lang.StringJavax.Xml.Stream.XMLEventReader→Java.Lang.StringJavax.Xml.Stream.XMLEventWriter→Java.Lang.StringJavax.Xml.Stream.XMLInputFactory→Java.Lang.ClassLoaderJavax.Xml.Stream.XMLInputFactory→Java.Lang.StringJavax.Xml.Stream.XMLOutputFactory→Java.Lang.ClassLoaderJavax.Xml.Stream.XMLOutputFactory→Java.Lang.StringJavax.Xml.Stream.XMLReporter→Java.Lang.StringJavax.Xml.Stream.XMLResolver→Java.Lang.StringJavax.Xml.Stream.XMLStreamException→Java.Lang.ExceptionJavax.Xml.Stream.XMLStreamReader→Java.Lang.StringJavax.Xml.Stream.XMLStreamWriter→Java.Lang.String
- Direction
- Javax.Xml.Stream uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Stream, while a change to Javax.Xml.Stream can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Stream uses a module listed above it, which is the healthy direction.
28→22 Javax.Xml.Stream uses Javax.Xml.Namespace✕
- Connections
- 10 pairs of types, where a type in Javax.Xml.Stream uses a type in Javax.Xml.Namespace.
- The types involved
Javax.Xml.Stream.IXMLEventWriter→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.IXMLStreamReader→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.IXMLStreamReader→Javax.Xml.Namespace.QNameJavax.Xml.Stream.IXMLStreamWriter→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.XMLEventFactory→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.XMLEventFactory→Javax.Xml.Namespace.QNameJavax.Xml.Stream.XMLEventWriter→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.XMLStreamReader→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Stream.XMLStreamReader→Javax.Xml.Namespace.QNameJavax.Xml.Stream.XMLStreamWriter→Javax.Xml.Namespace.NamespaceContext
- Direction
- Javax.Xml.Stream uses Javax.Xml.Namespace, so a change to Javax.Xml.Namespace can break Javax.Xml.Stream, while a change to Javax.Xml.Stream can't break Javax.Xml.Namespace.
- Position
- Below the diagonal: Javax.Xml.Stream uses a module listed above it, which is the healthy direction.
28→23 Javax.Xml.Stream uses Javax.Xml.Transform✕
- Connections
- 2 pairs of types, where a type in Javax.Xml.Stream uses a type in Javax.Xml.Transform.
- The types involved
Javax.Xml.Stream.XMLInputFactory→Javax.Xml.Transform.SourceJavax.Xml.Stream.XMLOutputFactory→Javax.Xml.Transform.Result
- Direction
- Javax.Xml.Stream uses Javax.Xml.Transform, so a change to Javax.Xml.Transform can break Javax.Xml.Stream, while a change to Javax.Xml.Stream can't break Javax.Xml.Transform.
- Position
- Below the diagonal: Javax.Xml.Stream uses a module listed above it, which is the healthy direction.
29→4 Javax.Swing.Tree uses Java.Util✕
- Connections
- 5 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Util.
- The types involved
Javax.Swing.Tree.AbstractLayoutCache→Java.Util.EnumerationJavax.Swing.Tree.DefaultMutableTreeNode→Java.Util.EnumerationJavax.Swing.Tree.DefaultTreeCellEditor→Java.Util.EventObjectJavax.Swing.Tree.ITreeNode→Java.Util.EnumerationJavax.Swing.Tree.TreeNode→Java.Util.Enumeration
- Direction
- Javax.Swing.Tree uses Java.Util, so a change to Java.Util can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Util.
- Position
- Below the diagonal: Javax.Swing.Tree uses a module listed above it, which is the healthy direction.
29→14 Javax.Swing.Tree uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Io.
- The types involved
Javax.Swing.Tree.DefaultMutableTreeNode→Java.Io.SerializableJavax.Swing.Tree.DefaultTreeModel→Java.Io.SerializableJavax.Swing.Tree.DefaultTreeSelectionModel→Java.Io.SerializableJavax.Swing.Tree.TreePath→Java.Io.Serializable
- Direction
- Javax.Swing.Tree uses Java.Io, so a change to Java.Io can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing.Tree uses a module listed above it, which is the healthy direction.
29→16 Javax.Swing.Tree uses Java.Lang✕
- Connections
- 6 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Lang.
- The types involved
Javax.Swing.Tree.DefaultMutableTreeNode→Java.Lang.CloneableJavax.Swing.Tree.DefaultTreeModel→Java.Lang.ClassJavax.Swing.Tree.DefaultTreeSelectionModel→Java.Lang.ClassJavax.Swing.Tree.DefaultTreeSelectionModel→Java.Lang.CloneableJavax.Swing.Tree.DefaultTreeSelectionModel→Java.Lang.StringJavax.Swing.Tree.ExpandVetoException→Java.Lang.Exception
- Direction
- Javax.Swing.Tree uses Java.Lang, so a change to Java.Lang can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing.Tree uses a module listed above it, which is the healthy direction.
29→26 Javax.Swing.Tree uses Java.Awt.EventNs✕
- Connections
- 2 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Awt.EventNs.
- The types involved
Javax.Swing.Tree.DefaultTreeCellEditor→Java.Awt.EventNs.ActionEventJavax.Swing.Tree.DefaultTreeCellEditor→Java.Awt.EventNs.ActionListener
- Direction
- Javax.Swing.Tree uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing.Tree uses a module listed above it, which is the healthy direction.
29→27 Javax.Swing.Tree uses Java.Beans✕
- Connections
- 3 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Beans.
- The types involved
Javax.Swing.Tree.DefaultTreeSelectionModel→Java.Beans.PropertyChangeListenerJavax.Swing.Tree.ITreeSelectionModel→Java.Beans.PropertyChangeListenerJavax.Swing.Tree.TreeSelectionModel→Java.Beans.PropertyChangeListener
- Direction
- Javax.Swing.Tree uses Java.Beans, so a change to Java.Beans can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Beans.
- Position
- Below the diagonal: Javax.Swing.Tree uses a module listed above it, which is the healthy direction.
29→31 Javax.Swing.Tree uses Javax.Swing.Event part of a loop✕
- Connections
- 10 pairs of types, where a type in Javax.Swing.Tree uses a type in Javax.Swing.Event.
- The types involved
Javax.Swing.Tree.AbstractLayoutCache→Javax.Swing.Event.TreeModelEventJavax.Swing.Tree.DefaultTreeCellEditor→Javax.Swing.Event.CellEditorListenerJavax.Swing.Tree.DefaultTreeCellEditor→Javax.Swing.Event.TreeSelectionEventJavax.Swing.Tree.DefaultTreeCellEditor→Javax.Swing.Event.TreeSelectionListenerJavax.Swing.Tree.DefaultTreeModel→Javax.Swing.Event.TreeModelListenerJavax.Swing.Tree.DefaultTreeSelectionModel→Javax.Swing.Event.TreeSelectionListenerJavax.Swing.Tree.ITreeModel→Javax.Swing.Event.TreeModelListenerJavax.Swing.Tree.ITreeSelectionModel→Javax.Swing.Event.TreeSelectionListenerJavax.Swing.Tree.TreeModel→Javax.Swing.Event.TreeModelListenerJavax.Swing.Tree.TreeSelectionModel→Javax.Swing.Event.TreeSelectionListener
- Direction
- Javax.Swing.Tree uses Javax.Swing.Event, so a change to Javax.Swing.Event can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Javax.Swing.Event.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→34 Javax.Swing.Tree uses Javax.Swing part of a loop✕
- Connections
- 11 pairs of types, where a type in Javax.Swing.Tree uses a type in Javax.Swing.
- The types involved
Javax.Swing.Tree.DefaultTextField→Javax.Swing.JTextFieldJavax.Swing.Tree.DefaultTreeCellEditor→Javax.Swing.JTreeJavax.Swing.Tree.DefaultTreeCellRenderer→Javax.Swing.IconJavax.Swing.Tree.DefaultTreeCellRenderer→Javax.Swing.JLabelJavax.Swing.Tree.DefaultTreeCellRenderer→Javax.Swing.JTreeJavax.Swing.Tree.ITreeCellEditor→Javax.Swing.ICellEditorJavax.Swing.Tree.ITreeCellEditor→Javax.Swing.JTreeJavax.Swing.Tree.ITreeCellRenderer→Javax.Swing.JTreeJavax.Swing.Tree.TreeCellEditor→Javax.Swing.CellEditorJavax.Swing.Tree.TreeCellEditor→Javax.Swing.JTreeJavax.Swing.Tree.TreeCellRenderer→Javax.Swing.JTree
- Direction
- Javax.Swing.Tree uses Javax.Swing, so a change to Javax.Swing can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Javax.Swing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
29→39 Javax.Swing.Tree uses Java.Awt part of a loop✕
- Connections
- 12 pairs of types, where a type in Javax.Swing.Tree uses a type in Java.Awt.
- The types involved
Javax.Swing.Tree.AbstractLayoutCache→Java.Awt.RectangleJavax.Swing.Tree.DefaultTreeCellEditor→Java.Awt.ColorJavax.Swing.Tree.DefaultTreeCellEditor→Java.Awt.ComponentJavax.Swing.Tree.DefaultTreeCellEditor→Java.Awt.FontJavax.Swing.Tree.DefaultTreeCellRenderer→Java.Awt.ColorJavax.Swing.Tree.DefaultTreeCellRenderer→Java.Awt.ComponentJavax.Swing.Tree.EditorContainer→Java.Awt.ContainerJavax.Swing.Tree.ITreeCellEditor→Java.Awt.ComponentJavax.Swing.Tree.ITreeCellRenderer→Java.Awt.ComponentJavax.Swing.Tree.NodeDimensions→Java.Awt.RectangleJavax.Swing.Tree.TreeCellEditor→Java.Awt.ComponentJavax.Swing.Tree.TreeCellRenderer→Java.Awt.Component
- Direction
- Javax.Swing.Tree uses Java.Awt, so a change to Java.Awt can break Javax.Swing.Tree, while a change to Javax.Swing.Tree can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→4 Javax.Xml.Bind uses Java.Util✕
- Connections
- 4 pairs of types, where a type in Javax.Xml.Bind uses a type in Java.Util.
- The types involved
Javax.Xml.Bind.DatatypeConverter→Java.Util.CalendarJavax.Xml.Bind.DatatypeConverterInterface→Java.Util.CalendarJavax.Xml.Bind.IDatatypeConverterInterface→Java.Util.CalendarJavax.Xml.Bind.JAXBContext→Java.Util.Map
- Direction
- Javax.Xml.Bind uses Java.Util, so a change to Java.Util can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→5 Javax.Xml.Bind uses Java.Math✕
- Connections
- 6 pairs of types, where a type in Javax.Xml.Bind uses a type in Java.Math.
- The types involved
Javax.Xml.Bind.DatatypeConverter→Java.Math.BigDecimalJavax.Xml.Bind.DatatypeConverter→Java.Math.BigIntegerJavax.Xml.Bind.DatatypeConverterInterface→Java.Math.BigDecimalJavax.Xml.Bind.DatatypeConverterInterface→Java.Math.BigIntegerJavax.Xml.Bind.IDatatypeConverterInterface→Java.Math.BigDecimalJavax.Xml.Bind.IDatatypeConverterInterface→Java.Math.BigInteger
- Direction
- Javax.Xml.Bind uses Java.Math, so a change to Java.Math can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Math.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→8 Javax.Xml.Bind uses Java.Security✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Bind uses a type in Java.Security.
- The types involved
Javax.Xml.Bind.JAXBPermission→Java.Security.BasicPermission
- Direction
- Javax.Xml.Bind uses Java.Security, so a change to Java.Security can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Security.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→13 Javax.Xml.Bind uses Java.Net✕
- Connections
- 6 pairs of types, where a type in Javax.Xml.Bind uses a type in Java.Net.
- The types involved
Javax.Xml.Bind.IUnmarshaller→Java.Net.URLJavax.Xml.Bind.IValidationEventLocator→Java.Net.URLJavax.Xml.Bind.JAXB→Java.Net.URIJavax.Xml.Bind.JAXB→Java.Net.URLJavax.Xml.Bind.Unmarshaller→Java.Net.URLJavax.Xml.Bind.ValidationEventLocator→Java.Net.URL
- Direction
- Javax.Xml.Bind uses Java.Net, so a change to Java.Net can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Net.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→14 Javax.Xml.Bind uses Java.Io✕
- Connections
- 18 pairs of types, where a type in Javax.Xml.Bind uses a type in Java.Io.
- The types involved
Javax.Xml.Bind.IMarshaller→Java.Io.FileJavax.Xml.Bind.IMarshaller→Java.Io.OutputStreamJavax.Xml.Bind.IMarshaller→Java.Io.WriterJavax.Xml.Bind.IUnmarshaller→Java.Io.FileJavax.Xml.Bind.IUnmarshaller→Java.Io.InputStreamJavax.Xml.Bind.IUnmarshaller→Java.Io.ReaderJavax.Xml.Bind.JAXB→Java.Io.FileJavax.Xml.Bind.JAXB→Java.Io.InputStreamJavax.Xml.Bind.JAXB→Java.Io.OutputStreamJavax.Xml.Bind.JAXB→Java.Io.ReaderJavax.Xml.Bind.JAXB→Java.Io.WriterJavax.Xml.Bind.JAXBElement→Java.Io.SerializableJavax.Xml.Bind.Marshaller→Java.Io.FileJavax.Xml.Bind.Marshaller→Java.Io.OutputStreamJavax.Xml.Bind.Marshaller→Java.Io.WriterJavax.Xml.Bind.Unmarshaller→Java.Io.FileJavax.Xml.Bind.Unmarshaller→Java.Io.InputStreamJavax.Xml.Bind.Unmarshaller→Java.Io.Reader
- Direction
- Javax.Xml.Bind uses Java.Io, so a change to Java.Io can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Io.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→16 Javax.Xml.Bind uses Java.Lang✕
- Connections
- 30 pairs of types, where a type in Javax.Xml.Bind uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Xml.Bind.Binder→Java.Lang.ClassJavax.Xml.Bind.Binder→Java.Lang.StringJavax.Xml.Bind.DataBindingException→Java.Lang.RuntimeExceptionJavax.Xml.Bind.DatatypeConverter→Java.Lang.StringJavax.Xml.Bind.DatatypeConverterInterface→Java.Lang.StringJavax.Xml.Bind.IDatatypeConverterInterface→Java.Lang.StringJavax.Xml.Bind.IMarshaller→Java.Lang.ClassJavax.Xml.Bind.IMarshaller→Java.Lang.StringJavax.Xml.Bind.IUnmarshaller→Java.Lang.ClassJavax.Xml.Bind.IUnmarshaller→Java.Lang.StringJavax.Xml.Bind.IValidationEvent→Java.Lang.StringJavax.Xml.Bind.IValidationEvent→Java.Lang.ThrowableJavax.Xml.Bind.IValidator→Java.Lang.StringJavax.Xml.Bind.JAXB→Java.Lang.ClassJavax.Xml.Bind.JAXB→Java.Lang.StringJavax.Xml.Bind.JAXBContext→Java.Lang.ClassJavax.Xml.Bind.JAXBContext→Java.Lang.ClassLoaderJavax.Xml.Bind.JAXBContext→Java.Lang.StringJavax.Xml.Bind.JAXBElement→Java.Lang.ClassJavax.Xml.Bind.JAXBException→Java.Lang.ExceptionJavax.Xml.Bind.JAXBPermission→Java.Lang.StringJavax.Xml.Bind.Marshaller→Java.Lang.ClassJavax.Xml.Bind.Marshaller→Java.Lang.StringJavax.Xml.Bind.SchemaOutputResolver→Java.Lang.StringJavax.Xml.Bind.TypeConstraintException→Java.Lang.RuntimeException
- Direction
- Javax.Xml.Bind uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→22 Javax.Xml.Bind uses Javax.Xml.Namespace✕
- Connections
- 8 pairs of types, where a type in Javax.Xml.Bind uses a type in Javax.Xml.Namespace.
- The types involved
Javax.Xml.Bind.DatatypeConverter→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Bind.DatatypeConverter→Javax.Xml.Namespace.QNameJavax.Xml.Bind.DatatypeConverterInterface→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Bind.DatatypeConverterInterface→Javax.Xml.Namespace.QNameJavax.Xml.Bind.IDatatypeConverterInterface→Javax.Xml.Namespace.NamespaceContextJavax.Xml.Bind.IDatatypeConverterInterface→Javax.Xml.Namespace.QNameJavax.Xml.Bind.JAXBElement→Javax.Xml.Namespace.QNameJavax.Xml.Bind.JAXBIntrospector→Javax.Xml.Namespace.QName
- Direction
- Javax.Xml.Bind uses Javax.Xml.Namespace, so a change to Javax.Xml.Namespace can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Javax.Xml.Namespace.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→23 Javax.Xml.Bind uses Javax.Xml.Transform✕
- Connections
- 7 pairs of types, where a type in Javax.Xml.Bind uses a type in Javax.Xml.Transform.
- The types involved
Javax.Xml.Bind.IMarshaller→Javax.Xml.Transform.ResultJavax.Xml.Bind.IUnmarshaller→Javax.Xml.Transform.SourceJavax.Xml.Bind.JAXB→Javax.Xml.Transform.ResultJavax.Xml.Bind.JAXB→Javax.Xml.Transform.SourceJavax.Xml.Bind.Marshaller→Javax.Xml.Transform.ResultJavax.Xml.Bind.SchemaOutputResolver→Javax.Xml.Transform.ResultJavax.Xml.Bind.Unmarshaller→Javax.Xml.Transform.Source
- Direction
- Javax.Xml.Bind uses Javax.Xml.Transform, so a change to Javax.Xml.Transform can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Javax.Xml.Transform.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→24 Javax.Xml.Bind uses Org.W3c.Dom✕
- Connections
- 7 pairs of types, where a type in Javax.Xml.Bind uses a type in Org.W3c.Dom.
- The types involved
Javax.Xml.Bind.IMarshaller→Org.W3c.Dom.NodeJavax.Xml.Bind.IUnmarshaller→Org.W3c.Dom.NodeJavax.Xml.Bind.IValidationEventLocator→Org.W3c.Dom.NodeJavax.Xml.Bind.JAXBContext→Org.W3c.Dom.NodeJavax.Xml.Bind.Marshaller→Org.W3c.Dom.NodeJavax.Xml.Bind.Unmarshaller→Org.W3c.Dom.NodeJavax.Xml.Bind.ValidationEventLocator→Org.W3c.Dom.Node
- Direction
- Javax.Xml.Bind uses Org.W3c.Dom, so a change to Org.W3c.Dom can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Org.W3c.Dom.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→25 Javax.Xml.Bind uses Org.Xml.Sax✕
- Connections
- 6 pairs of types, where a type in Javax.Xml.Bind uses a type in Org.Xml.Sax.
- The types involved
Javax.Xml.Bind.IMarshaller→Org.Xml.Sax.ContentHandlerJavax.Xml.Bind.IUnmarshaller→Org.Xml.Sax.InputSourceJavax.Xml.Bind.IUnmarshallerHandler→Org.Xml.Sax.IContentHandlerJavax.Xml.Bind.Marshaller→Org.Xml.Sax.ContentHandlerJavax.Xml.Bind.Unmarshaller→Org.Xml.Sax.InputSourceJavax.Xml.Bind.UnmarshallerHandler→Org.Xml.Sax.ContentHandler
- Direction
- Javax.Xml.Bind uses Org.Xml.Sax, so a change to Org.Xml.Sax can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Org.Xml.Sax.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
30→28 Javax.Xml.Bind uses Javax.Xml.Stream✕
- Connections
- 8 pairs of types, where a type in Javax.Xml.Bind uses a type in Javax.Xml.Stream.
- The types involved
Javax.Xml.Bind.IMarshaller→Javax.Xml.Stream.XMLEventWriterJavax.Xml.Bind.IMarshaller→Javax.Xml.Stream.XMLStreamWriterJavax.Xml.Bind.IUnmarshaller→Javax.Xml.Stream.XMLEventReaderJavax.Xml.Bind.IUnmarshaller→Javax.Xml.Stream.XMLStreamReaderJavax.Xml.Bind.Marshaller→Javax.Xml.Stream.XMLEventWriterJavax.Xml.Bind.Marshaller→Javax.Xml.Stream.XMLStreamWriterJavax.Xml.Bind.Unmarshaller→Javax.Xml.Stream.XMLEventReaderJavax.Xml.Bind.Unmarshaller→Javax.Xml.Stream.XMLStreamReader
- Direction
- Javax.Xml.Bind uses Javax.Xml.Stream, so a change to Javax.Xml.Stream can break Javax.Xml.Bind, while a change to Javax.Xml.Bind can't break Javax.Xml.Stream.
- Position
- Below the diagonal: Javax.Xml.Bind uses a module listed above it, which is the healthy direction.
31→4 Javax.Swing.Event uses Java.Util✕
- Connections
- 35 pairs of types, where a type in Javax.Swing.Event uses a type in Java.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Event.AncestorListener→Java.Util.EventListenerJavax.Swing.Event.CaretEvent→Java.Util.EventObjectJavax.Swing.Event.CaretListener→Java.Util.EventListenerJavax.Swing.Event.CellEditorListener→Java.Util.EventListenerJavax.Swing.Event.ChangeEvent→Java.Util.EventObjectJavax.Swing.Event.ChangeListener→Java.Util.EventListenerJavax.Swing.Event.DocumentListener→Java.Util.EventListenerJavax.Swing.Event.HyperlinkEvent→Java.Util.EventObjectJavax.Swing.Event.HyperlinkListener→Java.Util.EventListenerJavax.Swing.Event.InternalFrameListener→Java.Util.EventListenerJavax.Swing.Event.ListDataEvent→Java.Util.EventObjectJavax.Swing.Event.ListDataListener→Java.Util.EventListenerJavax.Swing.Event.ListSelectionEvent→Java.Util.EventObjectJavax.Swing.Event.ListSelectionListener→Java.Util.EventListenerJavax.Swing.Event.MenuDragMouseListener→Java.Util.EventListenerJavax.Swing.Event.MenuEvent→Java.Util.EventObjectJavax.Swing.Event.MenuKeyListener→Java.Util.EventListenerJavax.Swing.Event.MenuListener→Java.Util.EventListenerJavax.Swing.Event.PopupMenuEvent→Java.Util.EventObjectJavax.Swing.Event.PopupMenuListener→Java.Util.EventListenerJavax.Swing.Event.RowSorterEvent→Java.Util.EventObjectJavax.Swing.Event.RowSorterListener→Java.Util.EventListenerJavax.Swing.Event.TableColumnModelEvent→Java.Util.EventObjectJavax.Swing.Event.TableColumnModelListener→Java.Util.EventListenerJavax.Swing.Event.TableModelEvent→Java.Util.EventObject
- Direction
- Javax.Swing.Event uses Java.Util, so a change to Java.Util can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Util.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→6 Javax.Swing.Event uses MASES.JNet.Specific✕
- Connections
- 24 pairs of types, where a type in Javax.Swing.Event uses a type in MASES.JNet.Specific.
- The types involved
Javax.Swing.Event.AncestorListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.CaretListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.CellEditorListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.ChangeListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.DocumentListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.HyperlinkListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.InternalFrameAdapter→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.InternalFrameListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.ListDataListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.ListSelectionListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.MenuDragMouseListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.MenuKeyListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.MenuListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.MouseInputAdapter→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.MouseInputListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.PopupMenuListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.RowSorterListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TableColumnModelListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TableModelListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TreeExpansionListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TreeModelListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TreeSelectionListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.TreeWillExpandListener→MASES.JNet.Specific.JNetEventDataJavax.Swing.Event.UndoableEditListener→MASES.JNet.Specific.JNetEventData
- Direction
- Javax.Swing.Event uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→13 Javax.Swing.Event uses Java.Net✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Event uses a type in Java.Net.
- The types involved
Javax.Swing.Event.HyperlinkEvent→Java.Net.URL
- Direction
- Javax.Swing.Event uses Java.Net, so a change to Java.Net can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Net.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→14 Javax.Swing.Event uses Java.Io✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Event uses a type in Java.Io.
- The types involved
Javax.Swing.Event.EventListenerList→Java.Io.Serializable
- Direction
- Javax.Swing.Event uses Java.Io, so a change to Java.Io can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→16 Javax.Swing.Event uses Java.Lang✕
- Connections
- 4 pairs of types, where a type in Javax.Swing.Event uses a type in Java.Lang.
- The types involved
Javax.Swing.Event.EventListenerList→Java.Lang.ClassJavax.Swing.Event.HyperlinkEvent→Java.Lang.StringJavax.Swing.Event.Type→Java.Lang.EnumJavax.Swing.Event.Type→Java.Lang.String
- Direction
- Javax.Swing.Event uses Java.Lang, so a change to Java.Lang can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→26 Javax.Swing.Event uses Java.Awt.EventNs✕
- Connections
- 12 pairs of types, where a type in Javax.Swing.Event uses a type in Java.Awt.EventNs.
- The types involved
Javax.Swing.Event.HyperlinkEvent→Java.Awt.EventNs.InputEventJavax.Swing.Event.IMouseInputAdapter→Java.Awt.EventNs.MouseEventJavax.Swing.Event.IMouseInputAdapter→Java.Awt.EventNs.MouseWheelEventJavax.Swing.Event.IMouseInputListener→Java.Awt.EventNs.MouseEventJavax.Swing.Event.MenuDragMouseEvent→Java.Awt.EventNs.MouseEventJavax.Swing.Event.MenuKeyEvent→Java.Awt.EventNs.KeyEventJavax.Swing.Event.MouseInputAdapter→Java.Awt.EventNs.MouseEventJavax.Swing.Event.MouseInputAdapter→Java.Awt.EventNs.MouseWheelEventJavax.Swing.Event.MouseInputAdapterDirect→Java.Awt.EventNs.MouseEventJavax.Swing.Event.MouseInputAdapterDirect→Java.Awt.EventNs.MouseWheelEventJavax.Swing.Event.MouseInputListener→Java.Awt.EventNs.MouseEventJavax.Swing.Event.MouseInputListenerDirect→Java.Awt.EventNs.MouseEvent
- Direction
- Javax.Swing.Event uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→27 Javax.Swing.Event uses Java.Beans✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Event uses a type in Java.Beans.
- The types involved
Javax.Swing.Event.SwingPropertyChangeSupport→Java.Beans.PropertyChangeSupport
- Direction
- Javax.Swing.Event uses Java.Beans, so a change to Java.Beans can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Beans.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→29 Javax.Swing.Event uses Javax.Swing.Tree✕
- Connections
- 3 pairs of types, where a type in Javax.Swing.Event uses a type in Javax.Swing.Tree.
- The types involved
Javax.Swing.Event.TreeExpansionEvent→Javax.Swing.Tree.TreePathJavax.Swing.Event.TreeModelEvent→Javax.Swing.Tree.TreePathJavax.Swing.Event.TreeSelectionEvent→Javax.Swing.Tree.TreePath
- Direction
- Javax.Swing.Event uses Javax.Swing.Tree, so a change to Javax.Swing.Tree can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Javax.Swing.Tree.
- Position
- Below the diagonal: Javax.Swing.Event uses a module listed above it, which is the healthy direction.
31→34 Javax.Swing.Event uses Javax.Swing part of a loop✕
- Connections
- 7 pairs of types, where a type in Javax.Swing.Event uses a type in Javax.Swing.
- The types involved
Javax.Swing.Event.AncestorEvent→Javax.Swing.JComponentJavax.Swing.Event.InternalFrameEvent→Javax.Swing.JInternalFrameJavax.Swing.Event.MenuDragMouseEvent→Javax.Swing.MenuElementJavax.Swing.Event.MenuDragMouseEvent→Javax.Swing.MenuSelectionManagerJavax.Swing.Event.MenuKeyEvent→Javax.Swing.MenuElementJavax.Swing.Event.MenuKeyEvent→Javax.Swing.MenuSelectionManagerJavax.Swing.Event.RowSorterEvent→Javax.Swing.RowSorter
- Direction
- Javax.Swing.Event uses Javax.Swing, so a change to Javax.Swing can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Javax.Swing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→37 Javax.Swing.Event uses Javax.Swing.Text part of a loop✕
- Connections
- 6 pairs of types, where a type in Javax.Swing.Event uses a type in Javax.Swing.Text.
- The types involved
Javax.Swing.Event.DocumentEvent→Javax.Swing.Text.DocumentJavax.Swing.Event.DocumentEvent→Javax.Swing.Text.ElementJavax.Swing.Event.ElementChange→Javax.Swing.Text.ElementJavax.Swing.Event.HyperlinkEvent→Javax.Swing.Text.ElementJavax.Swing.Event.IDocumentEvent→Javax.Swing.Text.DocumentJavax.Swing.Event.IDocumentEvent→Javax.Swing.Text.Element
- Direction
- Javax.Swing.Event uses Javax.Swing.Text, so a change to Javax.Swing.Text can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Javax.Swing.Text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→39 Javax.Swing.Event uses Java.Awt part of a loop✕
- Connections
- 5 pairs of types, where a type in Javax.Swing.Event uses a type in Java.Awt.
- The types involved
Javax.Swing.Event.AncestorEvent→Java.Awt.AWTEventJavax.Swing.Event.AncestorEvent→Java.Awt.ContainerJavax.Swing.Event.InternalFrameEvent→Java.Awt.AWTEventJavax.Swing.Event.MenuDragMouseEvent→Java.Awt.ComponentJavax.Swing.Event.MenuKeyEvent→Java.Awt.Component
- Direction
- Javax.Swing.Event uses Java.Awt, so a change to Java.Awt can break Javax.Swing.Event, while a change to Javax.Swing.Event can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→14 Javax.Swing.Plaf uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Javax.Swing.Plaf uses a type in Java.Io.
- The types involved
Javax.Swing.Plaf.BorderUIResource→Java.Io.SerializableJavax.Swing.Plaf.FileChooserUI→Java.Io.FileJavax.Swing.Plaf.IconUIResource→Java.Io.SerializableJavax.Swing.Plaf.LayerUI→Java.Io.Serializable
- Direction
- Javax.Swing.Plaf uses Java.Io, so a change to Java.Io can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing.Plaf uses a module listed above it, which is the healthy direction.
32→16 Javax.Swing.Plaf uses Java.Lang✕
- Connections
- 5 pairs of types, where a type in Javax.Swing.Plaf uses a type in Java.Lang.
- The types involved
Javax.Swing.Plaf.FileChooserUI→Java.Lang.StringJavax.Swing.Plaf.FontUIResource→Java.Lang.StringJavax.Swing.Plaf.LayerUI→Java.Lang.StringJavax.Swing.Plaf.TextUI→Java.Lang.StringJavax.Swing.Plaf.TitledBorderUIResource→Java.Lang.String
- Direction
- Javax.Swing.Plaf uses Java.Lang, so a change to Java.Lang can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing.Plaf uses a module listed above it, which is the healthy direction.
32→26 Javax.Swing.Plaf uses Java.Awt.EventNs✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Plaf uses a type in Java.Awt.EventNs.
- The types involved
Javax.Swing.Plaf.PopupMenuUI→Java.Awt.EventNs.MouseEvent
- Direction
- Javax.Swing.Plaf uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing.Plaf uses a module listed above it, which is the healthy direction.
32→27 Javax.Swing.Plaf uses Java.Beans✕
- Connections
- 2 pairs of types, where a type in Javax.Swing.Plaf uses a type in Java.Beans.
- The types involved
Javax.Swing.Plaf.LayerUI→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.LayerUI→Java.Beans.PropertyChangeListener
- Direction
- Javax.Swing.Plaf uses Java.Beans, so a change to Java.Beans can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Java.Beans.
- Position
- Below the diagonal: Javax.Swing.Plaf uses a module listed above it, which is the healthy direction.
32→29 Javax.Swing.Plaf uses Javax.Swing.Tree✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Plaf uses a type in Javax.Swing.Tree.
- The types involved
Javax.Swing.Plaf.TreeUI→Javax.Swing.Tree.TreePath
- Direction
- Javax.Swing.Plaf uses Javax.Swing.Tree, so a change to Javax.Swing.Tree can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Javax.Swing.Tree.
- Position
- Below the diagonal: Javax.Swing.Plaf uses a module listed above it, which is the healthy direction.
32→34 Javax.Swing.Plaf uses Javax.Swing part of a loop✕
- Connections
- 18 pairs of types, where a type in Javax.Swing.Plaf uses a type in Javax.Swing.
- The types involved
Javax.Swing.Plaf.ActionMapUIResource→Javax.Swing.ActionMapJavax.Swing.Plaf.ComboBoxUI→Javax.Swing.JComboBoxJavax.Swing.Plaf.ComponentInputMapUIResource→Javax.Swing.ComponentInputMapJavax.Swing.Plaf.ComponentInputMapUIResource→Javax.Swing.JComponentJavax.Swing.Plaf.ComponentUI→Javax.Swing.JComponentJavax.Swing.Plaf.FileChooserUI→Javax.Swing.JButtonJavax.Swing.Plaf.FileChooserUI→Javax.Swing.JFileChooserJavax.Swing.Plaf.IconUIResource→Javax.Swing.IconJavax.Swing.Plaf.InputMapUIResource→Javax.Swing.InputMapJavax.Swing.Plaf.LayerUI→Javax.Swing.JLayerJavax.Swing.Plaf.ListUI→Javax.Swing.JListJavax.Swing.Plaf.MatteBorderUIResource→Javax.Swing.IconJavax.Swing.Plaf.OptionPaneUI→Javax.Swing.JOptionPaneJavax.Swing.Plaf.PopupMenuUI→Javax.Swing.JPopupMenuJavax.Swing.Plaf.PopupMenuUI→Javax.Swing.PopupJavax.Swing.Plaf.SplitPaneUI→Javax.Swing.JSplitPaneJavax.Swing.Plaf.TabbedPaneUI→Javax.Swing.JTabbedPaneJavax.Swing.Plaf.TreeUI→Javax.Swing.JTree
- Direction
- Javax.Swing.Plaf uses Javax.Swing, so a change to Javax.Swing can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Javax.Swing.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→37 Javax.Swing.Plaf uses Javax.Swing.Text part of a loop✕
- Connections
- 4 pairs of types, where a type in Javax.Swing.Plaf uses a type in Javax.Swing.Text.
- The types involved
Javax.Swing.Plaf.TextUI→Javax.Swing.Text.BiasJavax.Swing.Plaf.TextUI→Javax.Swing.Text.EditorKitJavax.Swing.Plaf.TextUI→Javax.Swing.Text.JTextComponentJavax.Swing.Plaf.TextUI→Javax.Swing.Text.View
- Direction
- Javax.Swing.Plaf uses Javax.Swing.Text, so a change to Javax.Swing.Text can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Javax.Swing.Text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→38 Javax.Swing.Plaf uses Javax.Accessibility part of a loop✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Plaf uses a type in Javax.Accessibility.
- The types involved
Javax.Swing.Plaf.ComponentUI→Javax.Accessibility.Accessible
- Direction
- Javax.Swing.Plaf uses Javax.Accessibility, so a change to Javax.Accessibility can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Javax.Accessibility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→39 Javax.Swing.Plaf uses Java.Awt part of a loop✕
- Connections
- 27 pairs of types, where a type in Javax.Swing.Plaf uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Plaf.BevelBorderUIResource→Java.Awt.ColorJavax.Swing.Plaf.BorderUIResource→Java.Awt.ComponentJavax.Swing.Plaf.BorderUIResource→Java.Awt.GraphicsJavax.Swing.Plaf.BorderUIResource→Java.Awt.InsetsJavax.Swing.Plaf.ColorUIResource→Java.Awt.ColorJavax.Swing.Plaf.ComponentUI→Java.Awt.BaselineResizeBehaviorJavax.Swing.Plaf.ComponentUI→Java.Awt.DimensionJavax.Swing.Plaf.ComponentUI→Java.Awt.GraphicsJavax.Swing.Plaf.DimensionUIResource→Java.Awt.DimensionJavax.Swing.Plaf.EmptyBorderUIResource→Java.Awt.InsetsJavax.Swing.Plaf.EtchedBorderUIResource→Java.Awt.ColorJavax.Swing.Plaf.FontUIResource→Java.Awt.FontJavax.Swing.Plaf.IconUIResource→Java.Awt.ComponentJavax.Swing.Plaf.IconUIResource→Java.Awt.GraphicsJavax.Swing.Plaf.InsetsUIResource→Java.Awt.InsetsJavax.Swing.Plaf.LayerUI→Java.Awt.AWTEventJavax.Swing.Plaf.LineBorderUIResource→Java.Awt.ColorJavax.Swing.Plaf.ListUI→Java.Awt.PointJavax.Swing.Plaf.ListUI→Java.Awt.RectangleJavax.Swing.Plaf.MatteBorderUIResource→Java.Awt.ColorJavax.Swing.Plaf.SplitPaneUI→Java.Awt.GraphicsJavax.Swing.Plaf.TabbedPaneUI→Java.Awt.RectangleJavax.Swing.Plaf.TextUI→Java.Awt.PointJavax.Swing.Plaf.TextUI→Java.Awt.RectangleJavax.Swing.Plaf.TitledBorderUIResource→Java.Awt.Color
- Direction
- Javax.Swing.Plaf uses Java.Awt, so a change to Java.Awt can break Javax.Swing.Plaf, while a change to Javax.Swing.Plaf can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→1 Javax.Xml.Ws uses Java.Lang.Annotation✕
- Connections
- 26 pairs of types, where a type in Javax.Xml.Ws uses a type in Java.Lang.Annotation. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Xml.Ws.Action→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.BindingType→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.FaultAction→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.IAction→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IBindingType→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IFaultAction→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IRequestWrapper→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IRespectBinding→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IResponseWrapper→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IServiceMode→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebEndpoint→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebFault→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebServiceClient→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebServiceProvider→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebServiceRef→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.IWebServiceRefs→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.RequestWrapper→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.RespectBinding→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.ResponseWrapper→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.ServiceMode→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.WebEndpoint→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.WebFault→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.WebServiceClient→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.WebServiceProvider→Java.Lang.Annotation.AnnotationJavax.Xml.Ws.WebServiceRef→Java.Lang.Annotation.Annotation
- Direction
- Javax.Xml.Ws uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→4 Javax.Xml.Ws uses Java.Util✕
- Connections
- 10 pairs of types, where a type in Javax.Xml.Ws uses a type in Java.Util.
- The types involved
Javax.Xml.Ws.Binding→Java.Util.ListJavax.Xml.Ws.BindingProvider→Java.Util.MapJavax.Xml.Ws.Endpoint→Java.Util.ListJavax.Xml.Ws.Endpoint→Java.Util.MapJavax.Xml.Ws.EndpointContext→Java.Util.SetJavax.Xml.Ws.IBinding→Java.Util.ListJavax.Xml.Ws.IBindingProvider→Java.Util.MapJavax.Xml.Ws.IResponse→Java.Util.MapJavax.Xml.Ws.Response→Java.Util.MapJavax.Xml.Ws.Service→Java.Util.Iterator
- Direction
- Javax.Xml.Ws uses Java.Util, so a change to Java.Util can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→8 Javax.Xml.Ws uses Java.Security✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Ws uses a type in Java.Security.
- The types involved
Javax.Xml.Ws.IWebServiceContext→Java.Security.PrincipalJavax.Xml.Ws.WebServiceContext→Java.Security.PrincipalJavax.Xml.Ws.WebServicePermission→Java.Security.BasicPermission
- Direction
- Javax.Xml.Ws uses Java.Security, so a change to Java.Security can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Security.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→9 Javax.Xml.Ws uses Java.Util.Concurrent✕
- Connections
- 6 pairs of types, where a type in Javax.Xml.Ws uses a type in Java.Util.Concurrent.
- The types involved
Javax.Xml.Ws.Dispatch→Java.Util.Concurrent.FutureJavax.Xml.Ws.Endpoint→Java.Util.Concurrent.ExecutorJavax.Xml.Ws.IDispatch→Java.Util.Concurrent.FutureJavax.Xml.Ws.IResponse→Java.Util.Concurrent.IFutureJavax.Xml.Ws.Response→Java.Util.Concurrent.FutureJavax.Xml.Ws.Service→Java.Util.Concurrent.Executor
- Direction
- Javax.Xml.Ws uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→13 Javax.Xml.Ws uses Java.Net✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws uses a type in Java.Net.
- The types involved
Javax.Xml.Ws.Service→Java.Net.URL
- Direction
- Javax.Xml.Ws uses Java.Net, so a change to Java.Net can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Net.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→14 Javax.Xml.Ws uses Java.Io✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws uses a type in Java.Io.
- The types involved
Javax.Xml.Ws.Holder→Java.Io.Serializable
- Direction
- Javax.Xml.Ws uses Java.Io, so a change to Java.Io can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Io.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→16 Javax.Xml.Ws uses Java.Lang✕
- Connections
- 46 pairs of types, where a type in Javax.Xml.Ws uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Xml.Ws.Action→Java.Lang.StringJavax.Xml.Ws.Binding→Java.Lang.StringJavax.Xml.Ws.BindingProvider→Java.Lang.ClassJavax.Xml.Ws.BindingProvider→Java.Lang.StringJavax.Xml.Ws.BindingType→Java.Lang.StringJavax.Xml.Ws.Endpoint→Java.Lang.ClassJavax.Xml.Ws.Endpoint→Java.Lang.StringJavax.Xml.Ws.EndpointReference→Java.Lang.ClassJavax.Xml.Ws.FaultAction→Java.Lang.ClassJavax.Xml.Ws.FaultAction→Java.Lang.StringJavax.Xml.Ws.IAction→Java.Lang.StringJavax.Xml.Ws.IBinding→Java.Lang.StringJavax.Xml.Ws.IBindingProvider→Java.Lang.ClassJavax.Xml.Ws.IBindingProvider→Java.Lang.StringJavax.Xml.Ws.IBindingType→Java.Lang.StringJavax.Xml.Ws.IFaultAction→Java.Lang.ClassJavax.Xml.Ws.IFaultAction→Java.Lang.StringJavax.Xml.Ws.IRequestWrapper→Java.Lang.StringJavax.Xml.Ws.IResponse→Java.Lang.StringJavax.Xml.Ws.IResponseWrapper→Java.Lang.StringJavax.Xml.Ws.IWebEndpoint→Java.Lang.StringJavax.Xml.Ws.IWebFault→Java.Lang.StringJavax.Xml.Ws.IWebServiceClient→Java.Lang.StringJavax.Xml.Ws.IWebServiceContext→Java.Lang.ClassJavax.Xml.Ws.IWebServiceContext→Java.Lang.String
- Direction
- Javax.Xml.Ws uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→22 Javax.Xml.Ws uses Javax.Xml.Namespace✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws uses a type in Javax.Xml.Namespace.
- The types involved
Javax.Xml.Ws.Service→Javax.Xml.Namespace.QName
- Direction
- Javax.Xml.Ws uses Javax.Xml.Namespace, so a change to Javax.Xml.Namespace can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Javax.Xml.Namespace.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→23 Javax.Xml.Ws uses Javax.Xml.Transform✕
- Connections
- 5 pairs of types, where a type in Javax.Xml.Ws uses a type in Javax.Xml.Transform.
- The types involved
Javax.Xml.Ws.Endpoint→Javax.Xml.Transform.SourceJavax.Xml.Ws.EndpointReference→Javax.Xml.Transform.ResultJavax.Xml.Ws.EndpointReference→Javax.Xml.Transform.SourceJavax.Xml.Ws.ILogicalMessage→Javax.Xml.Transform.SourceJavax.Xml.Ws.LogicalMessage→Javax.Xml.Transform.Source
- Direction
- Javax.Xml.Ws uses Javax.Xml.Transform, so a change to Javax.Xml.Transform can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Javax.Xml.Transform.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→24 Javax.Xml.Ws uses Org.W3c.Dom✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Ws uses a type in Org.W3c.Dom.
- The types involved
Javax.Xml.Ws.Endpoint→Org.W3c.Dom.ElementJavax.Xml.Ws.IWebServiceContext→Org.W3c.Dom.ElementJavax.Xml.Ws.WebServiceContext→Org.W3c.Dom.Element
- Direction
- Javax.Xml.Ws uses Org.W3c.Dom, so a change to Org.W3c.Dom can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Org.W3c.Dom.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
33→30 Javax.Xml.Ws uses Javax.Xml.Bind✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Ws uses a type in Javax.Xml.Bind.
- The types involved
Javax.Xml.Ws.ILogicalMessage→Javax.Xml.Bind.JAXBContextJavax.Xml.Ws.LogicalMessage→Javax.Xml.Bind.JAXBContextJavax.Xml.Ws.Service→Javax.Xml.Bind.JAXBContext
- Direction
- Javax.Xml.Ws uses Javax.Xml.Bind, so a change to Javax.Xml.Bind can break Javax.Xml.Ws, while a change to Javax.Xml.Ws can't break Javax.Xml.Bind.
- Position
- Below the diagonal: Javax.Xml.Ws uses a module listed above it, which is the healthy direction.
34→4 Javax.Swing uses Java.Util✕
- Connections
- 27 pairs of types, where a type in Javax.Swing uses a type in Java.Util. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractCellEditor→Java.Util.EventObjectJavax.Swing.AbstractListModel→Java.Util.EventListenerJavax.Swing.ButtonGroup→Java.Util.EnumerationJavax.Swing.CellEditor→Java.Util.EventObjectJavax.Swing.DefaultComboBoxModel→Java.Util.VectorJavax.Swing.DefaultListModel→Java.Util.EnumerationJavax.Swing.DefaultRowSorter→Java.Util.ComparatorJavax.Swing.ICellEditor→Java.Util.EventObjectJavax.Swing.JComboBox→Java.Util.VectorJavax.Swing.JComponent→Java.Util.LocaleJavax.Swing.JList→Java.Util.ListJavax.Swing.JList→Java.Util.VectorJavax.Swing.JSlider→Java.Util.DictionaryJavax.Swing.JSlider→Java.Util.HashtableJavax.Swing.JTable→Java.Util.EventObjectJavax.Swing.JTable→Java.Util.VectorJavax.Swing.JTree→Java.Util.EnumerationJavax.Swing.JTree→Java.Util.HashtableJavax.Swing.JTree→Java.Util.VectorJavax.Swing.RowFilter→Java.Util.DateJavax.Swing.RowSorter→Java.Util.ListJavax.Swing.SortingFocusTraversalPolicy→Java.Util.ComparatorJavax.Swing.SpinnerDateModel→Java.Util.DateJavax.Swing.SpinnerListModel→Java.Util.ListJavax.Swing.UIDefaults→Java.Util.Hashtable
- Direction
- Javax.Swing uses Java.Util, so a change to Java.Util can break Javax.Swing, while a change to Javax.Swing can't break Java.Util.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→6 Javax.Swing uses MASES.JNet.Specific✕
- Connections
- 1 pair of types, where a type in Javax.Swing uses a type in MASES.JNet.Specific.
- The types involved
Javax.Swing.Action→MASES.JNet.Specific.JNetEventData
- Direction
- Javax.Swing uses MASES.JNet.Specific, so a change to MASES.JNet.Specific can break Javax.Swing, while a change to Javax.Swing can't break MASES.JNet.Specific.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→9 Javax.Swing uses Java.Util.Concurrent✕
- Connections
- 2 pairs of types, where a type in Javax.Swing uses a type in Java.Util.Concurrent.
- The types involved
Javax.Swing.SwingWorker→Java.Util.Concurrent.RunnableFutureJavax.Swing.SwingWorker→Java.Util.Concurrent.TimeUnit
- Direction
- Javax.Swing uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Javax.Swing, while a change to Javax.Swing can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→13 Javax.Swing uses Java.Net✕
- Connections
- 2 pairs of types, where a type in Javax.Swing uses a type in Java.Net.
- The types involved
Javax.Swing.ImageIcon→Java.Net.URLJavax.Swing.JEditorPane→Java.Net.URL
- Direction
- Javax.Swing uses Java.Net, so a change to Java.Net can break Javax.Swing, while a change to Javax.Swing can't break Java.Net.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→14 Javax.Swing uses Java.Io✕
- Connections
- 30 pairs of types, where a type in Javax.Swing uses a type in Java.Io. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractAction→Java.Io.SerializableJavax.Swing.AbstractCellEditor→Java.Io.SerializableJavax.Swing.AbstractFormatter→Java.Io.SerializableJavax.Swing.AbstractListModel→Java.Io.SerializableJavax.Swing.AbstractSpinnerModel→Java.Io.SerializableJavax.Swing.ActionMap→Java.Io.SerializableJavax.Swing.BoxLayout→Java.Io.SerializableJavax.Swing.ButtonGroup→Java.Io.SerializableJavax.Swing.DebugGraphics→Java.Io.PrintStreamJavax.Swing.DefaultBoundedRangeModel→Java.Io.SerializableJavax.Swing.DefaultButtonModel→Java.Io.SerializableJavax.Swing.DefaultDesktopManager→Java.Io.SerializableJavax.Swing.DefaultListCellRenderer→Java.Io.SerializableJavax.Swing.DefaultListSelectionModel→Java.Io.SerializableJavax.Swing.DefaultSingleSelectionModel→Java.Io.SerializableJavax.Swing.ImageIcon→Java.Io.SerializableJavax.Swing.InputMap→Java.Io.SerializableJavax.Swing.JComponent→Java.Io.SerializableJavax.Swing.JEditorPane→Java.Io.InputStreamJavax.Swing.JFileChooser→Java.Io.FileJavax.Swing.LayoutFocusTraversalPolicy→Java.Io.SerializableJavax.Swing.OverlayLayout→Java.Io.SerializableJavax.Swing.ProgressMonitorInputStream→Java.Io.FilterInputStreamJavax.Swing.ProgressMonitorInputStream→Java.Io.InputStreamJavax.Swing.ScrollPaneLayout→Java.Io.Serializable
- Direction
- Javax.Swing uses Java.Io, so a change to Java.Io can break Javax.Swing, while a change to Javax.Swing can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→16 Javax.Swing uses Java.Lang✕
- Connections
- 110 pairs of types, where a type in Javax.Swing uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractAction→Java.Lang.CloneableJavax.Swing.AbstractAction→Java.Lang.StringJavax.Swing.AbstractButton→Java.Lang.StringJavax.Swing.AbstractFormatter→Java.Lang.StringJavax.Swing.AbstractListModel→Java.Lang.ClassJavax.Swing.AbstractSpinnerModel→Java.Lang.ClassJavax.Swing.AccessibleJComponent→Java.Lang.StringJavax.Swing.Action→Java.Lang.StringJavax.Swing.ActionDirect→Java.Lang.StringJavax.Swing.Alignment→Java.Lang.EnumJavax.Swing.Alignment→Java.Lang.StringJavax.Swing.BorderFactory→Java.Lang.StringJavax.Swing.BoxLayout→Java.Lang.StringJavax.Swing.ButtonModel→Java.Lang.StringJavax.Swing.ComparisonType→Java.Lang.EnumJavax.Swing.ComparisonType→Java.Lang.StringJavax.Swing.ComponentPlacement→Java.Lang.EnumJavax.Swing.ComponentPlacement→Java.Lang.StringJavax.Swing.Constraints→Java.Lang.StringJavax.Swing.DateEditor→Java.Lang.StringJavax.Swing.DefaultBoundedRangeModel→Java.Lang.ClassJavax.Swing.DefaultButtonModel→Java.Lang.ClassJavax.Swing.DefaultButtonModel→Java.Lang.StringJavax.Swing.DefaultEditor→Java.Lang.StringJavax.Swing.DefaultListSelectionModel→Java.Lang.Class
- Direction
- Javax.Swing uses Java.Lang, so a change to Java.Lang can break Javax.Swing, while a change to Javax.Swing can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→17 Javax.Swing uses Java.Awt.ImageNs✕
- Connections
- 2 pairs of types, where a type in Javax.Swing uses a type in Java.Awt.ImageNs.
- The types involved
Javax.Swing.GrayFilter→Java.Awt.ImageNs.RGBImageFilterJavax.Swing.ImageIcon→Java.Awt.ImageNs.ImageObserver
- Direction
- Javax.Swing uses Java.Awt.ImageNs, so a change to Java.Awt.ImageNs can break Javax.Swing, while a change to Javax.Swing can't break Java.Awt.ImageNs.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→19 Javax.Swing uses Java.Text✕
- Connections
- 4 pairs of types, where a type in Javax.Swing uses a type in Java.Text.
- The types involved
Javax.Swing.DateEditor→Java.Text.SimpleDateFormatJavax.Swing.JFormattedTextField→Java.Text.FormatJavax.Swing.JTable→Java.Text.MessageFormatJavax.Swing.NumberEditor→Java.Text.DecimalFormat
- Direction
- Javax.Swing uses Java.Text, so a change to Java.Text can break Javax.Swing, while a change to Javax.Swing can't break Java.Text.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→26 Javax.Swing uses Java.Awt.EventNs✕
- Connections
- 40 pairs of types, where a type in Javax.Swing uses a type in Java.Awt.EventNs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractButton→Java.Awt.EventNs.ActionListenerJavax.Swing.AbstractButton→Java.Awt.EventNs.ItemListenerJavax.Swing.Action→Java.Awt.EventNs.ActionEventJavax.Swing.ActionDirect→Java.Awt.EventNs.ActionEventJavax.Swing.ButtonModel→Java.Awt.EventNs.ActionListenerJavax.Swing.ButtonModel→Java.Awt.EventNs.ItemListenerJavax.Swing.ComboBoxEditor→Java.Awt.EventNs.ActionListenerJavax.Swing.DefaultButtonModel→Java.Awt.EventNs.ActionListenerJavax.Swing.DefaultButtonModel→Java.Awt.EventNs.ItemListenerJavax.Swing.IAction→Java.Awt.EventNs.ActionEventJavax.Swing.IButtonModel→Java.Awt.EventNs.ActionListenerJavax.Swing.IButtonModel→Java.Awt.EventNs.ItemListenerJavax.Swing.IComboBoxEditor→Java.Awt.EventNs.ActionListenerJavax.Swing.IMenuElement→Java.Awt.EventNs.KeyEventJavax.Swing.IMenuElement→Java.Awt.EventNs.MouseEventJavax.Swing.JColorChooser→Java.Awt.EventNs.ActionListenerJavax.Swing.JComboBox→Java.Awt.EventNs.ActionEventJavax.Swing.JComboBox→Java.Awt.EventNs.ActionListenerJavax.Swing.JComboBox→Java.Awt.EventNs.ItemListenerJavax.Swing.JComboBox→Java.Awt.EventNs.KeyEventJavax.Swing.JComponent→Java.Awt.EventNs.ActionListenerJavax.Swing.JComponent→Java.Awt.EventNs.MouseEventJavax.Swing.JFileChooser→Java.Awt.EventNs.ActionListenerJavax.Swing.JMenuBar→Java.Awt.EventNs.KeyEventJavax.Swing.JMenuBar→Java.Awt.EventNs.MouseEvent
- Direction
- Javax.Swing uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing, while a change to Javax.Swing can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→27 Javax.Swing uses Java.Beans✕
- Connections
- 13 pairs of types, where a type in Javax.Swing uses a type in Java.Beans.
- The types involved
Javax.Swing.AbstractAction→Java.Beans.PropertyChangeListenerJavax.Swing.Action→Java.Beans.PropertyChangeListenerJavax.Swing.ActionDirect→Java.Beans.PropertyChangeListenerJavax.Swing.DefaultEditor→Java.Beans.PropertyChangeEventJavax.Swing.DefaultEditor→Java.Beans.PropertyChangeListenerJavax.Swing.IAction→Java.Beans.PropertyChangeListenerJavax.Swing.JComponent→Java.Beans.VetoableChangeListenerJavax.Swing.JLayer→Java.Beans.PropertyChangeEventJavax.Swing.JLayer→Java.Beans.PropertyChangeListenerJavax.Swing.SwingWorker→Java.Beans.PropertyChangeListenerJavax.Swing.SwingWorker→Java.Beans.PropertyChangeSupportJavax.Swing.UIDefaults→Java.Beans.PropertyChangeListenerJavax.Swing.UIManager→Java.Beans.PropertyChangeListener
- Direction
- Javax.Swing uses Java.Beans, so a change to Java.Beans can break Javax.Swing, while a change to Javax.Swing can't break Java.Beans.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→29 Javax.Swing uses Javax.Swing.Tree✕
- Connections
- 8 pairs of types, where a type in Javax.Swing uses a type in Javax.Swing.Tree.
- The types involved
Javax.Swing.DefaultCellEditor→Javax.Swing.Tree.TreeCellEditorJavax.Swing.DynamicUtilTreeNode→Javax.Swing.Tree.DefaultMutableTreeNodeJavax.Swing.JTree→Javax.Swing.Tree.TreeCellEditorJavax.Swing.JTree→Javax.Swing.Tree.TreeCellRendererJavax.Swing.JTree→Javax.Swing.Tree.TreeModelJavax.Swing.JTree→Javax.Swing.Tree.TreeNodeJavax.Swing.JTree→Javax.Swing.Tree.TreePathJavax.Swing.JTree→Javax.Swing.Tree.TreeSelectionModel
- Direction
- Javax.Swing uses Javax.Swing.Tree, so a change to Javax.Swing.Tree can break Javax.Swing, while a change to Javax.Swing can't break Javax.Swing.Tree.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→31 Javax.Swing uses Javax.Swing.Event✕
- Connections
- 59 pairs of types, where a type in Javax.Swing uses a type in Javax.Swing.Event. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractButton→Javax.Swing.Event.ChangeListenerJavax.Swing.AbstractCellEditor→Javax.Swing.Event.CellEditorListenerJavax.Swing.AbstractListModel→Javax.Swing.Event.ListDataListenerJavax.Swing.AbstractSpinnerModel→Javax.Swing.Event.ChangeListenerJavax.Swing.BoundedRangeModel→Javax.Swing.Event.ChangeListenerJavax.Swing.ButtonModel→Javax.Swing.Event.ChangeListenerJavax.Swing.CellEditor→Javax.Swing.Event.CellEditorListenerJavax.Swing.DefaultBoundedRangeModel→Javax.Swing.Event.ChangeListenerJavax.Swing.DefaultButtonModel→Javax.Swing.Event.ChangeListenerJavax.Swing.DefaultEditor→Javax.Swing.Event.ChangeEventJavax.Swing.DefaultEditor→Javax.Swing.Event.ChangeListenerJavax.Swing.DefaultListSelectionModel→Javax.Swing.Event.ListSelectionListenerJavax.Swing.DefaultSingleSelectionModel→Javax.Swing.Event.ChangeListenerJavax.Swing.IBoundedRangeModel→Javax.Swing.Event.ChangeListenerJavax.Swing.IButtonModel→Javax.Swing.Event.ChangeListenerJavax.Swing.ICellEditor→Javax.Swing.Event.CellEditorListenerJavax.Swing.IListModel→Javax.Swing.Event.ListDataListenerJavax.Swing.IListSelectionModel→Javax.Swing.Event.ListSelectionListenerJavax.Swing.ISingleSelectionModel→Javax.Swing.Event.ChangeListenerJavax.Swing.ISpinnerModel→Javax.Swing.Event.ChangeListenerJavax.Swing.JComboBox→Javax.Swing.Event.ListDataEventJavax.Swing.JComboBox→Javax.Swing.Event.ListDataListenerJavax.Swing.JComboBox→Javax.Swing.Event.PopupMenuListenerJavax.Swing.JComponent→Javax.Swing.Event.AncestorListenerJavax.Swing.JEditorPane→Javax.Swing.Event.HyperlinkEvent
- Direction
- Javax.Swing uses Javax.Swing.Event, so a change to Javax.Swing.Event can break Javax.Swing, while a change to Javax.Swing can't break Javax.Swing.Event.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→32 Javax.Swing uses Javax.Swing.Plaf✕
- Connections
- 32 pairs of types, where a type in Javax.Swing uses a type in Javax.Swing.Plaf. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractButton→Javax.Swing.Plaf.ButtonUIJavax.Swing.JColorChooser→Javax.Swing.Plaf.ColorChooserUIJavax.Swing.JComboBox→Javax.Swing.Plaf.ComboBoxUIJavax.Swing.JDesktopIcon→Javax.Swing.Plaf.DesktopIconUIJavax.Swing.JDesktopPane→Javax.Swing.Plaf.DesktopPaneUIJavax.Swing.JFileChooser→Javax.Swing.Plaf.FileChooserUIJavax.Swing.JInternalFrame→Javax.Swing.Plaf.InternalFrameUIJavax.Swing.JLabel→Javax.Swing.Plaf.LabelUIJavax.Swing.JLayer→Javax.Swing.Plaf.LayerUIJavax.Swing.JList→Javax.Swing.Plaf.ListUIJavax.Swing.JMenuBar→Javax.Swing.Plaf.MenuBarUIJavax.Swing.JMenuItem→Javax.Swing.Plaf.MenuItemUIJavax.Swing.JOptionPane→Javax.Swing.Plaf.OptionPaneUIJavax.Swing.JPanel→Javax.Swing.Plaf.PanelUIJavax.Swing.JPopupMenu→Javax.Swing.Plaf.PopupMenuUIJavax.Swing.JProgressBar→Javax.Swing.Plaf.ProgressBarUIJavax.Swing.JRootPane→Javax.Swing.Plaf.RootPaneUIJavax.Swing.JScrollBar→Javax.Swing.Plaf.ScrollBarUIJavax.Swing.JScrollPane→Javax.Swing.Plaf.ScrollPaneUIJavax.Swing.JSeparator→Javax.Swing.Plaf.SeparatorUIJavax.Swing.JSlider→Javax.Swing.Plaf.SliderUIJavax.Swing.JSpinner→Javax.Swing.Plaf.SpinnerUIJavax.Swing.JSplitPane→Javax.Swing.Plaf.SplitPaneUIJavax.Swing.JTabbedPane→Javax.Swing.Plaf.TabbedPaneUIJavax.Swing.JTable→Javax.Swing.Plaf.TableUI
- Direction
- Javax.Swing uses Javax.Swing.Plaf, so a change to Javax.Swing.Plaf can break Javax.Swing, while a change to Javax.Swing can't break Javax.Swing.Plaf.
- Position
- Below the diagonal: Javax.Swing uses a module listed above it, which is the healthy direction.
34→37 Javax.Swing uses Javax.Swing.Text part of a loop✕
- Connections
- 14 pairs of types, where a type in Javax.Swing uses a type in Javax.Swing.Text.
- The types involved
Javax.Swing.JEditorPane→Javax.Swing.Text.EditorKitJavax.Swing.JEditorPane→Javax.Swing.Text.JTextComponentJavax.Swing.JList→Javax.Swing.Text.BiasJavax.Swing.JPasswordField→Javax.Swing.Text.DocumentJavax.Swing.JTextArea→Javax.Swing.Text.DocumentJavax.Swing.JTextArea→Javax.Swing.Text.JTextComponentJavax.Swing.JTextField→Javax.Swing.Text.DocumentJavax.Swing.JTextField→Javax.Swing.Text.JTextComponentJavax.Swing.JTextPane→Javax.Swing.Text.AttributeSetJavax.Swing.JTextPane→Javax.Swing.Text.MutableAttributeSetJavax.Swing.JTextPane→Javax.Swing.Text.StyleJavax.Swing.JTextPane→Javax.Swing.Text.StyledDocumentJavax.Swing.JTree→Javax.Swing.Text.BiasJavax.Swing.LookAndFeel→Javax.Swing.Text.KeyBinding
- Direction
- Javax.Swing uses Javax.Swing.Text, so a change to Javax.Swing.Text can break Javax.Swing, while a change to Javax.Swing can't break Javax.Swing.Text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→38 Javax.Swing uses Javax.Accessibility part of a loop✕
- Connections
- 44 pairs of types, where a type in Javax.Swing uses a type in Javax.Accessibility. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AccessibleJComponent→Javax.Accessibility.AccessibleExtendedComponentJavax.Swing.AccessibleJComponent→Javax.Accessibility.AccessibleKeyBindingJavax.Swing.Box→Javax.Accessibility.AccessibleJavax.Swing.CellRendererPane→Javax.Accessibility.AccessibleJavax.Swing.Filler→Javax.Accessibility.AccessibleJavax.Swing.ImageIcon→Javax.Accessibility.AccessibleJavax.Swing.ImageIcon→Javax.Accessibility.AccessibleContextJavax.Swing.JApplet→Javax.Accessibility.AccessibleJavax.Swing.JButton→Javax.Accessibility.AccessibleJavax.Swing.JColorChooser→Javax.Accessibility.AccessibleJavax.Swing.JComboBox→Javax.Accessibility.AccessibleJavax.Swing.JDesktopIcon→Javax.Accessibility.AccessibleJavax.Swing.JDialog→Javax.Accessibility.AccessibleJavax.Swing.JFileChooser→Javax.Accessibility.AccessibleJavax.Swing.JFrame→Javax.Accessibility.AccessibleJavax.Swing.JInternalFrame→Javax.Accessibility.AccessibleJavax.Swing.JLabel→Javax.Accessibility.AccessibleJavax.Swing.JLayer→Javax.Accessibility.AccessibleJavax.Swing.JLayeredPane→Javax.Accessibility.AccessibleJavax.Swing.JList→Javax.Accessibility.AccessibleJavax.Swing.JMenuBar→Javax.Accessibility.AccessibleJavax.Swing.JMenuItem→Javax.Accessibility.AccessibleJavax.Swing.JOptionPane→Javax.Accessibility.AccessibleJavax.Swing.JPanel→Javax.Accessibility.AccessibleJavax.Swing.JPopupMenu→Javax.Accessibility.Accessible
- Direction
- Javax.Swing uses Javax.Accessibility, so a change to Javax.Accessibility can break Javax.Swing, while a change to Javax.Swing can't break Javax.Accessibility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→39 Javax.Swing uses Java.Awt part of a loop✕
- Connections
- 189 pairs of types, where a type in Javax.Swing uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.AbstractButton→Java.Awt.InsetsJavax.Swing.AbstractButton→Java.Awt.ItemSelectableJavax.Swing.BorderFactory→Java.Awt.BasicStrokeJavax.Swing.BorderFactory→Java.Awt.ColorJavax.Swing.BorderFactory→Java.Awt.FontJavax.Swing.BorderFactory→Java.Awt.PaintJavax.Swing.Box→Java.Awt.ComponentJavax.Swing.Box→Java.Awt.DimensionJavax.Swing.BoxLayout→Java.Awt.ComponentJavax.Swing.BoxLayout→Java.Awt.ContainerJavax.Swing.BoxLayout→Java.Awt.DimensionJavax.Swing.BoxLayout→Java.Awt.LayoutManager2Javax.Swing.ButtonModel→Java.Awt.ItemSelectableJavax.Swing.CellRendererPane→Java.Awt.ComponentJavax.Swing.CellRendererPane→Java.Awt.ContainerJavax.Swing.CellRendererPane→Java.Awt.GraphicsJavax.Swing.CellRendererPane→Java.Awt.RectangleJavax.Swing.ComboBoxEditor→Java.Awt.ComponentJavax.Swing.Constraints→Java.Awt.ComponentJavax.Swing.DebugGraphics→Java.Awt.ColorJavax.Swing.DebugGraphics→Java.Awt.GraphicsJavax.Swing.DefaultCellEditor→Java.Awt.ComponentJavax.Swing.DefaultEditor→Java.Awt.ComponentJavax.Swing.DefaultEditor→Java.Awt.ContainerJavax.Swing.DefaultEditor→Java.Awt.Dimension
- Direction
- Javax.Swing uses Java.Awt, so a change to Java.Awt can break Javax.Swing, while a change to Javax.Swing can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→1 Javax.Xml.Ws.Spi uses Java.Lang.Annotation✕
- Connections
- 2 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Lang.Annotation.
- The types involved
Javax.Xml.Ws.Spi.IWebServiceFeatureAnnotation→Java.Lang.Annotation.IAnnotationJavax.Xml.Ws.Spi.WebServiceFeatureAnnotation→Java.Lang.Annotation.Annotation
- Direction
- Javax.Xml.Ws.Spi uses Java.Lang.Annotation, so a change to Java.Lang.Annotation can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Lang.Annotation.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→4 Javax.Xml.Ws.Spi uses Java.Util✕
- Connections
- 3 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Util.
- The types involved
Javax.Xml.Ws.Spi.Provider→Java.Util.ListJavax.Xml.Ws.Spi.Provider→Java.Util.MapJavax.Xml.Ws.Spi.ServiceDelegate→Java.Util.Iterator
- Direction
- Javax.Xml.Ws.Spi uses Java.Util, so a change to Java.Util can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Util.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→9 Javax.Xml.Ws.Spi uses Java.Util.Concurrent✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Util.Concurrent.
- The types involved
Javax.Xml.Ws.Spi.ServiceDelegate→Java.Util.Concurrent.Executor
- Direction
- Javax.Xml.Ws.Spi uses Java.Util.Concurrent, so a change to Java.Util.Concurrent can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Util.Concurrent.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→13 Javax.Xml.Ws.Spi uses Java.Net✕
- Connections
- 2 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Net.
- The types involved
Javax.Xml.Ws.Spi.Provider→Java.Net.URLJavax.Xml.Ws.Spi.ServiceDelegate→Java.Net.URL
- Direction
- Javax.Xml.Ws.Spi uses Java.Net, so a change to Java.Net can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Net.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→15 Javax.Xml.Ws.Spi uses Java.Lang.Reflect✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Lang.Reflect.
- The types involved
Javax.Xml.Ws.Spi.Invoker→Java.Lang.Reflect.Method
- Direction
- Javax.Xml.Ws.Spi uses Java.Lang.Reflect, so a change to Java.Lang.Reflect can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Lang.Reflect.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→16 Javax.Xml.Ws.Spi uses Java.Lang✕
- Connections
- 8 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Java.Lang.
- The types involved
Javax.Xml.Ws.Spi.IWebServiceFeatureAnnotation→Java.Lang.ClassJavax.Xml.Ws.Spi.IWebServiceFeatureAnnotation→Java.Lang.StringJavax.Xml.Ws.Spi.Provider→Java.Lang.ClassJavax.Xml.Ws.Spi.Provider→Java.Lang.StringJavax.Xml.Ws.Spi.ServiceDelegate→Java.Lang.ClassJavax.Xml.Ws.Spi.ServiceDelegate→Java.Lang.StringJavax.Xml.Ws.Spi.WebServiceFeatureAnnotation→Java.Lang.ClassJavax.Xml.Ws.Spi.WebServiceFeatureAnnotation→Java.Lang.String
- Direction
- Javax.Xml.Ws.Spi uses Java.Lang, so a change to Java.Lang can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Java.Lang.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→22 Javax.Xml.Ws.Spi uses Javax.Xml.Namespace✕
- Connections
- 2 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Javax.Xml.Namespace.
- The types involved
Javax.Xml.Ws.Spi.Provider→Javax.Xml.Namespace.QNameJavax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Namespace.QName
- Direction
- Javax.Xml.Ws.Spi uses Javax.Xml.Namespace, so a change to Javax.Xml.Namespace can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Javax.Xml.Namespace.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→23 Javax.Xml.Ws.Spi uses Javax.Xml.Transform✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws.Spi uses a type in Javax.Xml.Transform.
- The types involved
Javax.Xml.Ws.Spi.Provider→Javax.Xml.Transform.Source
- Direction
- Javax.Xml.Ws.Spi uses Javax.Xml.Transform, so a change to Javax.Xml.Transform can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Javax.Xml.Transform.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→24 Javax.Xml.Ws.Spi uses Org.W3c.Dom✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws.Spi uses a type in Org.W3c.Dom.
- The types involved
Javax.Xml.Ws.Spi.Provider→Org.W3c.Dom.Element
- Direction
- Javax.Xml.Ws.Spi uses Org.W3c.Dom, so a change to Org.W3c.Dom can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Org.W3c.Dom.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→30 Javax.Xml.Ws.Spi uses Javax.Xml.Bind✕
- Connections
- 1 pair of types, where a type in Javax.Xml.Ws.Spi uses a type in Javax.Xml.Bind.
- The types involved
Javax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Bind.JAXBContext
- Direction
- Javax.Xml.Ws.Spi uses Javax.Xml.Bind, so a change to Javax.Xml.Bind can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Javax.Xml.Bind.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
35→33 Javax.Xml.Ws.Spi uses Javax.Xml.Ws✕
- Connections
- 8 pairs of types, where a type in Javax.Xml.Ws.Spi uses a type in Javax.Xml.Ws.
- The types involved
Javax.Xml.Ws.Spi.Invoker→Javax.Xml.Ws.WebServiceContextJavax.Xml.Ws.Spi.Provider→Javax.Xml.Ws.EndpointJavax.Xml.Ws.Spi.Provider→Javax.Xml.Ws.EndpointReferenceJavax.Xml.Ws.Spi.Provider→Javax.Xml.Ws.WebServiceFeatureJavax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Ws.DispatchJavax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Ws.EndpointReferenceJavax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Ws.ModeJavax.Xml.Ws.Spi.ServiceDelegate→Javax.Xml.Ws.WebServiceFeature
- Direction
- Javax.Xml.Ws.Spi uses Javax.Xml.Ws, so a change to Javax.Xml.Ws can break Javax.Xml.Ws.Spi, while a change to Javax.Xml.Ws.Spi can't break Javax.Xml.Ws.
- Position
- Below the diagonal: Javax.Xml.Ws.Spi uses a module listed above it, which is the healthy direction.
36→4 Javax.Swing.Plaf.Basic uses Java.Util✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Util.
- The types involved
Javax.Swing.Plaf.Basic.BasicDirectoryModel→Java.Util.Vector
- Direction
- Javax.Swing.Plaf.Basic uses Java.Util, so a change to Java.Util can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Util.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→14 Javax.Swing.Plaf.Basic uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Io.
- The types involved
Javax.Swing.Plaf.Basic.BasicComboBoxRenderer→Java.Io.SerializableJavax.Swing.Plaf.Basic.BasicDirectoryModel→Java.Io.FileJavax.Swing.Plaf.Basic.BasicIconFactory→Java.Io.SerializableJavax.Swing.Plaf.Basic.BasicLookAndFeel→Java.Io.Serializable
- Direction
- Javax.Swing.Plaf.Basic uses Java.Io, so a change to Java.Io can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→16 Javax.Swing.Plaf.Basic uses Java.Lang✕
- Connections
- 17 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Lang.
- The types involved
Javax.Swing.Plaf.Basic.BasicCheckBoxUI→Java.Lang.StringJavax.Swing.Plaf.Basic.BasicFileChooserUI→Java.Lang.StringJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Java.Lang.StringJavax.Swing.Plaf.Basic.BasicHTML→Java.Lang.StringJavax.Swing.Plaf.Basic.BasicHorizontalLayoutManager→Java.Lang.StringJavax.Swing.Plaf.Basic.BasicScrollBarUI→Java.Lang.StringJavax.Swing.Plaf.Basic.ButtonAreaLayout→Java.Lang.StringJavax.Swing.Plaf.Basic.ComboBoxLayoutManager→Java.Lang.StringJavax.Swing.Plaf.Basic.InternalFrameLayout→Java.Lang.StringJavax.Swing.Plaf.Basic.TabbedPaneLayout→Java.Lang.StringJavax.Swing.Plaf.Basic.TitlePaneLayout→Java.Lang.StringJavax.Swing.Plaf.Basic.TreeCancelEditingAction→Java.Lang.StringJavax.Swing.Plaf.Basic.TreeHomeAction→Java.Lang.StringJavax.Swing.Plaf.Basic.TreeIncrementAction→Java.Lang.StringJavax.Swing.Plaf.Basic.TreePageAction→Java.Lang.StringJavax.Swing.Plaf.Basic.TreeToggleAction→Java.Lang.StringJavax.Swing.Plaf.Basic.TreeTraverseAction→Java.Lang.String
- Direction
- Javax.Swing.Plaf.Basic uses Java.Lang, so a change to Java.Lang can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→26 Javax.Swing.Plaf.Basic uses Java.Awt.EventNs✕
- Connections
- 31 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Awt.EventNs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Plaf.Basic.BasicCheckBoxMenuItemUI→Java.Awt.EventNs.MouseEventJavax.Swing.Plaf.Basic.BasicComboBoxEditor→Java.Awt.EventNs.ActionListenerJavax.Swing.Plaf.Basic.BasicComboBoxEditor→Java.Awt.EventNs.FocusEventJavax.Swing.Plaf.Basic.BasicComboBoxEditor→Java.Awt.EventNs.FocusListenerJavax.Swing.Plaf.Basic.BasicComboPopup→Java.Awt.EventNs.KeyListenerJavax.Swing.Plaf.Basic.BasicComboPopup→Java.Awt.EventNs.MouseListenerJavax.Swing.Plaf.Basic.BasicComboPopup→Java.Awt.EventNs.MouseMotionListenerJavax.Swing.Plaf.Basic.BasicRadioButtonMenuItemUI→Java.Awt.EventNs.MouseEventJavax.Swing.Plaf.Basic.ComboPopup→Java.Awt.EventNs.KeyListenerJavax.Swing.Plaf.Basic.ComboPopup→Java.Awt.EventNs.MouseListenerJavax.Swing.Plaf.Basic.ComboPopup→Java.Awt.EventNs.MouseMotionListenerJavax.Swing.Plaf.Basic.FocusHandler→Java.Awt.EventNs.FocusEventJavax.Swing.Plaf.Basic.FocusHandler→Java.Awt.EventNs.FocusListenerJavax.Swing.Plaf.Basic.IComboPopup→Java.Awt.EventNs.KeyListenerJavax.Swing.Plaf.Basic.IComboPopup→Java.Awt.EventNs.MouseListenerJavax.Swing.Plaf.Basic.IComboPopup→Java.Awt.EventNs.MouseMotionListenerJavax.Swing.Plaf.Basic.ItemHandler→Java.Awt.EventNs.ItemEventJavax.Swing.Plaf.Basic.ItemHandler→Java.Awt.EventNs.ItemListenerJavax.Swing.Plaf.Basic.KeyHandler→Java.Awt.EventNs.KeyEventJavax.Swing.Plaf.Basic.KeyHandler→Java.Awt.EventNs.KeyListenerJavax.Swing.Plaf.Basic.KeyboardDownRightHandler→Java.Awt.EventNs.ActionEventJavax.Swing.Plaf.Basic.KeyboardDownRightHandler→Java.Awt.EventNs.ActionListenerJavax.Swing.Plaf.Basic.KeyboardEndHandler→Java.Awt.EventNs.ActionEventJavax.Swing.Plaf.Basic.KeyboardEndHandler→Java.Awt.EventNs.ActionListenerJavax.Swing.Plaf.Basic.KeyboardHomeHandler→Java.Awt.EventNs.ActionEvent
- Direction
- Javax.Swing.Plaf.Basic uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→27 Javax.Swing.Plaf.Basic uses Java.Beans✕
- Connections
- 15 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Beans.
- The types involved
Javax.Swing.Plaf.Basic.BasicDirectoryModel→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.BasicDirectoryModel→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.BasicFileChooserUI→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.BasicLabelUI→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.BasicLabelUI→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.BasicRootPaneUI→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.BasicRootPaneUI→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.BasicSplitPaneDivider→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.BasicSplitPaneDivider→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.PropertyChangeHandler→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.PropertyChangeHandler→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.PropertyHandler→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.PropertyHandler→Java.Beans.PropertyChangeListenerJavax.Swing.Plaf.Basic.SelectionModelPropertyChangeHandler→Java.Beans.PropertyChangeEventJavax.Swing.Plaf.Basic.SelectionModelPropertyChangeHandler→Java.Beans.PropertyChangeListener
- Direction
- Javax.Swing.Plaf.Basic uses Java.Beans, so a change to Java.Beans can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Beans.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→29 Javax.Swing.Plaf.Basic uses Javax.Swing.Tree✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Plaf.Basic uses a type in Javax.Swing.Tree.
- The types involved
Javax.Swing.Plaf.Basic.NodeDimensionsHandler→Javax.Swing.Tree.NodeDimensions
- Direction
- Javax.Swing.Plaf.Basic uses Javax.Swing.Tree, so a change to Javax.Swing.Tree can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Javax.Swing.Tree.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→31 Javax.Swing.Plaf.Basic uses Javax.Swing.Event✕
- Connections
- 21 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Javax.Swing.Event.
- The types involved
Javax.Swing.Plaf.Basic.BasicDirectoryModel→Javax.Swing.Event.ListDataEventJavax.Swing.Plaf.Basic.BasicFileChooserUI→Javax.Swing.Event.ListSelectionListenerJavax.Swing.Plaf.Basic.CellEditorHandler→Javax.Swing.Event.CellEditorListenerJavax.Swing.Plaf.Basic.CellEditorHandler→Javax.Swing.Event.ChangeEventJavax.Swing.Plaf.Basic.ChangeHandler→Javax.Swing.Event.ChangeEventJavax.Swing.Plaf.Basic.ChangeHandler→Javax.Swing.Event.ChangeListenerJavax.Swing.Plaf.Basic.ListDataHandler→Javax.Swing.Event.ListDataEventJavax.Swing.Plaf.Basic.ListDataHandler→Javax.Swing.Event.ListDataListenerJavax.Swing.Plaf.Basic.ListSelectionHandler→Javax.Swing.Event.ListSelectionEventJavax.Swing.Plaf.Basic.ListSelectionHandler→Javax.Swing.Event.ListSelectionListenerJavax.Swing.Plaf.Basic.MouseInputHandler→Javax.Swing.Event.MouseInputListenerJavax.Swing.Plaf.Basic.TabSelectionHandler→Javax.Swing.Event.ChangeEventJavax.Swing.Plaf.Basic.TabSelectionHandler→Javax.Swing.Event.ChangeListenerJavax.Swing.Plaf.Basic.TreeExpansionHandler→Javax.Swing.Event.TreeExpansionEventJavax.Swing.Plaf.Basic.TreeExpansionHandler→Javax.Swing.Event.TreeExpansionListenerJavax.Swing.Plaf.Basic.TreeModelHandler→Javax.Swing.Event.TreeModelEventJavax.Swing.Plaf.Basic.TreeModelHandler→Javax.Swing.Event.TreeModelListenerJavax.Swing.Plaf.Basic.TreeSelectionHandler→Javax.Swing.Event.TreeSelectionEventJavax.Swing.Plaf.Basic.TreeSelectionHandler→Javax.Swing.Event.TreeSelectionListenerJavax.Swing.Plaf.Basic.ViewportChangeHandler→Javax.Swing.Event.ChangeEventJavax.Swing.Plaf.Basic.ViewportChangeHandler→Javax.Swing.Event.ChangeListener
- Direction
- Javax.Swing.Plaf.Basic uses Javax.Swing.Event, so a change to Javax.Swing.Event can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Javax.Swing.Event.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→32 Javax.Swing.Plaf.Basic uses Javax.Swing.Plaf✕
- Connections
- 39 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Javax.Swing.Plaf. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Plaf.Basic.BasicButtonUI→Javax.Swing.Plaf.ButtonUIJavax.Swing.Plaf.Basic.BasicCaret→Javax.Swing.Plaf.UIResourceJavax.Swing.Plaf.Basic.BasicColorChooserUI→Javax.Swing.Plaf.ColorChooserUIJavax.Swing.Plaf.Basic.BasicComboBoxUI→Javax.Swing.Plaf.ComboBoxUIJavax.Swing.Plaf.Basic.BasicDesktopIconUI→Javax.Swing.Plaf.DesktopIconUIJavax.Swing.Plaf.Basic.BasicDesktopPaneUI→Javax.Swing.Plaf.DesktopPaneUIJavax.Swing.Plaf.Basic.BasicFileChooserUI→Javax.Swing.Plaf.FileChooserUIJavax.Swing.Plaf.Basic.BasicHighlighter→Javax.Swing.Plaf.UIResourceJavax.Swing.Plaf.Basic.BasicInternalFrameUI→Javax.Swing.Plaf.InternalFrameUIJavax.Swing.Plaf.Basic.BasicLabelUI→Javax.Swing.Plaf.LabelUIJavax.Swing.Plaf.Basic.BasicListUI→Javax.Swing.Plaf.ListUIJavax.Swing.Plaf.Basic.BasicMenuBarUI→Javax.Swing.Plaf.MenuBarUIJavax.Swing.Plaf.Basic.BasicMenuItemUI→Javax.Swing.Plaf.MenuItemUIJavax.Swing.Plaf.Basic.BasicOptionPaneUI→Javax.Swing.Plaf.OptionPaneUIJavax.Swing.Plaf.Basic.BasicPanelUI→Javax.Swing.Plaf.PanelUIJavax.Swing.Plaf.Basic.BasicPopupMenuUI→Javax.Swing.Plaf.PopupMenuUIJavax.Swing.Plaf.Basic.BasicProgressBarUI→Javax.Swing.Plaf.ProgressBarUIJavax.Swing.Plaf.Basic.BasicRootPaneUI→Javax.Swing.Plaf.RootPaneUIJavax.Swing.Plaf.Basic.BasicScrollBarUI→Javax.Swing.Plaf.ScrollBarUIJavax.Swing.Plaf.Basic.BasicScrollPaneUI→Javax.Swing.Plaf.ScrollPaneUIJavax.Swing.Plaf.Basic.BasicSeparatorUI→Javax.Swing.Plaf.SeparatorUIJavax.Swing.Plaf.Basic.BasicSliderUI→Javax.Swing.Plaf.SliderUIJavax.Swing.Plaf.Basic.BasicSpinnerUI→Javax.Swing.Plaf.SpinnerUIJavax.Swing.Plaf.Basic.BasicSplitPaneUI→Javax.Swing.Plaf.SplitPaneUIJavax.Swing.Plaf.Basic.BasicTabbedPaneUI→Javax.Swing.Plaf.TabbedPaneUI
- Direction
- Javax.Swing.Plaf.Basic uses Javax.Swing.Plaf, so a change to Javax.Swing.Plaf can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Javax.Swing.Plaf.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→34 Javax.Swing.Plaf.Basic uses Javax.Swing✕
- Connections
- 60 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Javax.Swing. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Plaf.Basic.ActionScroller→Javax.Swing.AbstractActionJavax.Swing.Plaf.Basic.ActionScroller→Javax.Swing.JSliderJavax.Swing.Plaf.Basic.BasicArrowButton→Javax.Swing.JButtonJavax.Swing.Plaf.Basic.BasicArrowButton→Javax.Swing.SwingConstantsJavax.Swing.Plaf.Basic.BasicButtonUI→Javax.Swing.AbstractButtonJavax.Swing.Plaf.Basic.BasicCheckBoxMenuItemUI→Javax.Swing.JMenuItemJavax.Swing.Plaf.Basic.BasicCheckBoxMenuItemUI→Javax.Swing.MenuElementJavax.Swing.Plaf.Basic.BasicCheckBoxMenuItemUI→Javax.Swing.MenuSelectionManagerJavax.Swing.Plaf.Basic.BasicComboBoxEditor→Javax.Swing.ComboBoxEditorJavax.Swing.Plaf.Basic.BasicComboBoxRenderer→Javax.Swing.JLabelJavax.Swing.Plaf.Basic.BasicComboBoxRenderer→Javax.Swing.JListJavax.Swing.Plaf.Basic.BasicComboBoxRenderer→Javax.Swing.ListCellRendererJavax.Swing.Plaf.Basic.BasicComboPopup→Javax.Swing.JComboBoxJavax.Swing.Plaf.Basic.BasicComboPopup→Javax.Swing.JListJavax.Swing.Plaf.Basic.BasicComboPopup→Javax.Swing.JPopupMenuJavax.Swing.Plaf.Basic.BasicDesktopIconUI→Javax.Swing.JComponentJavax.Swing.Plaf.Basic.BasicDirectoryModel→Javax.Swing.AbstractListModelJavax.Swing.Plaf.Basic.BasicDirectoryModel→Javax.Swing.JFileChooserJavax.Swing.Plaf.Basic.BasicFileChooserUI→Javax.Swing.ActionJavax.Swing.Plaf.Basic.BasicFileChooserUI→Javax.Swing.JFileChooserJavax.Swing.Plaf.Basic.BasicFileChooserUI→Javax.Swing.JPanelJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Javax.Swing.AbstractButtonJavax.Swing.Plaf.Basic.BasicHTML→Javax.Swing.JComponentJavax.Swing.Plaf.Basic.BasicIconFactory→Javax.Swing.IconJavax.Swing.Plaf.Basic.BasicInternalFrameTitlePane→Javax.Swing.JComponent
- Direction
- Javax.Swing.Plaf.Basic uses Javax.Swing, so a change to Javax.Swing can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Javax.Swing.
- Position
- Below the diagonal: Javax.Swing.Plaf.Basic uses a module listed above it, which is the healthy direction.
36→37 Javax.Swing.Plaf.Basic uses Javax.Swing.Text part of a loop✕
- Connections
- 6 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Javax.Swing.Text.
- The types involved
Javax.Swing.Plaf.Basic.BasicCaret→Javax.Swing.Text.DefaultCaretJavax.Swing.Plaf.Basic.BasicHTML→Javax.Swing.Text.ViewJavax.Swing.Plaf.Basic.BasicHighlighter→Javax.Swing.Text.DefaultHighlighterJavax.Swing.Plaf.Basic.BasicTextUI→Javax.Swing.Text.ElementJavax.Swing.Plaf.Basic.BasicTextUI→Javax.Swing.Text.ViewJavax.Swing.Plaf.Basic.BasicTextUI→Javax.Swing.Text.ViewFactory
- Direction
- Javax.Swing.Plaf.Basic uses Javax.Swing.Text, so a change to Javax.Swing.Text can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Javax.Swing.Text.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→39 Javax.Swing.Plaf.Basic uses Java.Awt part of a loop✕
- Connections
- 62 pairs of types, where a type in Javax.Swing.Plaf.Basic uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Plaf.Basic.BasicArrowButton→Java.Awt.ColorJavax.Swing.Plaf.Basic.BasicArrowButton→Java.Awt.GraphicsJavax.Swing.Plaf.Basic.BasicComboBoxEditor→Java.Awt.ComponentJavax.Swing.Plaf.Basic.BasicComboBoxRenderer→Java.Awt.ComponentJavax.Swing.Plaf.Basic.BasicComboBoxUI→Java.Awt.GraphicsJavax.Swing.Plaf.Basic.BasicComboBoxUI→Java.Awt.RectangleJavax.Swing.Plaf.Basic.BasicDesktopIconUI→Java.Awt.InsetsJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Java.Awt.ColorJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Java.Awt.DimensionJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Java.Awt.GraphicsJavax.Swing.Plaf.Basic.BasicGraphicsUtils→Java.Awt.InsetsJavax.Swing.Plaf.Basic.BasicHorizontalLayoutManager→Java.Awt.ComponentJavax.Swing.Plaf.Basic.BasicHorizontalLayoutManager→Java.Awt.ContainerJavax.Swing.Plaf.Basic.BasicHorizontalLayoutManager→Java.Awt.DimensionJavax.Swing.Plaf.Basic.BasicHorizontalLayoutManager→Java.Awt.LayoutManager2Javax.Swing.Plaf.Basic.BasicInternalFrameTitlePane→Java.Awt.GraphicsJavax.Swing.Plaf.Basic.BasicOptionPaneUI→Java.Awt.DimensionJavax.Swing.Plaf.Basic.BasicScrollBarUI→Java.Awt.ComponentJavax.Swing.Plaf.Basic.BasicScrollBarUI→Java.Awt.ContainerJavax.Swing.Plaf.Basic.BasicScrollBarUI→Java.Awt.DimensionJavax.Swing.Plaf.Basic.BasicScrollBarUI→Java.Awt.LayoutManagerJavax.Swing.Plaf.Basic.BasicSliderUI→Java.Awt.DimensionJavax.Swing.Plaf.Basic.BasicSliderUI→Java.Awt.GraphicsJavax.Swing.Plaf.Basic.BasicSplitPaneDivider→Java.Awt.ContainerJavax.Swing.Plaf.Basic.BasicSplitPaneUI→Java.Awt.Component
- Direction
- Javax.Swing.Plaf.Basic uses Java.Awt, so a change to Java.Awt can break Javax.Swing.Plaf.Basic, while a change to Javax.Swing.Plaf.Basic can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→4 Javax.Swing.Text uses Java.Util✕
- Connections
- 12 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Util.
- The types involved
Javax.Swing.Text.AbstractDocument→Java.Util.DictionaryJavax.Swing.Text.AbstractElement→Java.Util.EnumerationJavax.Swing.Text.AttributeContext→Java.Util.EnumerationJavax.Swing.Text.AttributeSet→Java.Util.EnumerationJavax.Swing.Text.DefaultStyledDocument→Java.Util.EnumerationJavax.Swing.Text.IAttributeSet→Java.Util.EnumerationJavax.Swing.Text.IMutableAttributeSet→Java.Util.EnumerationJavax.Swing.Text.MutableAttributeSet→Java.Util.EnumerationJavax.Swing.Text.NamedStyle→Java.Util.EnumerationJavax.Swing.Text.SimpleAttributeSet→Java.Util.EnumerationJavax.Swing.Text.SmallAttributeSet→Java.Util.EnumerationJavax.Swing.Text.StyleContext→Java.Util.Enumeration
- Direction
- Javax.Swing.Text uses Java.Util, so a change to Java.Util can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Util.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→14 Javax.Swing.Text uses Java.Io✕
- Connections
- 23 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Io.
- The types involved
Javax.Swing.Text.AbstractDocument→Java.Io.PrintStreamJavax.Swing.Text.AbstractDocument→Java.Io.SerializableJavax.Swing.Text.AbstractElement→Java.Io.PrintStreamJavax.Swing.Text.AbstractElement→Java.Io.SerializableJavax.Swing.Text.ChangedCharSetException→Java.Io.IOExceptionJavax.Swing.Text.DefaultFormatterFactory→Java.Io.SerializableJavax.Swing.Text.EditorKit→Java.Io.InputStreamJavax.Swing.Text.EditorKit→Java.Io.OutputStreamJavax.Swing.Text.EditorKit→Java.Io.ReaderJavax.Swing.Text.EditorKit→Java.Io.SerializableJavax.Swing.Text.EditorKit→Java.Io.WriterJavax.Swing.Text.ElementBuffer→Java.Io.SerializableJavax.Swing.Text.GapContent→Java.Io.SerializableJavax.Swing.Text.JTextComponent→Java.Io.ReaderJavax.Swing.Text.JTextComponent→Java.Io.WriterJavax.Swing.Text.NamedStyle→Java.Io.SerializableJavax.Swing.Text.SimpleAttributeSet→Java.Io.SerializableJavax.Swing.Text.StringContent→Java.Io.SerializableJavax.Swing.Text.StyleContext→Java.Io.ObjectInputStreamJavax.Swing.Text.StyleContext→Java.Io.ObjectOutputStreamJavax.Swing.Text.StyleContext→Java.Io.SerializableJavax.Swing.Text.TabSet→Java.Io.SerializableJavax.Swing.Text.TabStop→Java.Io.Serializable
- Direction
- Javax.Swing.Text uses Java.Io, so a change to Java.Io can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Io.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→16 Javax.Swing.Text uses Java.Lang✕
- Connections
- 54 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Text.AbstractDocument→Java.Lang.ClassJavax.Swing.Text.AbstractDocument→Java.Lang.RunnableJavax.Swing.Text.AbstractDocument→Java.Lang.StringJavax.Swing.Text.AbstractElement→Java.Lang.StringJavax.Swing.Text.AbstractWriter→Java.Lang.StringJavax.Swing.Text.AccessibleJTextComponent→Java.Lang.StringJavax.Swing.Text.AlignmentAction→Java.Lang.StringJavax.Swing.Text.BadLocationException→Java.Lang.ExceptionJavax.Swing.Text.ChildState→Java.Lang.RunnableJavax.Swing.Text.Content→Java.Lang.StringJavax.Swing.Text.DefaultCaret→Java.Lang.ClassJavax.Swing.Text.DefaultEditorKit→Java.Lang.StringJavax.Swing.Text.DefaultFormatter→Java.Lang.ClassJavax.Swing.Text.DefaultFormatter→Java.Lang.CloneableJavax.Swing.Text.DefaultStyledDocument→Java.Lang.StringJavax.Swing.Text.Document→Java.Lang.RunnableJavax.Swing.Text.Document→Java.Lang.StringJavax.Swing.Text.DocumentFilter→Java.Lang.StringJavax.Swing.Text.EditorKit→Java.Lang.CloneableJavax.Swing.Text.EditorKit→Java.Lang.StringJavax.Swing.Text.Element→Java.Lang.StringJavax.Swing.Text.ElementIterator→Java.Lang.CloneableJavax.Swing.Text.FilterBypass→Java.Lang.StringJavax.Swing.Text.FontFamilyAction→Java.Lang.StringJavax.Swing.Text.FontSizeAction→Java.Lang.String
- Direction
- Javax.Swing.Text uses Java.Lang, so a change to Java.Lang can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Lang.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→19 Javax.Swing.Text uses Java.Text✕
- Connections
- 6 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Text.
- The types involved
Javax.Swing.Text.DateFormatter→Java.Text.DateFormatJavax.Swing.Text.InternationalFormatter→Java.Text.FieldJavax.Swing.Text.InternationalFormatter→Java.Text.FormatJavax.Swing.Text.JTextComponent→Java.Text.MessageFormatJavax.Swing.Text.NumberFormatter→Java.Text.NumberFormatJavax.Swing.Text.Segment→Java.Text.CharacterIterator
- Direction
- Javax.Swing.Text uses Java.Text, so a change to Java.Text can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Text.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→26 Javax.Swing.Text uses Java.Awt.EventNs✕
- Connections
- 5 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Awt.EventNs.
- The types involved
Javax.Swing.Text.DefaultCaret→Java.Awt.EventNs.FocusEventJavax.Swing.Text.DefaultCaret→Java.Awt.EventNs.FocusListenerJavax.Swing.Text.DefaultCaret→Java.Awt.EventNs.MouseEventJavax.Swing.Text.DefaultCaret→Java.Awt.EventNs.MouseListenerJavax.Swing.Text.DefaultCaret→Java.Awt.EventNs.MouseMotionListener
- Direction
- Javax.Swing.Text uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→29 Javax.Swing.Text uses Javax.Swing.Tree✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Text uses a type in Javax.Swing.Tree.
- The types involved
Javax.Swing.Text.AbstractElement→Javax.Swing.Tree.TreeNode
- Direction
- Javax.Swing.Text uses Javax.Swing.Tree, so a change to Javax.Swing.Tree can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Swing.Tree.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→31 Javax.Swing.Text uses Javax.Swing.Event✕
- Connections
- 23 pairs of types, where a type in Javax.Swing.Text uses a type in Javax.Swing.Event.
- The types involved
Javax.Swing.Text.AbstractDocument→Javax.Swing.Event.DocumentListenerJavax.Swing.Text.AbstractDocument→Javax.Swing.Event.UndoableEditListenerJavax.Swing.Text.AccessibleJTextComponent→Javax.Swing.Event.CaretEventJavax.Swing.Text.AccessibleJTextComponent→Javax.Swing.Event.CaretListenerJavax.Swing.Text.AccessibleJTextComponent→Javax.Swing.Event.DocumentEventJavax.Swing.Text.AccessibleJTextComponent→Javax.Swing.Event.DocumentListenerJavax.Swing.Text.Caret→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.DefaultCaret→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.DefaultDocumentEvent→Javax.Swing.Event.DocumentEventJavax.Swing.Text.DefaultDocumentEvent→Javax.Swing.Event.ElementChangeJavax.Swing.Text.DefaultDocumentEvent→Javax.Swing.Event.EventTypeJavax.Swing.Text.Document→Javax.Swing.Event.DocumentListenerJavax.Swing.Text.Document→Javax.Swing.Event.UndoableEditListenerJavax.Swing.Text.FlowStrategy→Javax.Swing.Event.DocumentEventJavax.Swing.Text.ICaret→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.IDocument→Javax.Swing.Event.DocumentListenerJavax.Swing.Text.IDocument→Javax.Swing.Event.UndoableEditListenerJavax.Swing.Text.IStyle→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.JTextComponent→Javax.Swing.Event.CaretListenerJavax.Swing.Text.NamedStyle→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.Style→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.StyleContext→Javax.Swing.Event.ChangeListenerJavax.Swing.Text.View→Javax.Swing.Event.DocumentEvent
- Direction
- Javax.Swing.Text uses Javax.Swing.Event, so a change to Javax.Swing.Event can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Swing.Event.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→32 Javax.Swing.Text uses Javax.Swing.Plaf✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Text uses a type in Javax.Swing.Plaf.
- The types involved
Javax.Swing.Text.JTextComponent→Javax.Swing.Plaf.TextUI
- Direction
- Javax.Swing.Text uses Javax.Swing.Plaf, so a change to Javax.Swing.Plaf can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Swing.Plaf.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→34 Javax.Swing.Text uses Javax.Swing✕
- Connections
- 20 pairs of types, where a type in Javax.Swing.Text uses a type in Javax.Swing.
- The types involved
Javax.Swing.Text.AccessibleJTextComponent→Javax.Swing.AccessibleJComponentJavax.Swing.Text.DefaultFormatter→Javax.Swing.AbstractFormatterJavax.Swing.Text.DefaultFormatterFactory→Javax.Swing.AbstractFormatterJavax.Swing.Text.DefaultFormatterFactory→Javax.Swing.AbstractFormatterFactoryJavax.Swing.Text.DropLocation→Javax.Swing.DropLocationJavax.Swing.Text.EditorKit→Javax.Swing.ActionJavax.Swing.Text.EditorKit→Javax.Swing.JEditorPaneJavax.Swing.Text.IKeymap→Javax.Swing.ActionJavax.Swing.Text.IKeymap→Javax.Swing.KeyStrokeJavax.Swing.Text.JTextComponent→Javax.Swing.ActionJavax.Swing.Text.JTextComponent→Javax.Swing.DropModeJavax.Swing.Text.JTextComponent→Javax.Swing.JComponentJavax.Swing.Text.JTextComponent→Javax.Swing.ScrollableJavax.Swing.Text.KeyBinding→Javax.Swing.KeyStrokeJavax.Swing.Text.Keymap→Javax.Swing.ActionJavax.Swing.Text.Keymap→Javax.Swing.KeyStrokeJavax.Swing.Text.StyleConstants→Javax.Swing.IconJavax.Swing.Text.TextAction→Javax.Swing.AbstractActionJavax.Swing.Text.TextAction→Javax.Swing.ActionJavax.Swing.Text.View→Javax.Swing.SwingConstants
- Direction
- Javax.Swing.Text uses Javax.Swing, so a change to Javax.Swing can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Swing.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→36 Javax.Swing.Text uses Javax.Swing.Plaf.Basic✕
- Connections
- 1 pair of types, where a type in Javax.Swing.Text uses a type in Javax.Swing.Plaf.Basic.
- The types involved
Javax.Swing.Text.DefaultTextUI→Javax.Swing.Plaf.Basic.BasicTextUI
- Direction
- Javax.Swing.Text uses Javax.Swing.Plaf.Basic, so a change to Javax.Swing.Plaf.Basic can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Swing.Plaf.Basic.
- Position
- Below the diagonal: Javax.Swing.Text uses a module listed above it, which is the healthy direction.
37→38 Javax.Swing.Text uses Javax.Accessibility part of a loop✕
- Connections
- 6 pairs of types, where a type in Javax.Swing.Text uses a type in Javax.Accessibility.
- The types involved
Javax.Swing.Text.AccessibleJTextComponent→Javax.Accessibility.AccessibleActionJavax.Swing.Text.AccessibleJTextComponent→Javax.Accessibility.AccessibleEditableTextJavax.Swing.Text.AccessibleJTextComponent→Javax.Accessibility.AccessibleExtendedTextJavax.Swing.Text.AccessibleJTextComponent→Javax.Accessibility.AccessibleTextJavax.Swing.Text.AccessibleJTextComponent→Javax.Accessibility.AccessibleTextSequenceJavax.Swing.Text.JTextComponent→Javax.Accessibility.Accessible
- Direction
- Javax.Swing.Text uses Javax.Accessibility, so a change to Javax.Accessibility can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Javax.Accessibility.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
37→39 Javax.Swing.Text uses Java.Awt part of a loop✕
- Connections
- 49 pairs of types, where a type in Javax.Swing.Text uses a type in Java.Awt. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Javax.Swing.Text.AccessibleJTextComponent→Java.Awt.PointJavax.Swing.Text.AccessibleJTextComponent→Java.Awt.RectangleJavax.Swing.Text.Caret→Java.Awt.GraphicsJavax.Swing.Text.Caret→Java.Awt.PointJavax.Swing.Text.ChildLocator→Java.Awt.GraphicsJavax.Swing.Text.ChildLocator→Java.Awt.ShapeJavax.Swing.Text.ComponentView→Java.Awt.ComponentJavax.Swing.Text.DefaultCaret→Java.Awt.GraphicsJavax.Swing.Text.DefaultCaret→Java.Awt.PointJavax.Swing.Text.DefaultCaret→Java.Awt.RectangleJavax.Swing.Text.DefaultHighlightPainter→Java.Awt.ColorJavax.Swing.Text.DefaultStyledDocument→Java.Awt.ColorJavax.Swing.Text.DefaultStyledDocument→Java.Awt.FontJavax.Swing.Text.FlowStrategy→Java.Awt.RectangleJavax.Swing.Text.ForegroundAction→Java.Awt.ColorJavax.Swing.Text.GlyphPainter→Java.Awt.GraphicsJavax.Swing.Text.GlyphPainter→Java.Awt.ShapeJavax.Swing.Text.GlyphView→Java.Awt.ColorJavax.Swing.Text.GlyphView→Java.Awt.FontJavax.Swing.Text.HighlightPainter→Java.Awt.GraphicsJavax.Swing.Text.HighlightPainter→Java.Awt.ShapeJavax.Swing.Text.Highlighter→Java.Awt.GraphicsJavax.Swing.Text.ICaret→Java.Awt.GraphicsJavax.Swing.Text.ICaret→Java.Awt.PointJavax.Swing.Text.IHighlighter→Java.Awt.Graphics
- Direction
- Javax.Swing.Text uses Java.Awt, so a change to Java.Awt can break Javax.Swing.Text, while a change to Javax.Swing.Text can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
38→4 Javax.Accessibility uses Java.Util✕
- Connections
- 3 pairs of types, where a type in Javax.Accessibility uses a type in Java.Util.
- The types involved
Javax.Accessibility.AccessibleBundle→Java.Util.LocaleJavax.Accessibility.AccessibleContext→Java.Util.LocaleJavax.Accessibility.AccessibleResourceBundle→Java.Util.ListResourceBundle
- Direction
- Javax.Accessibility uses Java.Util, so a change to Java.Util can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Util.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→14 Javax.Accessibility uses Java.Io✕
- Connections
- 2 pairs of types, where a type in Javax.Accessibility uses a type in Java.Io.
- The types involved
Javax.Accessibility.AccessibleStreamable→Java.Io.InputStreamJavax.Accessibility.IAccessibleStreamable→Java.Io.InputStream
- Direction
- Javax.Accessibility uses Java.Io, so a change to Java.Io can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Io.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→16 Javax.Accessibility uses Java.Lang✕
- Connections
- 20 pairs of types, where a type in Javax.Accessibility uses a type in Java.Lang.
- The types involved
Javax.Accessibility.AccessibleAction→Java.Lang.StringJavax.Accessibility.AccessibleBundle→Java.Lang.StringJavax.Accessibility.AccessibleContext→Java.Lang.StringJavax.Accessibility.AccessibleEditableText→Java.Lang.StringJavax.Accessibility.AccessibleExtendedComponent→Java.Lang.StringJavax.Accessibility.AccessibleExtendedText→Java.Lang.StringJavax.Accessibility.AccessibleHyperlink→Java.Lang.StringJavax.Accessibility.AccessibleIcon→Java.Lang.StringJavax.Accessibility.AccessibleRelation→Java.Lang.StringJavax.Accessibility.AccessibleRelationSet→Java.Lang.StringJavax.Accessibility.AccessibleText→Java.Lang.StringJavax.Accessibility.AccessibleTextSequence→Java.Lang.StringJavax.Accessibility.AccessibleValue→Java.Lang.NumberJavax.Accessibility.IAccessibleAction→Java.Lang.StringJavax.Accessibility.IAccessibleEditableText→Java.Lang.StringJavax.Accessibility.IAccessibleExtendedComponent→Java.Lang.StringJavax.Accessibility.IAccessibleExtendedText→Java.Lang.StringJavax.Accessibility.IAccessibleIcon→Java.Lang.StringJavax.Accessibility.IAccessibleText→Java.Lang.StringJavax.Accessibility.IAccessibleValue→Java.Lang.Number
- Direction
- Javax.Accessibility uses Java.Lang, so a change to Java.Lang can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Lang.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→26 Javax.Accessibility uses Java.Awt.EventNs✕
- Connections
- 2 pairs of types, where a type in Javax.Accessibility uses a type in Java.Awt.EventNs.
- The types involved
Javax.Accessibility.AccessibleComponent→Java.Awt.EventNs.FocusListenerJavax.Accessibility.IAccessibleComponent→Java.Awt.EventNs.FocusListener
- Direction
- Javax.Accessibility uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→27 Javax.Accessibility uses Java.Beans✕
- Connections
- 1 pair of types, where a type in Javax.Accessibility uses a type in Java.Beans.
- The types involved
Javax.Accessibility.AccessibleContext→Java.Beans.PropertyChangeListener
- Direction
- Javax.Accessibility uses Java.Beans, so a change to Java.Beans can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Beans.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→37 Javax.Accessibility uses Javax.Swing.Text✕
- Connections
- 5 pairs of types, where a type in Javax.Accessibility uses a type in Javax.Swing.Text.
- The types involved
Javax.Accessibility.AccessibleAttributeSequence→Javax.Swing.Text.AttributeSetJavax.Accessibility.AccessibleEditableText→Javax.Swing.Text.AttributeSetJavax.Accessibility.AccessibleText→Javax.Swing.Text.AttributeSetJavax.Accessibility.IAccessibleEditableText→Javax.Swing.Text.AttributeSetJavax.Accessibility.IAccessibleText→Javax.Swing.Text.AttributeSet
- Direction
- Javax.Accessibility uses Javax.Swing.Text, so a change to Javax.Swing.Text can break Javax.Accessibility, while a change to Javax.Accessibility can't break Javax.Swing.Text.
- Position
- Below the diagonal: Javax.Accessibility uses a module listed above it, which is the healthy direction.
38→39 Javax.Accessibility uses Java.Awt part of a loop✕
- Connections
- 20 pairs of types, where a type in Javax.Accessibility uses a type in Java.Awt.
- The types involved
Javax.Accessibility.AccessibleComponent→Java.Awt.ColorJavax.Accessibility.AccessibleComponent→Java.Awt.CursorJavax.Accessibility.AccessibleComponent→Java.Awt.DimensionJavax.Accessibility.AccessibleComponent→Java.Awt.FontJavax.Accessibility.AccessibleComponent→Java.Awt.FontMetricsJavax.Accessibility.AccessibleComponent→Java.Awt.PointJavax.Accessibility.AccessibleComponent→Java.Awt.RectangleJavax.Accessibility.AccessibleExtendedText→Java.Awt.RectangleJavax.Accessibility.AccessibleText→Java.Awt.PointJavax.Accessibility.AccessibleText→Java.Awt.RectangleJavax.Accessibility.IAccessibleComponent→Java.Awt.ColorJavax.Accessibility.IAccessibleComponent→Java.Awt.CursorJavax.Accessibility.IAccessibleComponent→Java.Awt.DimensionJavax.Accessibility.IAccessibleComponent→Java.Awt.FontJavax.Accessibility.IAccessibleComponent→Java.Awt.FontMetricsJavax.Accessibility.IAccessibleComponent→Java.Awt.PointJavax.Accessibility.IAccessibleComponent→Java.Awt.RectangleJavax.Accessibility.IAccessibleExtendedText→Java.Awt.RectangleJavax.Accessibility.IAccessibleText→Java.Awt.PointJavax.Accessibility.IAccessibleText→Java.Awt.Rectangle
- Direction
- Javax.Accessibility uses Java.Awt, so a change to Java.Awt can break Javax.Accessibility, while a change to Javax.Accessibility can't break Java.Awt.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
39→4 Java.Awt uses Java.Util✕
- Connections
- 20 pairs of types, where a type in Java.Awt uses a type in Java.Util.
- The types involved
Java.Awt.AWTEvent→Java.Util.EventObjectJava.Awt.AWTEventMulticaster→Java.Util.EventListenerJava.Awt.Component→Java.Util.LocaleJava.Awt.Component→Java.Util.SetJava.Awt.ComponentOrientation→Java.Util.LocaleJava.Awt.ComponentOrientation→Java.Util.ResourceBundleJava.Awt.Font→Java.Util.LocaleJava.Awt.Font→Java.Util.MapJava.Awt.Graphics2D→Java.Util.MapJava.Awt.GraphicsEnvironment→Java.Util.LocaleJava.Awt.KeyboardFocusManager→Java.Util.SetJava.Awt.MenuBar→Java.Util.EnumerationJava.Awt.RenderingHints→Java.Util.CollectionJava.Awt.RenderingHints→Java.Util.EntryJava.Awt.RenderingHints→Java.Util.MapJava.Awt.RenderingHints→Java.Util.SetJava.Awt.Toolkit→Java.Util.MapJava.Awt.Toolkit→Java.Util.PropertiesJava.Awt.Window→Java.Util.ListJava.Awt.Window→Java.Util.ResourceBundle
- Direction
- Java.Awt uses Java.Util, so a change to Java.Util can break Java.Awt, while a change to Java.Awt can't break Java.Util.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→8 Java.Awt uses Java.Security✕
- Connections
- 1 pair of types, where a type in Java.Awt uses a type in Java.Security.
- The types involved
Java.Awt.AWTPermission→Java.Security.BasicPermission
- Direction
- Java.Awt uses Java.Security, so a change to Java.Security can break Java.Awt, while a change to Java.Awt can't break Java.Security.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→13 Java.Awt uses Java.Net✕
- Connections
- 3 pairs of types, where a type in Java.Awt uses a type in Java.Net.
- The types involved
Java.Awt.Desktop→Java.Net.URIJava.Awt.SplashScreen→Java.Net.URLJava.Awt.Toolkit→Java.Net.URL
- Direction
- Java.Awt uses Java.Net, so a change to Java.Net can break Java.Awt, while a change to Java.Awt can't break Java.Net.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→14 Java.Awt uses Java.Io✕
- Connections
- 34 pairs of types, where a type in Java.Awt uses a type in Java.Io. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.AWTKeyStroke→Java.Io.SerializableJava.Awt.BorderLayout→Java.Io.SerializableJava.Awt.CardLayout→Java.Io.SerializableJava.Awt.CheckboxGroup→Java.Io.SerializableJava.Awt.Color→Java.Io.SerializableJava.Awt.Component→Java.Io.PrintStreamJava.Awt.Component→Java.Io.PrintWriterJava.Awt.Component→Java.Io.SerializableJava.Awt.ComponentOrientation→Java.Io.SerializableJava.Awt.ContainerOrderFocusTraversalPolicy→Java.Io.SerializableJava.Awt.Cursor→Java.Io.SerializableJava.Awt.Desktop→Java.Io.FileJava.Awt.Dimension→Java.Io.SerializableJava.Awt.Event→Java.Io.SerializableJava.Awt.FileDialog→Java.Io.FileJava.Awt.FileDialog→Java.Io.FilenameFilterJava.Awt.FlowLayout→Java.Io.SerializableJava.Awt.Font→Java.Io.FileJava.Awt.Font→Java.Io.InputStreamJava.Awt.Font→Java.Io.SerializableJava.Awt.FontMetrics→Java.Io.SerializableJava.Awt.GraphicsConfigTemplate→Java.Io.SerializableJava.Awt.GridBagConstraints→Java.Io.SerializableJava.Awt.GridBagLayout→Java.Io.SerializableJava.Awt.GridBagLayoutInfo→Java.Io.Serializable
- Direction
- Java.Awt uses Java.Io, so a change to Java.Io can break Java.Awt, while a change to Java.Awt can't break Java.Io.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→16 Java.Awt uses Java.Lang✕
- Connections
- 81 pairs of types, where a type in Java.Awt uses a type in Java.Lang. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.AWTError→Java.Lang.ErrorJava.Awt.AWTEvent→Java.Lang.StringJava.Awt.AWTEventMulticaster→Java.Lang.ClassJava.Awt.AWTException→Java.Lang.ExceptionJava.Awt.AWTKeyStroke→Java.Lang.CharacterJava.Awt.AWTKeyStroke→Java.Lang.StringJava.Awt.AWTPermission→Java.Lang.StringJava.Awt.Action→Java.Lang.EnumJava.Awt.Action→Java.Lang.StringJava.Awt.BaselineResizeBehavior→Java.Lang.EnumJava.Awt.BaselineResizeBehavior→Java.Lang.StringJava.Awt.BorderLayout→Java.Lang.StringJava.Awt.BufferCapabilities→Java.Lang.CloneableJava.Awt.Button→Java.Lang.StringJava.Awt.CardLayout→Java.Lang.StringJava.Awt.Checkbox→Java.Lang.StringJava.Awt.CheckboxMenuItem→Java.Lang.StringJava.Awt.Choice→Java.Lang.StringJava.Awt.Color→Java.Lang.StringJava.Awt.ColorSpaceType→Java.Lang.EnumJava.Awt.ColorSpaceType→Java.Lang.StringJava.Awt.Component→Java.Lang.ClassJava.Awt.Component→Java.Lang.StringJava.Awt.Container→Java.Lang.StringJava.Awt.Cursor→Java.Lang.String
- Direction
- Java.Awt uses Java.Lang, so a change to Java.Lang can break Java.Awt, while a change to Java.Awt can't break Java.Lang.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→17 Java.Awt uses Java.Awt.ImageNs✕
- Connections
- 38 pairs of types, where a type in Java.Awt uses a type in Java.Awt.ImageNs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.AlphaComposite→Java.Awt.ImageNs.ColorModelJava.Awt.Canvas→Java.Awt.ImageNs.BufferStrategyJava.Awt.Color→Java.Awt.ImageNs.ColorModelJava.Awt.Component→Java.Awt.ImageNs.ColorModelJava.Awt.Component→Java.Awt.ImageNs.ImageObserverJava.Awt.Component→Java.Awt.ImageNs.ImageProducerJava.Awt.Component→Java.Awt.ImageNs.VolatileImageJava.Awt.Composite→Java.Awt.ImageNs.ColorModelJava.Awt.CompositeContext→Java.Awt.ImageNs.RasterJava.Awt.CompositeContext→Java.Awt.ImageNs.WritableRasterJava.Awt.GradientPaint→Java.Awt.ImageNs.ColorModelJava.Awt.Graphics→Java.Awt.ImageNs.ImageObserverJava.Awt.Graphics2D→Java.Awt.ImageNs.BufferedImageJava.Awt.Graphics2D→Java.Awt.ImageNs.BufferedImageOpJava.Awt.Graphics2D→Java.Awt.ImageNs.ImageObserverJava.Awt.Graphics2D→Java.Awt.ImageNs.RenderedImageJava.Awt.GraphicsConfiguration→Java.Awt.ImageNs.BufferedImageJava.Awt.GraphicsConfiguration→Java.Awt.ImageNs.ColorModelJava.Awt.GraphicsConfiguration→Java.Awt.ImageNs.VolatileImageJava.Awt.GraphicsEnvironment→Java.Awt.ImageNs.BufferedImageJava.Awt.IComposite→Java.Awt.ImageNs.ColorModelJava.Awt.ICompositeContext→Java.Awt.ImageNs.RasterJava.Awt.ICompositeContext→Java.Awt.ImageNs.WritableRasterJava.Awt.IPaint→Java.Awt.ImageNs.ColorModelJava.Awt.IPaintContext→Java.Awt.ImageNs.ColorModel
- Direction
- Java.Awt uses Java.Awt.ImageNs, so a change to Java.Awt.ImageNs can break Java.Awt, while a change to Java.Awt can't break Java.Awt.ImageNs.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→19 Java.Awt uses Java.Text✕
- Connections
- 5 pairs of types, where a type in Java.Awt uses a type in Java.Text.
- The types involved
Java.Awt.Font→Java.Text.AttributeJava.Awt.Font→Java.Text.CharacterIteratorJava.Awt.FontMetrics→Java.Text.CharacterIteratorJava.Awt.Graphics→Java.Text.AttributedCharacterIteratorJava.Awt.Graphics2D→Java.Text.AttributedCharacterIterator
- Direction
- Java.Awt uses Java.Text, so a change to Java.Text can break Java.Awt, while a change to Java.Awt can't break Java.Text.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→26 Java.Awt uses Java.Awt.EventNs✕
- Connections
- 68 pairs of types, where a type in Java.Awt uses a type in Java.Awt.EventNs. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
Java.Awt.AWTEventMulticaster→Java.Awt.EventNs.ActionEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ActionListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.AdjustmentEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.AdjustmentListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ComponentEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ComponentListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ContainerEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ContainerListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.FocusEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.FocusListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.HierarchyBoundsListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.HierarchyEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.HierarchyListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.InputMethodEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.InputMethodListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ItemEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.ItemListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.KeyEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.KeyListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.MouseEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.MouseListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.MouseMotionListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.MouseWheelEventJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.MouseWheelListenerJava.Awt.AWTEventMulticaster→Java.Awt.EventNs.TextEvent
- Direction
- Java.Awt uses Java.Awt.EventNs, so a change to Java.Awt.EventNs can break Java.Awt, while a change to Java.Awt can't break Java.Awt.EventNs.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→27 Java.Awt uses Java.Beans✕
- Connections
- 5 pairs of types, where a type in Java.Awt uses a type in Java.Beans.
- The types involved
Java.Awt.Component→Java.Beans.PropertyChangeListenerJava.Awt.KeyboardFocusManager→Java.Beans.PropertyChangeListenerJava.Awt.KeyboardFocusManager→Java.Beans.VetoableChangeListenerJava.Awt.SystemTray→Java.Beans.PropertyChangeListenerJava.Awt.Toolkit→Java.Beans.PropertyChangeListener
- Direction
- Java.Awt uses Java.Beans, so a change to Java.Beans can break Java.Awt, while a change to Java.Awt can't break Java.Beans.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
39→38 Java.Awt uses Javax.Accessibility✕
- Connections
- 15 pairs of types, where a type in Java.Awt uses a type in Javax.Accessibility.
- The types involved
Java.Awt.Button→Javax.Accessibility.AccessibleJava.Awt.Canvas→Javax.Accessibility.AccessibleJava.Awt.Checkbox→Javax.Accessibility.AccessibleJava.Awt.Choice→Javax.Accessibility.AccessibleJava.Awt.Component→Javax.Accessibility.AccessibleContextJava.Awt.Label→Javax.Accessibility.AccessibleJava.Awt.List→Javax.Accessibility.AccessibleJava.Awt.MenuBar→Javax.Accessibility.AccessibleJava.Awt.MenuComponent→Javax.Accessibility.AccessibleContextJava.Awt.MenuItem→Javax.Accessibility.AccessibleJava.Awt.Panel→Javax.Accessibility.AccessibleJava.Awt.ScrollPane→Javax.Accessibility.AccessibleJava.Awt.Scrollbar→Javax.Accessibility.AccessibleJava.Awt.TextComponent→Javax.Accessibility.AccessibleJava.Awt.Window→Javax.Accessibility.Accessible
- Direction
- Java.Awt uses Javax.Accessibility, so a change to Javax.Accessibility can break Java.Awt, while a change to Java.Awt can't break Javax.Accessibility.
- Position
- Below the diagonal: Java.Awt uses a module listed above it, which is the healthy direction.
40→4 Javax.Imageio uses Java.Util✕
- Connections
- 8 pairs of types, where a type in Javax.Imageio uses a type in Java.Util.
- The types involved
Javax.Imageio.IIOImage→Java.Util.ListJavax.Imageio.ImageIO→Java.Util.IteratorJavax.Imageio.ImageReader→Java.Util.IteratorJavax.Imageio.ImageReader→Java.Util.LocaleJavax.Imageio.ImageReader→Java.Util.SetJavax.Imageio.ImageWriteParam→Java.Util.LocaleJavax.Imageio.ImageWriter→Java.Util.ListJavax.Imageio.ImageWriter→Java.Util.Locale
- Direction
- Javax.Imageio uses Java.Util, so a change to Java.Util can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Util.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
40→13 Javax.Imageio uses Java.Net✕
- Connections
- 1 pair of types, where a type in Javax.Imageio uses a type in Java.Net.
- The types involved
Javax.Imageio.ImageIO→Java.Net.URL
- Direction
- Javax.Imageio uses Java.Net, so a change to Java.Net can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Net.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
40→14 Javax.Imageio uses Java.Io✕
- Connections
- 4 pairs of types, where a type in Javax.Imageio uses a type in Java.Io.
- The types involved
Javax.Imageio.IIOException→Java.Io.IOExceptionJavax.Imageio.ImageIO→Java.Io.FileJavax.Imageio.ImageIO→Java.Io.InputStreamJavax.Imageio.ImageIO→Java.Io.OutputStream
- Direction
- Javax.Imageio uses Java.Io, so a change to Java.Io can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Io.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
40→16 Javax.Imageio uses Java.Lang✕
- Connections
- 3 pairs of types, where a type in Javax.Imageio uses a type in Java.Lang.
- The types involved
Javax.Imageio.ImageIO→Java.Lang.StringJavax.Imageio.ImageReader→Java.Lang.StringJavax.Imageio.ImageWriteParam→Java.Lang.String
- Direction
- Javax.Imageio uses Java.Lang, so a change to Java.Lang can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Lang.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
40→17 Javax.Imageio uses Java.Awt.ImageNs✕
- Connections
- 15 pairs of types, where a type in Javax.Imageio uses a type in Java.Awt.ImageNs.
- The types involved
Javax.Imageio.IIOImage→Java.Awt.ImageNs.BufferedImageJavax.Imageio.IIOImage→Java.Awt.ImageNs.RasterJavax.Imageio.IIOImage→Java.Awt.ImageNs.RenderedImageJavax.Imageio.ImageIO→Java.Awt.ImageNs.BufferedImageJavax.Imageio.ImageIO→Java.Awt.ImageNs.RenderedImageJavax.Imageio.ImageReadParam→Java.Awt.ImageNs.BufferedImageJavax.Imageio.ImageReader→Java.Awt.ImageNs.BufferedImageJavax.Imageio.ImageReader→Java.Awt.ImageNs.RasterJavax.Imageio.ImageReader→Java.Awt.ImageNs.RenderedImageJavax.Imageio.ImageTypeSpecifier→Java.Awt.ImageNs.BufferedImageJavax.Imageio.ImageTypeSpecifier→Java.Awt.ImageNs.ColorModelJavax.Imageio.ImageTypeSpecifier→Java.Awt.ImageNs.RenderedImageJavax.Imageio.ImageTypeSpecifier→Java.Awt.ImageNs.SampleModelJavax.Imageio.ImageWriter→Java.Awt.ImageNs.RasterJavax.Imageio.ImageWriter→Java.Awt.ImageNs.RenderedImage
- Direction
- Javax.Imageio uses Java.Awt.ImageNs, so a change to Java.Awt.ImageNs can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Awt.ImageNs.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
40→39 Javax.Imageio uses Java.Awt✕
- Connections
- 6 pairs of types, where a type in Javax.Imageio uses a type in Java.Awt.
- The types involved
Javax.Imageio.IIOParam→Java.Awt.PointJavax.Imageio.IIOParam→Java.Awt.RectangleJavax.Imageio.ImageReadParam→Java.Awt.DimensionJavax.Imageio.ImageWriteParam→Java.Awt.DimensionJavax.Imageio.ImageWriter→Java.Awt.DimensionJavax.Imageio.ImageWriter→Java.Awt.Rectangle
- Direction
- Javax.Imageio uses Java.Awt, so a change to Java.Awt can break Javax.Imageio, while a change to Javax.Imageio can't break Java.Awt.
- Position
- Below the diagonal: Javax.Imageio uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 16 | Medium |
| A02:2025 — Security Misconfiguration | 4 | High / Critical |
| A07:2025 — Authentication Failures | 1 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj; Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj. | +6.2 pts | Low | ADR Quality |
| Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11. | +5.9 pts | Medium | Documentation accuracy |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +5.2 pts | Medium | Architecture documentation |
| Resolve the 2 BlanketAnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (2). | +2.3 pts | Low | Explicit Debt |
| Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with JNetReflectorHelper.cs (4). | +2.3 pts | Low | Explicit Debt |
| Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (7). | +2.3 pts | Low | Explicit Debt |
| Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps. | +2.6 pts | Medium | Data Protection |
| Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor). | +2.5 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/net/JNetReflector/JNetReflectorHelper.cs | 1.0 | Slop | Explicit Debt: EmptyCatchBlock |
| REDACTED | 3.4 | Slop | IaC & Container Security: High IaC: REDACTED |
| src/net/JNet/Generated/.editorconfig | 5.3 | Mixed | Explicit Debt: BlanketAnalyzerSeverityNone |
| src/net/JNet/Developed/.editorconfig | 5.8 | Mixed | Explicit Debt: BlanketAnalyzerSeverityNone |
| src/net/JNetReflector/InternalExtensions.cs | 6.0 | Mixed | Explicit Debt: CommentedOutCode |
| src/net/JNetReflector/InternalMethods.cs | 7.0 | Mixed | Cyclomatic Complexity: ReflectionUtils.AnalyzeMethods (cyclomatic 253) |
| src/net/JNetReflector/JNetReflectorCore.cs | 7.2 | Mixed | Cyclomatic Complexity: JNetReflectorCore.ProcessCommandLine (cyclomatic 74) |
| src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs | 7.2 | Mixed | Code Duplication: Edited copy of a member (28 corresponding lines) |
| REDACTED | 7.2 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java | 7.4 | Mixed | Cyclomatic Complexity: JNetHelper.listFromPrimitiveArray (cyclomatic 19) |
| src/net/Common/Common.props | 7.6 | Mixed | Explicit Debt: NoWarnInCsproj |
| src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs | 7.8 | Mixed | Cyclomatic Complexity: ParserAdapter.ListenerShallManageEventHandlers (cyclomatic 23) |
| src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs | 7.8 | Mixed | Cyclomatic Complexity: JNetCLICoreHelper.ProcessCLIParsedArgs (cyclomatic 21) |
| src/net/JNetCLICore/ProgramBase.cs | 7.8 | Mixed | Cyclomatic Complexity: ProgramBase.Start (cyclomatic 20) |
| src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs | 7.8 | Mixed | Cyclomatic Complexity: XMLReaderAdapter.ListenerShallManageEventHandlers (cyclomatic 19) |
| src/net/JNet/JNetCoreBase.cs | 7.8 | Mixed | Cognitive Complexity: JNetCoreBase.Launch (cognitive 25) |
| src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs | 7.8 | Mixed | Code Duplication: Duplicated block (33 lines × 2) |
| src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs | 7.8 | Mixed | Code Duplication: Duplicated block (15 lines × 3) |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 45 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 45 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 335 of 344 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .cs, .java, and our analyzer cannot run the .java test suite(s) — so no coverage was collected for the repository as a whole. The .NET half may well have built and run; what is missing is a coverage figure that covers the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (tests/jvm/jnettest, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 958 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 20 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .java (13,903 lines, 56% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — evaluation did not complete — Naming Consistency not included (check did not complete) — excluded from the score.
- D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D23 Boundary Type-Coupling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Large codebase (638,261 production LoC in the .NET projects) with no declared bounded contexts — cross-boundary type coupling is unassessed Bounded contexts cannot be inferred from a codebase that is not physically organised by them (D-321), so with none declared there are no boundaries for the coupling pass to measure across. You can widen what we reach: name this codebase's bounded contexts (≥2 module groups, e.g. per subsystem) so cross-boundary type coupling can be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D28 Secrets (history) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `gitleaks` TIMED OUT after 266.8s against a 266.8s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan. 1 of 2 declared ecosystem(s) (osv) WERE scanned and every vulnerability they reported is included in this result; nuget was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that nuget is free of known-vulnerable dependencies.
- AX6 Interface segregation — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 31 further occurrence(s) are not listed individually; the score already reflects all 71.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- P10 Library API & versioning — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 88 further occurrence(s) are not listed individually; the score already reflects all 128.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X18 Disposal-pattern correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X28 Index access outside its own emptiness guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X5 Nullable reference types — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/net/templates/templatepack.csproj, src/net/JNet/JNet.csproj, src/net/JNetCLI/JNetCLI.csproj, src/net/JNetPS/JNetPS.csproj, src/net/JNetPSCore/JNetPSCore.csproj and 1 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
- C5 Data-Subject Rights: This control is scored from in-repo evidence only — absence of evidence here means the scan found no in-repo trace, not that the control does not exist.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ReflectionUtils.AnalyzeMethods at 253. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being JNetReflectorExtensions.IsNetNativeType at 22 — they are counted neither in the figure above nor in this dimension's score.
What to do
- Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with ReflectionUtils.AnalyzeMethods (cyclomatic 253). — Refactoring it lifts Cyclomatic Complexity from 5.2 to about 6.0/10.
D2 · Cognitive Complexity
35 method(s) exceeded the cognitive complexity threshold of 15; the worst was ReflectionUtils.AnalyzeMethods at 671.
What to do
- Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with ReflectionUtils.AnalyzeMethods (cognitive 671). — Refactoring it lifts Cognitive Complexity from 4.0 to about 5.1/10.
D3 · God Classes
9 god class(es) detected.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with InternalMethods.cs (4), JNetReflectorCore.cs, InternalExtensions.cs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with InternalMethods.cs, JNetReflectorCore.cs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with InternalMethods.cs. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
40 duplicated block group(s) detected. 0.2 % of the production lines (1,315 of 638,261) are in a reported copy. A further 12 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with InternalMethods.cs (3), JNetReflectorHelper.cs. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with InternalMethods.cs (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (15 lines × 2) finding(s) in Code Duplication — start with InternalExtensions.cs, InvokeQueryAndCmdletCommand.cs, InternalMethods.cs. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
24 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling — start with JNet.csproj. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 105 classes have LCOM4 above 3.
D13 · Secret Scanning
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
0 of 130 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 9 direct `PackageReference`(s), and 117 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
20 deducted debt markers + 5 dead symbols across 638261 LoC in the .NET projects (0.0/KLoC) → score 9.9. Measured on the .NET source only: .java (56% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 7 AnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (7). — One of this dimension's main actionable groups (7 issue-level).
- Resolve the 4 EmptyCatchBlock finding(s) in Explicit Debt — start with JNetReflectorHelper.cs (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 2 BlanketAnalyzerSeverityNone finding(s) in Explicit Debt — start with .editorconfig (2). — One of this dimension's main actionable groups (2 issue-level).
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 21 document(s) read across 9 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with JNetCLI.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 445 judged comments only repeat the code they sit on (0.0 %). 2 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 9 projects flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with JNet.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (osv). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (osv), and the findings above are real and complete for them. nuget was not scanned (nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan), so this is not the whole dependency surface and the result is reported at reduced confidence.
D31 · IaC & Container Security
4 finding(s): 0 critical, 1 high, 2 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 22 of the 64 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
3/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 10 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 9 platform declaration(s) and 4 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
- `JNetCLICoreHelper` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_mainClassToRun, _classToRun, _Interactive, _RunCommand, _NoLogo, _Script; e.g. `_mainClassToRun` at line 249). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:32
- `JNetReflectorExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CurrentJavadocBaseUrl, _CurrentJavadocVersion, _CurrentNoModule; e.g. `_CurrentJavadocBaseUrl` at line 50). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/InternalExtensions.cs:38
- `ReflectionUtils` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (TraceReportHandler, Level, namespaces, classes, JarOrModuleName, CancellationTokenSource; e.g. `TraceReportHandler` at line 56). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/InternalMethods.cs:36
- `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (_CopyrightFile, _JavaPLocationPath, _ConfigurationFromFile, _ClassesToAnalyze, _OriginRootPath, _JarsToAddInClassPath; e.g. `_CopyrightFile` at line 607). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/JNetReflectorCore.cs:34
- `JNetReflectorCore` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (CurrentClassPath; e.g. `CurrentClassPath` at line 913). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetReflector/JNetReflectorCore.cs:905
- `JNetPSHelperExtensions` keeps mutable `static` state — one slot for the whole process, shared by every thread that reaches the type however its instances are created — and mutates it outside any lock (processExited, cancelKeyRaised; e.g. `processExited` at line 127). Concurrent callers lose updates, and a collection that is not built for concurrent writers can corrupt. — src/net/JNetPSCore/JNetPSHelper.cs:37
What to do
- A `static` field is one slot for the whole process, however its type is created: back it with a thread-safe type (ConcurrentDictionary, Interlocked), take a lock around every write, or move it into a registered singleton that does.
AX3 · Project dependency cycles
- The namespaces Java.Applet ↔ Java.Awt ↔ Java.Awt.ColorNs ↔ Java.Awt.Datatransfer ↔ Java.Awt.Dnd ↔ Java.Awt.Dnd.Peer ↔ Java.Awt.EventNs ↔ Java.Awt.FontNs ↔ Java.Awt.Geom ↔ Java.Awt.Im ↔ Java.Awt.ImageNs ↔ Java.Awt.ImageNs.Renderable ↔ Java.Awt.Print ↔ Java.Beans ↔ Java.Beans.Beancontext ↔ Java.Io ↔ Java.Lang ↔ Java.Lang.Annotation ↔ Java.Lang.Reflect ↔ Java.Math ↔ Java.Net ↔ Java.Nio ↔ Java.Nio.Channels ↔ Java.Nio.Channels.Spi ↔ Java.Nio.Charset ↔ Java.Nio.File ↔ Java.Nio.File.Attribute ↔ Java.Nio.File.Spi ↔ Java.Security ↔ Java.Security.Cert ↔ Java.Text ↔ Java.Time ↔ Java.Time.Chrono ↔ Java.Time.Format ↔ Java.Time.Temporal ↔ Java.Time.Zone ↔ Java.Util ↔ Java.Util.Concurrent ↔ Java.Util.Jar ↔ Java.Util.Regex ↔ Java.Util.Stream ↔ Java.Util.Zip ↔ Javax.Accessibility ↔ Javax.Print ↔ Javax.Print.Attribute ↔ Javax.Print.Event ↔ Javax.Security.Auth ↔ Javax.Security.Auth.Callback ↔ Javax.Security.Auth.X500 ↔ Javax.Swing ↔ Javax.Swing.Border ↔ Javax.Swing.Colorchooser ↔ Javax.Swing.Event ↔ Javax.Swing.Filechooser ↔ Javax.Swing.Plaf ↔ Javax.Swing.Plaf.Basic ↔ Javax.Swing.Table ↔ Javax.Swing.Text ↔ Javax.Swing.Tree ↔ Javax.Swing.Undo ↔ MASES.JNet.Specific ↔ MASES.JNet.Specific.Extensions ↔ Org.Xml.Sax ↔ Org.Xml.Sax.Helpers depend on each other. The lightest dependency in the cycle is Java.Awt → Java.Awt.ColorNs (Java.Awt.Color → Java.Awt.ColorNs.ColorSpace, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Java/Awt/Color.cs:32
- The namespaces Javax.Management ↔ Javax.Management.Loading depend on each other. The lightest dependency in the cycle is Javax.Management → Javax.Management.Loading (Javax.Management.IMBeanServer → Javax.Management.Loading.ClassLoaderRepository, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66
- The namespaces Javax.Lang.Model.Element ↔ Javax.Lang.Model.Type depend on each other. The lightest dependency in the cycle is Javax.Lang.Model.Type → Javax.Lang.Model.Element (Javax.Lang.Model.Type.DeclaredType → Javax.Lang.Model.Element.Element, 4 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Lang/Model/Type/DeclaredType.cs:32
- The namespaces Javax.Imageio ↔ Javax.Imageio.Event ↔ Javax.Imageio.Metadata ↔ Javax.Imageio.Spi depend on each other. The lightest dependency in the cycle is Javax.Imageio.Spi → Javax.Imageio.Metadata (Javax.Imageio.Spi.ImageReaderWriterSpi → Javax.Imageio.Metadata.IIOMetadataFormat, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Imageio/Spi/ImageReaderWriterSpi.cs:32
- The namespaces Javax.Sql.Rowset ↔ Javax.Sql.Rowset.Spi depend on each other. The lightest dependency in the cycle is Javax.Sql.Rowset → Javax.Sql.Rowset.Spi (Javax.Sql.Rowset.CachedRowSet → Javax.Sql.Rowset.Spi.SyncProvider, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:32
- The namespaces Javax.Xml.Stream ↔ Javax.Xml.Stream.Events ↔ Javax.Xml.Stream.Util depend on each other. The lightest dependency in the cycle is Javax.Xml.Stream → Javax.Xml.Stream.Util (Javax.Xml.Stream.IXMLEventWriter → Javax.Xml.Stream.Util.IXMLEventConsumer, 3 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Stream/XMLEventWriter.cs:66
- The namespaces Javax.Xml.Crypto ↔ Javax.Xml.Crypto.Dsig.Keyinfo depend on each other. The lightest dependency in the cycle is Javax.Xml.Crypto → Javax.Xml.Crypto.Dsig.Keyinfo (Javax.Xml.Crypto.KeySelector → Javax.Xml.Crypto.Dsig.Keyinfo.KeyInfo, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Crypto/KeySelector.cs:32
- The namespaces Javax.Xml.Ws ↔ Javax.Xml.Ws.Handler depend on each other. The lightest dependency in the cycle is Javax.Xml.Ws.Handler → Javax.Xml.Ws (Javax.Xml.Ws.Handler.ILogicalMessageContext → Javax.Xml.Ws.LogicalMessage, 2 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — src/net/JNet/Generated/Javax/Xml/Ws/Handler/LogicalMessageContext.cs:66
What to do
- Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
AX5 · Architecture & structure
AX6 · Interface segregation
- `IInputMethod` declares 16 members: `ControlObject`, `Locale`, `IsCompositionEnabled`, `SetLocale`, `Activate`, `Deactivate`, `DispatchEvent`, `DisposeJVM`, `EndComposition`, `HideWindows`, `NotifyClientWindowChange`, `Reconvert`, `RemoveNotify`, `SetCharacterSubsets`, `SetCompositionEnabled`, `SetInputMethodContext`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Awt/Im/Spi/InputMethod.cs:66
- `IRenderedImage` declares 21 members: `ColorModel`, `Data`, `Height`, `MinTileX`, `MinTileY`, `MinX`, `MinY`, `NumXTiles`, `NumYTiles`, `PropertyNames`, `SampleModel`, `Sources`, `TileGridXOffset`, `TileGridYOffset`, `TileHeight`, `TileWidth`, `Width`, `GetData`, `GetTile`, `CopyData`, `GetProperty`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Awt/ImageNs/RenderedImage.cs:66
- `IMemoryPoolMXBean` declares 16 members: `CollectionUsage`, `CollectionUsageThreshold`, `CollectionUsageThresholdCount`, `MemoryManagerNames`, `Name`, `PeakUsage`, `Type`, `Usage`, `UsageThreshold`, `UsageThresholdCount`, `IsCollectionUsageThresholdExceeded`, `IsCollectionUsageThresholdSupported`, `IsUsageThresholdExceeded`, `IsUsageThresholdSupported`, `IsValid`, `ResetPeakUsage`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/MemoryPoolMXBean.cs:66
- `IRuntimeMXBean` declares 16 members: `BootClassPath`, `ClassPath`, `InputArguments`, `LibraryPath`, `ManagementSpecVersion`, `Name`, `SpecName`, `SpecVendor`, `SpecVersion`, `StartTime`, `SystemProperties`, `Uptime`, `VmName`, `VmVendor`, `VmVersion`, `IsBootClassPathSupported`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/RuntimeMXBean.cs:66
- `IThreadMXBean` declares 27 members: `AllThreadIds`, `CurrentThreadCpuTime`, `CurrentThreadUserTime`, `DaemonThreadCount`, `PeakThreadCount`, `ThreadCount`, `TotalStartedThreadCount`, `IsCurrentThreadCpuTimeSupported`, `IsObjectMonitorUsageSupported`, `IsSynchronizerUsageSupported`, `IsThreadContentionMonitoringEnabled`, `IsThreadContentionMonitoringSupported`, `IsThreadCpuTimeEnabled`, `IsThreadCpuTimeSupported`, `GetThreadInfo`, `GetThreadInfo`, `DumpAllThreads`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadInfo`, `GetThreadCpuTime`, `GetThreadUserTime`, `FindDeadlockedThreads`, `FindMonitorDeadlockedThreads`, `ResetPeakThreadCount`, `SetThreadContentionMonitoringEnabled`, `SetThreadCpuTimeEnabled`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Lang/Management/ThreadMXBean.cs:66
- `IPath` declares 27 members: `FileName`, `FileSystem`, `NameCount`, `Parent`, `Root`, `EndsWith`, `EndsWith`, `IsAbsolute`, `StartsWith`, `StartsWith`, `CompareTo`, `ToFile`, `ToUri`, `GetName`, `Normalize`, `Relativize`, `Resolve`, `Resolve`, `ResolveSibling`, `ResolveSibling`, `Subpath`, `ToAbsolutePath`, `ToRealPath`, `Register`, `Register`, `Iterator`, `CompareTo`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Nio/File/Path.cs:66
- `IChronoLocalDate` declares 25 members: `Chronology`, `Era`, `LengthOfMonth`, `Until`, `Until`, `Query`, `IsAfter`, `IsBefore`, `IsEqual`, `IsLeapYear`, `IsSupported`, `IsSupported`, `CompareTo`, `CompareTo`, `LengthOfYear`, `Format`, `AtTime`, `AdjustInto`, `Minus`, `Minus`, `Plus`, `Plus`, `With`, `With`, `ToEpochDay`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Time/Chrono/ChronoLocalDate.cs:66
- `IChronology` declares 24 members: `CalendarType`, `Id`, `IsLeapYear`, `CompareTo`, `ProlepticYear`, `Date`, `Date`, `DateEpochDay`, `DateYearDay`, `ResolveDate`, `EraOf`, `Range`, `Eras`, `CompareTo`, `GetDisplayName`, `Date`, `DateNow`, `DateNow`, `DateNow`, `DateYearDay`, `LocalDateTime`, `Period`, `ZonedDateTime`, `ZonedDateTime`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 24 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Time/Chrono/Chronology.cs:66
- `ICollection<E>` declares 17 members: `ToArray`, `Add`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Size`, `ToArray`, `Iterator`, `Clear`, `RemoveIf`, `Spliterator`, `ParallelStream`, `Stream`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 17 declarations carry 16 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 16 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Collection.cs:276
- `IDeque<E>` declares 27 members: `First`, `Last`, `Add`, `Contains`, `Offer`, `OfferFirst`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `PeekFirst`, `PeekLast`, `Poll`, `PollFirst`, `PollLast`, `Pop`, `Remove`, `RemoveFirst`, `RemoveLast`, `Size`, `DescendingIterator`, `Iterator`, `AddFirst`, `AddLast`, `Push`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Deque.cs:354
- `IList<E>` declares 26 members: `ToArray`, `Add`, `AddAll`, `AddAll`, `Contains`, `ContainsAll`, `IsEmpty`, `Remove`, `RemoveAll`, `RetainAll`, `Get`, `Remove`, `Set`, `IndexOf`, `LastIndexOf`, `Size`, `ToArray`, `Iterator`, `SubList`, `ListIterator`, `ListIterator`, `Add`, `Clear`, `Spliterator`, `ReplaceAll`, `Sort`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 26 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/List.cs:359
- `IMap<K, V>` declares 23 members: `ContainsKey`, `ContainsValue`, `IsEmpty`, `Size`, `Values`, `EntrySet`, `KeySet`, `Get`, `Put`, `Remove`, `Clear`, `PutAll`, `Remove`, `Replace`, `Compute`, `ComputeIfAbsent`, `ComputeIfPresent`, `GetOrDefault`, `Merge`, `PutIfAbsent`, `Replace`, `ForEach`, `ReplaceAll`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 23 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Map.cs:594
- `INavigableMap<K, V>` declares 21 members: `CeilingEntry`, `FirstEntry`, `FloorEntry`, `HigherEntry`, `LastEntry`, `LowerEntry`, `PollFirstEntry`, `PollLastEntry`, `DescendingMap`, `HeadMap`, `SubMap`, `TailMap`, `DescendingKeySet`, `NavigableKeySet`, `HeadMap`, `SubMap`, `TailMap`, `CeilingKey`, `FloorKey`, `HigherKey`, `LowerKey`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 21 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/NavigableMap.cs:321
- `IBlockingDeque<E>` declares 29 members: `Add`, `Contains`, `Offer`, `Offer`, `OfferFirst`, `OfferFirst`, `OfferLast`, `OfferLast`, `Remove`, `RemoveFirstOccurrence`, `RemoveLastOccurrence`, `Element`, `Peek`, `Poll`, `Poll`, `PollFirst`, `PollLast`, `Remove`, `Take`, `TakeFirst`, `TakeLast`, `Size`, `Iterator`, `AddFirst`, `AddLast`, `Push`, `Put`, `PutFirst`, `PutLast`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 29 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Concurrent/BlockingDeque.cs:407
- `ICompletionStage<T>` declares 38 members: `ThenCombine`, `ThenCombineAsync`, `ThenCombineAsync`, `ThenAcceptBoth`, `ThenAcceptBothAsync`, `ThenAcceptBothAsync`, `ApplyToEither`, `ApplyToEitherAsync`, `ApplyToEitherAsync`, `Handle`, `HandleAsync`, `HandleAsync`, `ThenApply`, `ThenApplyAsync`, `ThenApplyAsync`, `ThenCompose`, `ThenComposeAsync`, `ThenComposeAsync`, `ToCompletableFuture`, `AcceptEither`, `AcceptEitherAsync`, `AcceptEitherAsync`, `RunAfterBoth`, `RunAfterBothAsync`, `RunAfterBothAsync`, `RunAfterEither`, `RunAfterEitherAsync`, `RunAfterEitherAsync`, `ThenAccept`, `ThenAcceptAsync`, `ThenAcceptAsync`, `ThenRun`, `ThenRunAsync`, `ThenRunAsync`, `Exceptionally`, `WhenComplete`, `WhenCompleteAsync`, `WhenCompleteAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 38 declarations carry 26 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 26 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Concurrent/CompletionStage.cs:503
- `IDoubleStream` declares 33 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `MapToInt`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 33 declarations carry 32 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 32 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/DoubleStream.cs:66
- `IIntStream` declares 35 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `Reduce`, `Sum`, `ToArray`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `AsLongStream`, `MapToLong`, `Boxed`, `Count`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 35 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/IntStream.cs:66
- `ILongStream` declares 34 members: `Collect`, `MapToObj`, `AllMatch`, `AnyMatch`, `NoneMatch`, `SummaryStatistics`, `Average`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `AsDoubleStream`, `MapToDouble`, `MapToInt`, `Distinct`, `Filter`, `FlatMap`, `Limit`, `Map`, `Peek`, `Skip`, `Sorted`, `Boxed`, `Count`, `Reduce`, `Sum`, `ToArray`, `ForEach`, `ForEachOrdered`, `Iterator`, `Spliterator`, `Parallel`, `Sequential`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 34 declarations carry 33 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 33 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/LongStream.cs:66
- `IStream<T>` declares 32 members: `ToArray`, `Collect`, `FlatMap`, `Map`, `Collect`, `Reduce`, `AllMatch`, `AnyMatch`, `NoneMatch`, `ToArray`, `FindAny`, `FindFirst`, `Max`, `Min`, `Reduce`, `FlatMapToDouble`, `MapToDouble`, `FlatMapToInt`, `MapToInt`, `FlatMapToLong`, `MapToLong`, `Distinct`, `Filter`, `Limit`, `Peek`, `Skip`, `Sorted`, `Sorted`, `Count`, `Reduce`, `ForEach`, `ForEachOrdered`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 32 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Util/Stream/Stream.cs:472
- `ICallableStatement` declares 121 members: `GetObject`, `GetObject`, `GetBoolean`, `GetBoolean`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `GetInt`, `GetInt`, `GetCharacterStream`, `GetCharacterStream`, `GetNCharacterStream`, `GetNCharacterStream`, `GetObject`, `GetObject`, `GetObject`, `GetObject`, `GetNString`, `GetNString`, `GetString`, `GetString`, `GetBigDecimal`, `GetBigDecimal`, `GetBigDecimal`, `GetURL`, `GetURL`, `GetArray`, `GetArray`, `GetBlob`, `GetBlob`, `GetClob`, `GetClob`, `GetDate`, `GetDate`, and 81 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 121 declarations carry 53 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 53 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/CallableStatement.cs:66
- `IConnection` declares 45 members: `AutoCommit`, `Catalog`, `ClientInfo`, `Holdability`, `MetaData`, `NetworkTimeout`, `Schema`, `TransactionIsolation`, `TypeMap`, `Warnings`, `IsClosed`, `IsReadOnly`, `IsValid`, `GetClientInfo`, `NativeSQL`, `CreateArrayOf`, `CreateBlob`, `PrepareCall`, `PrepareCall`, `PrepareCall`, `CreateClob`, `CreateNClob`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `PrepareStatement`, `SetSavepoint`, `SetSavepoint`, `CreateSQLXML`, `CreateStatement`, `CreateStatement`, `CreateStatement`, `CreateStruct`, `Abort`, `ClearWarnings`, `Close`, `Commit`, `ReleaseSavepoint`, and 5 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 45 declarations carry 34 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 34 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/Connection.cs:66
- `IDatabaseMetaData` declares 176 members: `Catalogs`, `CatalogSeparator`, `CatalogTerm`, `ClientInfoProperties`, `Connection`, `DatabaseMajorVersion`, `DatabaseMinorVersion`, `DatabaseProductName`, `DatabaseProductVersion`, `DefaultTransactionIsolation`, `DriverMajorVersion`, `DriverMinorVersion`, `DriverName`, `DriverVersion`, `ExtraNameCharacters`, `IdentifierQuoteString`, `JDBCMajorVersion`, `JDBCMinorVersion`, `MaxBinaryLiteralLength`, `MaxCatalogNameLength`, `MaxCharLiteralLength`, `MaxColumnNameLength`, `MaxColumnsInGroupBy`, `MaxColumnsInIndex`, `MaxColumnsInOrderBy`, `MaxColumnsInSelect`, `MaxColumnsInTable`, `MaxConnections`, `MaxCursorNameLength`, `MaxIndexLength`, `MaxLogicalLobSize`, `MaxProcedureNameLength`, `MaxRowSize`, `MaxSchemaNameLength`, `MaxStatementLength`, `MaxStatements`, `MaxTableNameLength`, `MaxTablesInSelect`, `MaxUserNameLength`, `NumericFunctions`, and 136 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 176 declarations carry 175 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 175 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/DatabaseMetaData.cs:66
- `IPreparedStatement` declares 58 members: `MetaData`, `ParameterMetaData`, `Execute`, `ExecuteUpdate`, `ExecuteQuery`, `AddBatch`, `ClearParameters`, `SetArray`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetBigDecimal`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBoolean`, `SetByte`, `SetBytes`, `SetCharacterStream`, `SetCharacterStream`, `SetCharacterStream`, `SetClob`, `SetClob`, `SetClob`, `SetDate`, `SetDate`, `SetDouble`, `SetFloat`, `SetInt`, `SetLong`, `SetNCharacterStream`, `SetNCharacterStream`, `SetNClob`, `SetNClob`, `SetNClob`, `SetNString`, `SetNull`, and 18 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 58 declarations carry 37 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 37 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/PreparedStatement.cs:66
- `IResultSet` declares 191 members: `Concurrency`, `CursorName`, `FetchDirection`, `FetchSize`, `Holdability`, `MetaData`, `Row`, `Statement`, `Type`, `Warnings`, `GetObject`, `GetObject`, `Absolute`, `First`, `GetBoolean`, `GetBoolean`, `IsAfterLast`, `IsBeforeFirst`, `IsClosed`, `IsFirst`, `IsLast`, `Last`, `Next`, `Previous`, `Relative`, `RowDeleted`, `RowInserted`, `RowUpdated`, `WasNull`, `GetByte`, `GetByte`, `GetBytes`, `GetBytes`, `GetDouble`, `GetDouble`, `GetFloat`, `GetFloat`, `FindColumn`, `GetInt`, `GetInt`, and 151 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 191 declarations carry 92 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 92 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/ResultSet.cs:66
- `IResultSetMetaData` declares 21 members: `ColumnCount`, `IsAutoIncrement`, `IsCaseSensitive`, `IsCurrency`, `IsDefinitelyWritable`, `IsReadOnly`, `IsSearchable`, `IsSigned`, `IsWritable`, `GetColumnDisplaySize`, `GetColumnType`, `GetPrecision`, `GetScale`, `IsNullable`, `GetCatalogName`, `GetColumnClassName`, `GetColumnLabel`, `GetColumnName`, `GetColumnTypeName`, `GetSchemaName`, `GetTableName`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/ResultSetMetaData.cs:66
- `ISQLInput` declares 28 members: `ReadBoolean`, `WasNull`, `ReadByte`, `ReadBytes`, `ReadDouble`, `ReadFloat`, `ReadInt`, `ReadAsciiStream`, `ReadBinaryStream`, `ReadCharacterStream`, `ReadObject`, `ReadNString`, `ReadString`, `ReadBigDecimal`, `ReadURL`, `ReadArray`, `ReadBlob`, `ReadClob`, `ReadDate`, `ReadNClob`, `ReadRef`, `ReadRowId`, `ReadSQLXML`, `ReadTime`, `ReadTimestamp`, `ReadLong`, `ReadShort`, `ReadObject`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 28 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/SQLInput.cs:66
- `ISQLOutput` declares 28 members: `WriteArray`, `WriteAsciiStream`, `WriteBigDecimal`, `WriteBinaryStream`, `WriteBlob`, `WriteBoolean`, `WriteByte`, `WriteBytes`, `WriteCharacterStream`, `WriteClob`, `WriteDate`, `WriteDouble`, `WriteFloat`, `WriteInt`, `WriteLong`, `WriteNClob`, `WriteNString`, `WriteObject`, `WriteRef`, `WriteRowId`, `WriteShort`, `WriteSQLXML`, `WriteString`, `WriteStruct`, `WriteTime`, `WriteTimestamp`, `WriteURL`, `WriteObject`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 28 declarations carry 27 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 27 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/SQLOutput.cs:66
- `IStatement` declares 44 members: `Connection`, `FetchDirection`, `FetchSize`, `GeneratedKeys`, `LargeMaxRows`, `LargeUpdateCount`, `MaxFieldSize`, `MaxRows`, `MoreResults`, `QueryTimeout`, `ResultSet`, `ResultSetConcurrency`, `ResultSetHoldability`, `ResultSetType`, `UpdateCount`, `Warnings`, `Execute`, `Execute`, `Execute`, `Execute`, `GetMoreResults`, `IsClosed`, `IsCloseOnCompletion`, `IsPoolable`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteUpdate`, `ExecuteBatch`, `ExecuteQuery`, `AddBatch`, `Cancel`, `ClearBatch`, `ClearWarnings`, `Close`, `CloseOnCompletion`, `SetCursorName`, `SetEscapeProcessing`, `SetPoolable`, `ExecuteLargeUpdate`, and 4 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 44 declarations carry 35 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 35 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Java/Sql/Statement.cs:66
- `IMBeanServer` declares 36 members: `ClassLoaderRepository`, `DefaultDomain`, `Domains`, `MBeanCount`, `IsInstanceOf`, `IsRegistered`, `Deserialize`, `Deserialize`, `Deserialize`, `GetClassLoader`, `GetClassLoaderFor`, `GetAttribute`, `Instantiate`, `Instantiate`, `Instantiate`, `Instantiate`, `Invoke`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `RegisterMBean`, `AddNotificationListener`, `AddNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 36 declarations carry 24 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 24 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66
- `IMBeanServerConnection` declares 25 members: `DefaultDomain`, `Domains`, `MBeanCount`, `IsInstanceOf`, `IsRegistered`, `GetAttribute`, `Invoke`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `AddNotificationListener`, `AddNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListener`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 25 declarations carry 18 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 18 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/MBeanServerConnection.cs:66
- `IRelationServiceMBean` declares 33 members: `AllRelationIds`, `AllRelationTypeNames`, `PurgeFlag`, `HasRelation`, `CheckRoleReading`, `CheckRoleWriting`, `GetRoleCardinality`, `GetRelationTypeName`, `IsRelation`, `FindRelationsOfType`, `GetRole`, `GetRoleInfos`, `FindReferencingRelations`, `FindAssociatedMBeans`, `GetReferencedMBeans`, `IsRelationMBean`, `GetRoleInfo`, `GetAllRoles`, `GetRoles`, `SetRoles`, `AddRelation`, `AddRelationType`, `CreateRelation`, `CreateRelationType`, `IsActive`, `PurgeRelations`, `RemoveRelation`, `RemoveRelationType`, `SendRelationCreationNotification`, `SendRelationRemovalNotification`, `SendRoleUpdateNotification`, `SetRole`, `UpdateRoleMap`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Relation/RelationServiceMBean.cs:66
- `IRMIConnection` declares 27 members: `ConnectionId`, `IsInstanceOf`, `IsRegistered`, `GetMBeanCount`, `AddNotificationListeners`, `GetAttribute`, `Invoke`, `GetDefaultDomain`, `GetDomains`, `QueryMBeans`, `QueryNames`, `GetAttributes`, `SetAttributes`, `GetMBeanInfo`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `CreateMBean`, `GetObjectInstance`, `FetchNotifications`, `AddNotificationListener`, `Close`, `RemoveNotificationListener`, `RemoveNotificationListener`, `RemoveNotificationListeners`, `SetAttribute`, `UnregisterMBean`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 27 declarations carry 23 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 23 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnection.cs:66
- `ITimerMBean` declares 22 members: `AllNotificationIDs`, `NbNotifications`, `SendPastNotifications`, `IsActive`, `IsEmpty`, `GetFixedRate`, `AddNotification`, `AddNotification`, `AddNotification`, `AddNotification`, `GetNbOccurences`, `GetPeriod`, `GetNotificationUserData`, `GetNotificationMessage`, `GetNotificationType`, `GetDate`, `GetNotificationIDs`, `RemoveAllNotifications`, `RemoveNotification`, `RemoveNotifications`, `Start`, `Stop`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 19 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 19 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Management/Timer/TimerMBean.cs:66
- `IContext` declares 29 members: `Environment`, `NameInNamespace`, `AddToEnvironment`, `Lookup`, `Lookup`, `LookupLink`, `LookupLink`, `RemoveFromEnvironment`, `ComposeName`, `CreateSubcontext`, `CreateSubcontext`, `ComposeName`, `GetNameParser`, `GetNameParser`, `ListBindings`, `ListBindings`, `List`, `List`, `Bind`, `Bind`, `Close`, `DestroySubcontext`, `DestroySubcontext`, `Rebind`, `Rebind`, `Rename`, `Rename`, `Unbind`, `Unbind`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 29 declarations carry 17 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 17 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Naming/Context.cs:66
- `IDirContext` declares 26 members under just 8 distinct name(s): `GetAttributes`, `GetAttributes`, `GetAttributes`, `GetAttributes`, `CreateSubcontext`, `CreateSubcontext`, `GetSchema`, `GetSchema`, `GetSchemaClassDefinition`, `GetSchemaClassDefinition`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Search`, `Bind`, `Bind`, `ModifyAttributes`, `ModifyAttributes`, `ModifyAttributes`, `ModifyAttributes`, `Rebind`, `Rebind`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. That is an OVERLOAD SET, not 26 separate responsibilities: a caller binds to 8 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 26 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — src/net/JNet/Generated/Javax/Naming/Directory/DirContext.cs:66
- `IRowSet` declares 104 members: `Command`, `DataSourceName`, `EscapeProcessing`, `MaxFieldSize`, `MaxRows`, `Password`, `QueryTimeout`, `TransactionIsolation`, `TypeMap`, `Url`, `Username`, `IsReadOnly`, `AddRowSetListener`, `ClearParameters`, `Execute`, `RemoveRowSetListener`, `SetArray`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetAsciiStream`, `SetBigDecimal`, `SetBigDecimal`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBinaryStream`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBlob`, `SetBoolean`, `SetBoolean`, `SetByte`, `SetByte`, `SetBytes`, `SetBytes`, `SetCharacterStream`, and 64 more. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 104 declarations carry 47 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 47 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/RowSet.cs:66
- `IRowSetMetaData` declares 17 members: `SetAutoIncrement`, `SetCaseSensitive`, `SetCatalogName`, `SetColumnCount`, `SetColumnDisplaySize`, `SetColumnLabel`, `SetColumnName`, `SetColumnType`, `SetColumnTypeName`, `SetCurrency`, `SetNullable`, `SetPrecision`, `SetScale`, `SetSchemaName`, `SetSearchable`, `SetSigned`, `SetTableName`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/RowSetMetaData.cs:66
- `ICachedRowSet` declares 36 members: `KeyColumns`, `Original`, `OriginalRow`, `PageSize`, `RowSetWarnings`, `ShowDeleted`, `SyncProvider`, `TableName`, `ColumnUpdated`, `ColumnUpdated`, `NextPage`, `PreviousPage`, `Size`, `ToCollection`, `ToCollection`, `ToCollection`, `CreateShared`, `CreateCopy`, `CreateCopyNoConstraints`, `CreateCopySchema`, `AcceptChanges`, `AcceptChanges`, `Commit`, `Execute`, `Populate`, `Populate`, `Release`, `RestoreOriginal`, `Rollback`, `Rollback`, `RowSetPopulated`, `SetMetaData`, `SetOriginalRow`, `UndoDelete`, `UndoInsert`, `UndoUpdate`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 36 declarations carry 30 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 30 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:66
- `IButtonModel` declares 19 members: `ActionCommand`, `Mnemonic`, `IsArmed`, `IsEnabled`, `IsPressed`, `IsRollover`, `IsSelected`, `AddActionListener`, `AddChangeListener`, `AddItemListener`, `RemoveActionListener`, `RemoveChangeListener`, `RemoveItemListener`, `SetArmed`, `SetEnabled`, `SetGroup`, `SetPressed`, `SetRollover`, `SetSelected`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Swing/ButtonModel.cs:66
- `IListSelectionModel` declares 16 members: `AnchorSelectionIndex`, `LeadSelectionIndex`, `MaxSelectionIndex`, `MinSelectionIndex`, `SelectionMode`, `ValueIsAdjusting`, `IsSelectedIndex`, `IsSelectionEmpty`, `AddListSelectionListener`, `AddSelectionInterval`, `ClearSelection`, `InsertIndexInterval`, `RemoveIndexInterval`, `RemoveListSelectionListener`, `RemoveSelectionInterval`, `SetSelectionInterval`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — src/net/JNet/Generated/Javax/Swing/ListSelectionModel.cs:66
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
- Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (Azure Key Vault / AWS KMS / IDataProtector key ring) and encrypt the most sensitive columns (EF HasConversion encryption or provider-native column encryption) — partial coverage still leaves gaps.
- Enforce HTTPS (UseHttpsRedirection / RequireHttpsMetadata) so data in transit is always encrypted.
C4 · Data Retention
- A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (PurgeOlderThan / CleanupJob).
What to do
- Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
C5 · Data-Subject Rights
- Corroborated rights: erasure ✓ · export ✗ · consent ✗. Each tick means this scan found code in the repository implementing that right — a deletion/anonymisation path for erasure, a data-export or portability path for export, and consent state recorded alongside the personal data it authorises. A ✗ therefore means no such code was recognised HERE, not that the right is unsupported: a capability provided by a platform, a manual runbook, or code spelled in a way this scan does not match is not visible to it. Confirm before treating a cross as a gap; where it is one, the right has to be fulfilled manually.
What to do
- Implement data export/portability for a data subject (a machine-readable export of their personal data).
- Track GDPR consent (lawful basis) alongside the personal data it authorises.
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — CONTRIBUTING.md:48
- README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:120
- README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:138
- src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/performance.md:30
- src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/support.md:17
- src/documentation/articles/usage.md names .NET 9, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/usage.md:66
- src/documentation/articles/usageCLI.md names .NET 6, but the projects target .NET 10, 11. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — src/documentation/articles/usageCLI.md:12
What to do
- Reconcile the README with reality: CONTRIBUTING.md links to `PULL_REQUEST_TEMPLATE.md`, but `PULL_REQUEST_TEMPLATE.md` does not exist; README.md links to `articles/usage.md#intel-cet-and-jnet`, but `articles/usage.md` does not exist; README.md links to `articles/usageReflector.md`, but `articles/usageReflector.md` does not exist; src/documentation/articles/performance.md names .NET 8, but the projects target .NET 10, 11; src/documentation/articles/support.md names .NET 8, but the projects target .NET 10, 11.
P1 · CI/CD gates
P10 · Library API & versioning
- 6 public types in `Java.Net` are marked as implementation by their own namespace, folder or name: `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `DatagramSocketImpl` (src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`), `SocketImpl` (src/net/JNet/Generated/Java/Net/SocketImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32
- 3 public types in `Javax.Imageio.Metadata` are marked as implementation by their own namespace, folder or name: `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`), `IIOMetadataFormatImpl` (src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32
- 6 public types in `Javax.Imageio.Stream` are marked as implementation by their own namespace, folder or name: `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageInputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`), `ImageOutputStreamImpl` (src/net/JNet/Generated/Javax/Imageio/Stream/ImageOutputStreamImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32
- 12 public types in `Javax.Management.Remote.Rmi` are marked as implementation by their own namespace, folder or name: `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIConnectionImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIIIOPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIIIOPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), `RMIJRMPServerImpl` (src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIJRMPServerImpl.cs:32, name ends in `Impl`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32
- 3 public types in `Javax.Sql.Rowset` are marked as implementation by their own namespace, folder or name: `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`), `RowSetMetaDataImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32
- 6 public types in `Javax.Sql.Rowset.Serial` are marked as implementation by their own namespace, folder or name: `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLInputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`), `SQLOutputImpl` (src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLOutputImpl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32
- 21 public types in `Javax.Xml.Bind.Helpers` are marked as implementation by their own namespace, folder or name: `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractMarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `AbstractUnmarshallerImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractUnmarshallerImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), `NotIdentifiableEventImpl` (src/net/JNet/Generated/Javax/Xml/Bind/Helpers/NotIdentifiableEventImpl.cs:32, name ends in `Impl`), and 13 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32
- 6 public types in `Org.Xml.Sax.Ext` are marked as implementation by their own namespace, folder or name: `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Attributes2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`), `Locator2Impl` (src/net/JNet/Generated/Org/Xml/Sax/Ext/Locator2Impl.cs:32, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32
- 12 public types in `Org.Xml.Sax.Helpers` are marked as implementation by their own namespace, folder or name: `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributeListImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `AttributesImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributesImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), `LocatorImpl` (src/net/JNet/Generated/Org/Xml/Sax/Helpers/LocatorImpl.cs:32, name ends in `Impl`), and 4 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- `Java.Util.Function.BiConsumerDirect` (src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- `Java.Util.Function.BiFunctionDirect` (src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- `Java.Util.Function.BinaryOperatorDirect` (src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:56) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- `Java.Util.Function.FunctionDirect` (src/net/JNet/Developed/Java/Util/Function/Function.cs:152) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- `Java.Util.Function.PredicateDirect` (src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net10.0)`, `JNetPSCore(net10.0)`, `jnetAWTApp(net10.0)`, `jnetApp(net10.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
- `Java.Util.Function.SupplierDirect` (src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net11.0)`, `JNetPSCore(net11.0)`, `jnetAWTApp(net11.0)`, `jnetApp(net11.0)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Developed/Java/Util/Function/Supplier.cs:129
- `Java.Awt.EventNs.ActionListenerDirect` (src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:103) is public, and the library's own code uses it, but no other project in this repository uses it (read: `JNetCLICore(net462)`, `JNetPSCore(net462)`, `jnetAWTApp(net462)`, `jnetApp(net462)`) and no public member of the library exposes it. Consumers outside this repository are not visible here; if they rely on it, it is API and should be documented as such. — src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:103
What to do
- Hide `Java.Net` (`DatagramSocketImpl`, `DatagramSocketImpl`, `DatagramSocketImpl`, `SocketImpl`, `SocketImpl`, `SocketImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Imageio.Metadata` (`IIOMetadataFormatImpl`, `IIOMetadataFormatImpl`, `IIOMetadataFormatImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Imageio.Stream` (`ImageInputStreamImpl`, `ImageInputStreamImpl`, `ImageInputStreamImpl`, `ImageOutputStreamImpl`, `ImageOutputStreamImpl`, `ImageOutputStreamImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Management.Remote.Rmi` (`RMIConnectionImpl`, `RMIConnectionImpl`, `RMIConnectionImpl`, `RMIIIOPServerImpl`, `RMIIIOPServerImpl`, `RMIIIOPServerImpl`, `RMIJRMPServerImpl`, `RMIJRMPServerImpl`, and 4 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Sql.Rowset` (`RowSetMetaDataImpl`, `RowSetMetaDataImpl`, `RowSetMetaDataImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Sql.Rowset.Serial` (`SQLInputImpl`, `SQLInputImpl`, `SQLInputImpl`, `SQLOutputImpl`, `SQLOutputImpl`, `SQLOutputImpl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Javax.Xml.Bind.Helpers` (`AbstractMarshallerImpl`, `AbstractMarshallerImpl`, `AbstractMarshallerImpl`, `AbstractUnmarshallerImpl`, `AbstractUnmarshallerImpl`, `AbstractUnmarshallerImpl`, `NotIdentifiableEventImpl`, `NotIdentifiableEventImpl`, and 13 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Org.Xml.Sax.Ext` (`Attributes2Impl`, `Attributes2Impl`, `Attributes2Impl`, `Locator2Impl`, `Locator2Impl`, `Locator2Impl`) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `Org.Xml.Sax.Helpers` (`AttributeListImpl`, `AttributeListImpl`, `AttributeListImpl`, `AttributesImpl`, `AttributesImpl`, `AttributesImpl`, `LocatorImpl`, `LocatorImpl`, and 4 more) (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiConsumerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BiFunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.BinaryOperatorDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.FunctionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.PredicateDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Function.SupplierDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ActionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.AdjustmentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ComponentListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ContainerListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.FocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyBoundsListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.HierarchyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.InputMethodListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.ItemListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.KeyListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseMotionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.MouseWheelListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.TextListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowFocusListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Awt.EventNs.WindowStateListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Beans.PropertyChangeListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Lang.InterruptedException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CallableDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.CancellationException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Java.Util.Concurrent.ExecutionException` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.Soap.SOAPBinding` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Jws.WebParam` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Naming.Spi.DirStateFactory` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.ActionDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `Javax.Swing.Event.ListSelectionListenerDirect` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetAsyncEnumerator` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.Specific.JNetEventData` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.PowerShell.JNetPSHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
- Make `MASES.JNet.PowerShell.JNetPSHelper` internal (C#: `internal`, with `[InternalsVisibleTo]` for the sibling assemblies and tests that need them): only the library itself uses it and nothing on its public API exposes it, so hiding it costs consumers nothing and lets it change freely.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF1 · Benchmark discipline
PF3 · Async & latency hygiene
- Only 0/8 awaits in library code use ConfigureAwait(false). A library that captures the caller's context can stall or deadlock its host — the classic way a dependency drags an app down.
- `await Task<object>.Run(() => { try { token.ThrowIfCancellationRequested(); object r...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. (×2) — src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:36, src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:35
- `await Task<T>.Run(() => { try { token.ThrowIfCancellationRequested(); T _result = t...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:93
- `await Task<V>.Run(() => { try { token.ThrowIfCancellationRequested(); V result = th...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:73
- `await CSharpScript.RunAsync(codeToEval, options)` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:65
- `await state.ContinueWithAsync(codeToEval, options, (o) => { if (o is CompilationErr...` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:69
- `await script.RunAsync()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:108
- `await main.Start()` resumes on the caller's captured context. In library code that context belongs to the host application, so a host that blocks on this call (or runs on a UI thread) can stall or deadlock — append `.ConfigureAwait(false)`. — src/net/JNetCLICore/ProgramBase.cs:151
What to do
- In library code, append .ConfigureAwait(false) to every await (or set <ConfigureAwait>false</ConfigureAwait> / use the analyzer CA2007) so the library never captures the host's context.
X20 · Mistyped argument guard
X5 · Nullable reference types
- 0/22 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
- This method contradicts itself about `types`: line 921 writes `types?.ApplyGenerics`, which says `types` can be null, but line 906 then dereferences it directly as `types.Add` with no null test between them and no guard around it. If the `?.` is right, that dereference throws NullReferenceException on the input it was written for; if `types` truly cannot be null here, the `?.` is misleading. Settle it one way — test `types` once before the first use and handle the null case, or drop the `?.` — rather than leaving the two readings side by side. — src/net/JNetReflector/InternalExtensions.cs:906
- This method contradicts itself about `jClass`: line 156 tests it for null before doing anything with it — the author's own statement that null is an input this code expects — but that `if` scopes only the block beneath it, and line 157 then dereferences `jClass` as `jClass.Classes` AFTER the block has closed, where the guard no longer applies. A null `jClass` skips the guarded body and reaches that line anyway, throwing NullReferenceException on exactly the input the guard was written for. If the dereference belongs to the guarded work, move it inside the block; if `jClass` truly cannot be null by then, the guard above is misleading and should go. — src/net/JNetReflector/InternalMethods.cs:157
- This method contradicts itself about `attribute`: line 252 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 253 then dereferences it directly as `attribute.NounName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/net/JNetPSCore/JNetPSHelper.cs:253
- This method contradicts itself about `attribute`: line 273 assigns it with `as CmdletAttribute`, which hands back null rather than throwing when the value is not a `CmdletAttribute`, but line 274 then dereferences it directly as `attribute.VerbName` with no null test between them and no guard around it. If the `as` is right, that dereference throws NullReferenceException on the input it was written for — and the NullReferenceException names neither the cast nor the type that failed. Settle it one way — test `attribute` once before the first use and handle the null case, or cast with `(CmdletAttribute)` so the failure is reported where it happens — rather than leaving the two readings side by side. — src/net/JNetPSCore/JNetPSHelper.cs:274
- 0/6 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
- Where a method uses `?.` on a symbol and then dereferences it directly, settle the question once: test it before the first use and handle null, or drop the `?.`.
- Where a method null-tests a symbol and then uses it after the guarded block closes, move the trailing work inside the block — the guard skips its body on null, it does not stop the method.
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 56.4 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 70.7 | Adequate — gated by AX2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 46.8 | Weak — gated by M2, M4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 71.0 | Strong | Solid. |
| Security | 53.4 | Adequate — gated by C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 77.1 | Strong | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (IAuditable, an immutable audit log, an EF SaveChanges interceptor) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — docker build failed (exit 1) — ------ REDACTED:6 -------------------- 4 | 5 | # Copy everything 6 | >>> COPY ./src/net ./ 7 | ENV JNET_DOCKER_BUILD_ACTIONS=true 8 | # Restore as distinct layers -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref fd3becf8-094b-49ee-aa4d-29727f62c9ff::rzeo7v7n9nzkiyla4o801krp8: "net": not found; likely cause (the repository): a file the Dockerfile copies (`src/net`) is not in the repository's build context (it may be produced by a build step outside the Dockerfile, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the Dockerfile copies (`src/net`) is not in the repository's build context (it may be produced by a build step outside the Dockerfile, or excluded by .dockerignore). Nothing here says the surface is inaccessible, only that it was never rendered.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- D10 Test Quality — ~3370 lines of test source are present (.java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .java, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — Naming Consistency not included (check did not complete)
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — Cross-context type coupling could not be assessed — this codebase's bounded contexts are neither declared nor inferable.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — too few calls resolved to assess navigability
- D28 Secrets (history) — gitleaks killed before it finished — this repository's working tree not scanned
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (27 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
- ED1 Event-Driven — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 33 event handler(s); 42 CQRS handler(s)
- ED5 Idempotency — 63 mutating command handler(s)/consumer(s) detected and 81 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — X1 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X12 Unreachable branch — X12 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — X13 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — X18 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — X2 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — X28 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X29 Per-element action decided by a fixed element — X29 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X3 Exception handling — X3 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — X30 reached only 26% of this repository's production lines — javascript (17,109 lines), java (13,903 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 24 finding(s)
- Namespace dependency cycle src/net/JNet/Generated/Java/Awt/Color.cs:32
- Namespace dependency cycle src/net/JNet/Generated/Javax/Management/MBeanServer.cs:66
- Namespace dependency cycle src/net/JNet/Generated/Javax/Lang/Model/Type/DeclaredType.cs:32
- Namespace dependency cycle src/net/JNet/Generated/Javax/Imageio/Spi/ImageReaderWriterSpi.cs:32
- Namespace dependency cycle src/net/JNet/Generated/Javax/Sql/Rowset/CachedRowSet.cs:32
- Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Stream/XMLEventWriter.cs:66
- Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Crypto/KeySelector.cs:32
- Namespace dependency cycle src/net/JNet/Generated/Javax/Xml/Ws/Handler/LogicalMessageContext.cs:66
- AnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:4
- AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:4
- AnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:5
- AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:8
- AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:5
- AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:6
- AnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:7
- EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:217
- EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:220
- EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:274
- EmptyCatchBlock src/net/JNetReflector/JNetReflectorHelper.cs:277
- BlanketAnalyzerSeverityNone src/net/JNet/Developed/.editorconfig:3
- BlanketAnalyzerSeverityNone src/net/JNet/Generated/.editorconfig:3
- REDACTED
- NoWarnInCsproj src/net/Common/Common.props:21
- REDACTED
Serious — 176 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NuGet dependencies are not locked src/net/Directory.Build.targets:11
- NuGet dependencies are not locked src/net/JNet/JNet.csproj:52
- NuGet dependencies are not locked src/net/JNetCLICore/JNetCLICore.csproj:24
- NuGet dependencies are not locked src/net/JNetPS/JNetPS.csproj:32
- NuGet dependencies are not locked src/net/JNetPSCore/JNetPSCore.csproj:21
- NuGet dependencies are not locked src/net/JNetReflector/JNetReflector.csproj:119
- NuGet dependencies are not locked src/net/templates/templates/jnetAWTApp/jnetAWTApp.csproj:17
- NuGet dependencies are not locked src/net/templates/templates/jnetApp/jnetApp.csproj:17
- NuGet dependencies are not locked tests/net/JNetBenchmarksTest/JNetBenchmarksTest.csproj:12
- NuGet dependencies are not locked tests/net/JNetTest/JNetTest.csproj:14
- Awaits without ConfigureAwait(false)
- Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:36
- Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/CompletableFuture.cs:93
- Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:35
- Awaits without ConfigureAwait(false) src/net/JNet/Developed/Java/Util/Concurrent/Future.cs:73
- Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:65
- Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:69
- Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:108
- Awaits without ConfigureAwait(false) src/net/JNetCLICore/ProgramBase.cs:151
- Process-global static state: JNetCLICoreHelper src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:32
- Process-global static state: JNetReflectorExtensions src/net/JNetReflector/InternalExtensions.cs:38
- Process-global static state: ReflectionUtils src/net/JNetReflector/InternalMethods.cs:36
- Process-global static state: JNetReflectorCore src/net/JNetReflector/JNetReflectorCore.cs:34
- Process-global static state: JNetReflectorCore src/net/JNetReflector/JNetReflectorCore.cs:905
- Process-global static state: JNetPSHelperExtensions src/net/JNetPSCore/JNetPSHelper.cs:37
- MethodTooLong: ReflectionUtils.AnalyzeMethods src/net/JNetReflector/InternalMethods.cs:1303
- MethodTooLong: ReflectionUtils.PrepareSingleClass src/net/JNetReflector/InternalMethods.cs:672
- MethodTooLong: JNetReflectorCore.ProcessCommandLine src/net/JNetReflector/JNetReflectorCore.cs:603
- MethodTooLong: ReflectionUtils.AnalyzeJavaMethods src/net/JNetReflector/InternalMethods.cs:2222
- MethodTooLong: ReflectionUtils.AnalyzeConstructors src/net/JNetReflector/InternalMethods.cs:931
- MethodTooLong: JNetReflectorExtensions.ToNetType src/net/JNetReflector/InternalExtensions.cs:2042
- Dead code: IAsyncEnumerator<TObject>.Current src/net/JNet/Specific/AsyncEnumerable.cs:72
- Dead code: LocalBridgeClazz src/net/JNet/Specific/JNetEventResult.cs:40
- Dead code: InternalConst src/net/JNetCLI/InternalConst.cs:21
- Dead code: GetRelativePath src/net/JNetReflector/InternalConst.cs:259
- Dead code: InternalConst src/net/JNetCLICore/InternalConst.cs:21
- DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2172
- DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2571
- DeadPreprocessorBranch src/net/JNetReflector/InternalExtensions.cs:2593
- DeadPreprocessorBranch src/net/JNetReflector/JNetReflectorHelper.cs:136
- Duplicated block (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:1197
- Duplicated block (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:367
- Duplicated block (7 lines × 2) src/net/JNetReflector/InternalMethods.cs:1847
- Duplicated block (7 lines × 2) src/net/JNetReflector/JNetReflectorHelper.cs:109
- Duplicated block (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:1868
- Duplicated block (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2069
- Duplicated block (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2172
- Duplicated block (6 lines × 2) src/net/JNetReflector/InternalMethods.cs:2303
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (15 lines × 2) src/net/JNetReflector/InternalExtensions.cs:2296
- Duplicated block (15 lines × 2) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAndCmdletCommand.cs:29
- Duplicated block (15 lines × 2) src/net/JNetReflector/InternalMethods.cs:428
- Duplicated block (11 lines × 2) src/net/JNetReflector/InternalExtensions.cs:984
- Duplicated block (11 lines × 2) src/net/JNetReflector/InternalMethods.cs:1696
- Duplicated block (11 lines × 2) src/net/JNetReflector/InternalMethods.cs:2040
- Duplicated block (8 lines × 2) src/net/JNetReflector/InternalMethods.cs:1363
- Duplicated block (8 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1494
- Duplicated block (8 lines × 2) src/net/JNetReflector/InternalMethods.cs:1512
- Duplicated block (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:1685
- Duplicated block (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:1022
- Duplicated block (5 lines × 2) src/net/JNetReflector/InternalMethods.cs:2438
- Symbol treated as nullable, then dereferenced unguarded src/net/JNetReflector/InternalExtensions.cs:906
- Symbol treated as nullable, then dereferenced unguarded src/net/JNetPSCore/JNetPSHelper.cs:253
- Symbol treated as nullable, then dereferenced unguarded src/net/JNetPSCore/JNetPSHelper.cs:274
- CommentedOutCode src/net/JNetReflector/InternalExtensions.cs:931
- CommentedOutCode src/net/JNetReflector/InternalExtensions.cs:1917
- FileTooLong: JNetReflector/InternalMethods.cs src/net/JNetReflector/InternalMethods.cs
- FileTooLong: JNetReflector/JNetReflectorCore.cs src/net/JNetReflector/JNetReflectorCore.cs
- REDACTED
- REDACTED
- Duplicated block (12 lines × 2) src/net/JNetReflector/InternalMethods.cs:1855
- Duplicated block (12 lines × 2) src/net/JNetReflector/InternalExtensions.cs:2269
- Duplicated block (10 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1461
- Duplicated block (10 lines × 2) src/net/JNetReflector/InternalMethods.cs:1085
- ReflectionUtils.AnalyzeMethods (cyclomatic 253) src/net/JNetReflector/InternalMethods.cs:1303
- JNetReflectorCore.ProcessCommandLine (cyclomatic 74) src/net/JNetReflector/JNetReflectorCore.cs:603
- ReflectionUtils.AnalyzeJavaMethods (cyclomatic 70) src/net/JNetReflector/InternalMethods.cs:2222
- JNetReflectorExtensions.ToNetType (cyclomatic 67) src/net/JNetReflector/InternalExtensions.cs:2042
- ReflectionUtils.AnalyzeConstructors (cyclomatic 53) src/net/JNetReflector/InternalMethods.cs:931
- ReflectionUtils.PrepareSingleClass (cyclomatic 52) src/net/JNetReflector/InternalMethods.cs:672
- JNetReflectorExtensions.JVMBaseClassName (cyclomatic 48) src/net/JNetReflector/InternalExtensions.cs:1424
- JNetReflectorExtensions.GetGenerics (cyclomatic 47) src/net/JNetReflector/InternalExtensions.cs:964
- ReflectionUtils.PrefilterMethods (cyclomatic 34) src/net/JNetReflector/InternalMethods.cs:1224
- JNetReflectorExtensions.NeedsOperators (cyclomatic 29) src/net/JNetReflector/InternalExtensions.cs:1309
- ReflectionUtils.AnalyzeClasses (cyclomatic 28) src/net/JNetReflector/InternalMethods.cs:397
- ReflectionUtils.AnalyzeNestedClasses (cyclomatic 28) src/net/JNetReflector/InternalMethods.cs:551
- JNetReflectorHelper.ExtractJavaInfo (cyclomatic 28) src/net/JNetReflector/JNetReflectorHelper.cs:76
- JNetReflectorExtensions.HasJVMBaseClassName (cyclomatic 26) src/net/JNetReflector/InternalExtensions.cs:1370
- ReflectionUtils.AnalyzeFields (cyclomatic 25) src/net/JNetReflector/InternalMethods.cs:2472
- ParserAdapter.ListenerShallManageEventHandlers (cyclomatic 23) src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:235
- JNetCLICoreHelper.ProcessCLIParsedArgs (cyclomatic 21) src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:346
- ProgramBase.Start (cyclomatic 20) src/net/JNetCLICore/ProgramBase.cs:49
- XMLReaderAdapter.ListenerShallManageEventHandlers (cyclomatic 19) src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs:227
- JNetHelper.listFromPrimitiveArray (cyclomatic 19) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:33
- JNetReflectorExtensions.PropertyName (cyclomatic 18) src/net/JNetReflector/InternalExtensions.cs:2468
- JNetReflectorExtensions.Type (cyclomatic 17) src/net/JNetReflector/InternalExtensions.cs:615
- ReflectionUtils.AnalyzeOperators (cyclomatic 17) src/net/JNetReflector/InternalMethods.cs:1141
- ReflectionUtils.AnalyzeMethods (cognitive 671) src/net/JNetReflector/InternalMethods.cs:1303
- JNetReflectorExtensions.GetGenerics (cognitive 168) src/net/JNetReflector/InternalExtensions.cs:964
- ReflectionUtils.AnalyzeJavaMethods (cognitive 151) src/net/JNetReflector/InternalMethods.cs:2222
- JNetReflectorCore.ProcessCommandLine (cognitive 128) src/net/JNetReflector/JNetReflectorCore.cs:603
- ReflectionUtils.AnalyzeConstructors (cognitive 123) src/net/JNetReflector/InternalMethods.cs:931
- ReflectionUtils.PrepareSingleClass (cognitive 94) src/net/JNetReflector/InternalMethods.cs:672
- JNetReflectorExtensions.ToNetType (cognitive 82) src/net/JNetReflector/InternalExtensions.cs:2042
- JNetReflectorHelper.ExtractJavaInfo (cognitive 66) src/net/JNetReflector/JNetReflectorHelper.cs:76
- ReflectionUtils.AnalyzeNestedClasses (cognitive 65) src/net/JNetReflector/InternalMethods.cs:551
- JNetReflectorExtensions.JVMBaseClassName (cognitive 64) src/net/JNetReflector/InternalExtensions.cs:1424
- ReflectionUtils.AnalyzeFields (cognitive 48) src/net/JNetReflector/InternalMethods.cs:2472
- ReflectionUtils.AnalyzeClasses (cognitive 42) src/net/JNetReflector/InternalMethods.cs:397
- JNetReflectorExtensions.Type (cognitive 40) src/net/JNetReflector/InternalExtensions.cs:615
- ReflectionUtils.PrefilterMethods (cognitive 39) src/net/JNetReflector/InternalMethods.cs:1224
- ProgramBase.Start (cognitive 37) src/net/JNetCLICore/ProgramBase.cs:49
- ReflectionUtils.AnalyzeOperators (cognitive 36) src/net/JNetReflector/InternalMethods.cs:1141
- JNetCLICoreHelper.ProcessCLIParsedArgs (cognitive 32) src/net/JNet/Specific/CLI/JNetCLICoreHelper.cs:346
- JNetReflectorExtensions.WhereClauses (cognitive 28) src/net/JNetReflector/InternalExtensions.cs:1250
- JNetPSHelperExtensions.InvokeExternal (cognitive 28) src/net/JNetPSCore/JNetPSHelper.cs:65
- JNetReflectorExtensions.JVMGenericInterfaces (cognitive 27) src/net/JNetReflector/InternalExtensions.cs:1586
- JNetHelper.listFromPrimitiveArray (cognitive 26) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:33
- JNetCoreBase.Launch (cognitive 25) src/net/JNet/JNetCoreBase.cs:440
- JNetReflectorExtensions.GetGenerics (cognitive 25) src/net/JNetReflector/InternalExtensions.cs:458
- JNetReflectorExtensions.NeedsOperators (cognitive 24) src/net/JNetReflector/InternalExtensions.cs:1309
- JNetReflectorExtensions.JavadocUrl (cognitive 23) src/net/JNetReflector/InternalExtensions.cs:2263
- ParserAdapter.ListenerShallManageEventHandlers (cognitive 22) src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:235
- JNetReflectorExtensions.HasJVMBaseClassName (cognitive 21) src/net/JNetReflector/InternalExtensions.cs:1370
- JNetReflectorExtensions.JavadocUrl (cognitive 19) src/net/JNetReflector/InternalExtensions.cs:2629
- XMLReaderAdapter.ListenerShallManageEventHandlers (cognitive 18) src/net/JNet/Generated/Org/Xml/Sax/Helpers/XMLReaderAdapter.cs:227
- JNetHelper.ListFrom (cognitive 18) src/net/JNet/Specific/JNetHelper.cs:92
- JNetReflectorExtensions.GetGenerics (cognitive 18) src/net/JNetReflector/InternalExtensions.cs:850
- JNetReflectorExtensions.GetGenerics (cognitive 17) src/net/JNetReflector/InternalExtensions.cs:877
- JNetReflectorExtensions.JVMInterfaces (cognitive 17) src/net/JNetReflector/InternalExtensions.cs:1553
- JNetReflectorHelper.ExtractJavaInfo (cognitive 17) src/net/JNetReflector/JNetReflectorHelper.cs:225
- JNetReflectorExtensions.TypeNameMustBeAvoided (cognitive 16) src/net/JNetReflector/InternalExtensions.cs:553
- ClassTooLong: ReflectionUtils src/net/JNetReflector/InternalMethods.cs
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (45 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:2264
- Edited copy of a member (52 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:1310
- Edited copy of a member (25 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:459
- Edited copy of a member (31 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:1554
- Edited copy of a member (28 corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264
- Edited copy of a member (7 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:541
- Edited copies of one member (7 members, 11+ corresponding lines) src/jvm/jnet/src/main/java/org/mases/jnet/developed/JNetHelper.java:98
- Edited copy of a member (15 corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:305
- Edited copies of one member (3 members, 15+ corresponding lines) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:264
- Edited copy of a member (10 corresponding lines) src/net/JNetReflector/InternalExtensions.cs:2374
- Duplicated block (37 lines × 2) src/net/JNetPS/Cmdlet/JMX/AddNotificationListenerCmdletCommand.cs:30
- Duplicated block (20 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1015
- Duplicated block (33 lines × 2) src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:31
- Duplicated block (24 lines × 2) src/net/JNetReflector/InternalMethods.cs:599
- Duplicated block (19 lines × 2) src/net/JNetReflector/InternalExtensions.cs:1560
- Duplicated block (18 lines × 2) src/net/JNetReflector/Program.cs:52
- Duplicated block (15 lines × 5) src/net/JNetPS/Cmdlet/JMX/InvokeQueryEqCmdletCommand.cs:29
- Duplicated block (15 lines × 3) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29
- Duplicated block (13 lines × 4) src/net/JNetPS/Cmdlet/JMX/InvokeQueryAnySubStringCmdletCommand.cs:29
- Duplicated block (11–16 lines × 3) src/net/JNet/Specific/Extensions/JavaUtilExtensions.cs:276
- Duplicated block (9 lines × 2) src/net/JNet/JNetCoreBase.cs:315
- Duplicated block (8 lines × 3) src/net/JNetReflector/InternalExtensions.cs:1319
- Duplicated block (9–10 lines × 2) src/net/JNetReflector/InternalMethods.cs:1911
- Duplicated block (6 lines × 4) src/net/JNetReflector/InternalMethods.cs:2069
- Duplicated block (4–5 lines × 5) src/net/JNetReflector/InternalMethods.cs:2028
- Duplicated block (27 lines × 2) src/net/JNetPS/Cmdlet/JMX/NewMBeanProxyCmdletCommand.cs:68
- Off the main sequence: JNet(net462) src/net/JNet/JNet.csproj:1
- Null guard scopes only part of the work it protects src/net/JNetReflector/InternalMethods.cs:157
Minor — 141 finding(s)
- Fat interface: IInputMethod (16 members) src/net/JNet/Generated/Java/Awt/Im/Spi/InputMethod.cs:66
- Fat interface: IRenderedImage (21 members) src/net/JNet/Generated/Java/Awt/ImageNs/RenderedImage.cs:66
- Fat interface: IMemoryPoolMXBean (16 members) src/net/JNet/Generated/Java/Lang/Management/MemoryPoolMXBean.cs:66
- Fat interface: IRuntimeMXBean (16 members) src/net/JNet/Generated/Java/Lang/Management/RuntimeMXBean.cs:66
- Fat interface: IThreadMXBean (27 members) src/net/JNet/Generated/Java/Lang/Management/ThreadMXBean.cs:66
- Fat interface: IPath (27 members) src/net/JNet/Generated/Java/Nio/File/Path.cs:66
- Fat interface: IChronoLocalDate (25 members) src/net/JNet/Generated/Java/Time/Chrono/ChronoLocalDate.cs:66
- Fat interface: IChronology (24 members) src/net/JNet/Generated/Java/Time/Chrono/Chronology.cs:66
- Fat interface: ICollection<E> (17 members) src/net/JNet/Generated/Java/Util/Collection.cs:276
- Fat interface: IDeque<E> (27 members) src/net/JNet/Generated/Java/Util/Deque.cs:354
- Fat interface: IList<E> (26 members) src/net/JNet/Generated/Java/Util/List.cs:359
- Fat interface: IMap<K, V> (23 members) src/net/JNet/Generated/Java/Util/Map.cs:594
- Fat interface: INavigableMap<K, V> (21 members) src/net/JNet/Generated/Java/Util/NavigableMap.cs:321
- Fat interface: IBlockingDeque<E> (29 members) src/net/JNet/Generated/Java/Util/Concurrent/BlockingDeque.cs:407
- Fat interface: ICompletionStage<T> (38 members) src/net/JNet/Generated/Java/Util/Concurrent/CompletionStage.cs:503
- Fat interface: IDoubleStream (33 members) src/net/JNet/Generated/Java/Util/Stream/DoubleStream.cs:66
- Fat interface: IIntStream (35 members) src/net/JNet/Generated/Java/Util/Stream/IntStream.cs:66
- Fat interface: ILongStream (34 members) src/net/JNet/Generated/Java/Util/Stream/LongStream.cs:66
- Fat interface: IStream<T> (32 members) src/net/JNet/Generated/Java/Util/Stream/Stream.cs:472
- Fat interface: ICallableStatement (121 members) src/net/JNet/Generated/Java/Sql/CallableStatement.cs:66
- Fat interface: IConnection (45 members) src/net/JNet/Generated/Java/Sql/Connection.cs:66
- Fat interface: IDatabaseMetaData (176 members) src/net/JNet/Generated/Java/Sql/DatabaseMetaData.cs:66
- Fat interface: IPreparedStatement (58 members) src/net/JNet/Generated/Java/Sql/PreparedStatement.cs:66
- Fat interface: IResultSet (191 members) src/net/JNet/Generated/Java/Sql/ResultSet.cs:66
- Fat interface: IResultSetMetaData (21 members) src/net/JNet/Generated/Java/Sql/ResultSetMetaData.cs:66
- Duplicated predicate src/net/JNetReflector/InternalExtensions.cs:1908
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ActionListener.cs:223
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs:210
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/HierarchyBoundsAdapter.cs:252
- Duplicated predicate src/net/JNet/Generated/Javax/Print/Event/PrintJobAttributeListener.cs:223
- Duplicated predicate src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:604
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs:210
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:216
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:258
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ContainerAdapter.cs:252
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:300
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/ComponentAdapter.cs:342
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:222
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:264
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:306
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:348
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:390
- Duplicated predicate src/net/JNet/Generated/Java/Awt/Dnd/DragSourceAdapter.cs:432
- Duplicated predicate src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:649
- Duplicated predicate src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:691
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs:210
- Duplicated predicate src/net/JNet/Generated/Java/Awt/EventNs/FocusAdapter.cs:252
- Duplicated predicate src/net/JNet/Generated/Org/Xml/Sax/Helpers/ParserAdapter.cs:734
- Duplicated predicate src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs:293
- Duplicated predicate src/net/JNet/Generated/Javax/Imageio/Event/IIOReadProgressListener.cs:335
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiConsumer.cs:138
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BiFunction.cs:58
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:57
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/BinaryOperator.cs:150
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:56
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Function.cs:152
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Predicate.cs:149
- Public type used only inside its own library src/net/JNet/Developed/Java/Util/Function/Supplier.cs:54
- Implementation type on the public API src/net/JNet/Generated/Java/Net/DatagramSocketImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Imageio/Metadata/IIOMetadataFormatImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Imageio/Stream/ImageInputStreamImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Management/Remote/Rmi/RMIConnectionImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Sql/Rowset/RowSetMetaDataImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Sql/Rowset/Serial/SQLInputImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Javax/Xml/Bind/Helpers/AbstractMarshallerImpl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Org/Xml/Sax/Ext/Attributes2Impl.cs:32
- Implementation type on the public API src/net/JNet/Generated/Org/Xml/Sax/Helpers/AttributeListImpl.cs:32
- README/code drift CONTRIBUTING.md:48
- README/code drift README.md:120
- README/code drift README.md:138
- README/code drift src/documentation/articles/performance.md:30
- README/code drift src/documentation/articles/support.md:17
- README/code drift src/documentation/articles/usage.md:66
- README/code drift src/documentation/articles/usageCLI.md:12
- Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:353
- Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:448
- Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:1364
- Silent fallback default in catch src/net/JNetReflector/InternalExtensions.cs:1418
- Silent fallback default in catch src/net/JNetReflector/JNetReflectorHelper.cs:274
- Partial data-retention evidence
- Partial data-subject-rights support
- No ADRs found src/net/JNetCLI/JNetCLI.csproj:5
- Projects may be oversized for their cohesion src/net/JNet/JNet.csproj:1
- REDACTED
- No ADRs
- No changelog
- Java packages are not null-marked everywhere
- Nullable reference types not enabled everywhere
Minor — 3 finding(s)
- doc comments repeat the names src/net/JNet/Developed/Java/Awt/Container.cs:29
- doc comments repeat the names src/net/JNetCLICore/ProgramBase.cs:195
- doc comments repeat the names src/net/JNetPSCore/Cmdlet/StartJNetPSCmdletCommandBase.cs:236
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d63d0aaa08714ee8b0a6a71468a3021d/tree.json --exit-code 0 --source . | 0 | — |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/awt/dnd --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/awt/event --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/java/util/function --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/imageio --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/print --exclude src/jvm/jnet/src/main/java/org/mases/jnet/generated/javax/swing/event --exclude src/net/JNet/Developed/Java --exclude src/net/JNet/Developed/Javax --exclude src/net/JNet/Generated/Java --exclude src/net/JNet/Generated/Javax --exclude src/net/JNet/Generated/Org . | 0 | — |
| D30 · Dependency Vulnerabilities | nuget | — | nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan | 0 | — |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-492a043998d149f293d9ffa2011e9b2d | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-492a043998d149f293d9ffa2011e9b2d | 0 | artifacts/raw/osv-scanner.json |
Appendix C — Personal-data map
Name — 1 field(s)
- GraphicsEnvironment.AvailableFontFamilyNames src/net/JNet/Generated/Java/Awt/GraphicsEnvironment.cs:107