Executive summary
mybatis/mybatis-3 falls short of our standard for production because we found no recorded design decisions and no architecture document or diagram. It scores 64 out of 100 and is rated Adequate, and three of its 11 critical findings are security problems in its automatic dependency updates and in its code.
Maturity, at 57, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 6 points. Adding build and run instructions to the README comes next, worth about 4 points. Raising Maturity to 70 would lift the score to about 69.
One automatic update takes new releases before a bad one can be spotted. One place turns outside data straight into objects, which an attacker could use, and one weakness in the code could be used by an attacker. Setting a waiting period for automatic updates, reading outside data into plain values and fixing the weaknesses the scanner points to would close these risks. The six tests that check nothing need to check the result they produce.
The product code is 35,358 lines, about €140,000 to rebuild.
If Maturity rose from 57 to 70, the lowest score rated Strong, the score would rise from 64 to about 69.
New since the last survey: 44 findings
- Code Duplication · Edited copy of a member (34 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BaseWrapper.java
- Code Duplication · Edited copies of one member (3 members, 30+ corresponding lines) src/main/java/org/apache/ibatis/reflection/ArrayUtil.java
- Code Duplication · Edited copy of a member (40 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java
- Code Duplication · Edited copy of a member (21 corresponding lines) src/main/java/org/apache/ibatis/logging/jdbc/ConnectionLogger.java
- Code Duplication · Edited copy of a member (26 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java
- Code Duplication · Edited copy of a member (22 corresponding lines) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java
- Code Duplication · Edited copy of a member (16 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/type/TypeAliasRegistry.java
- Code Duplication · Edited copy of a member (15 corresponding lines) src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSessionFactory.java
- Code Duplication · Edited copy of a member (16 corresponding lines) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java
- Code Duplication · Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/reflection/Reflector.java
- Code Duplication · Edited copy of a member (14 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BeanWrapper.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/executor/BatchExecutor.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/binding/MapperMethod.java
- Code Duplication · Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSession.java
- Code Duplication · Edited copy of a member (10 corresponding lines) src/main/java/org/apache/ibatis/logging/jdbc/ResultSetLogger.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/reflection/MetaClass.java
- Code Duplication · Edited copy of a member (14 corresponding lines) src/main/java/org/apache/ibatis/builder/xml/XMLMapperBuilder.java
- Code Duplication · Edited copy of a member (7 corresponding lines) src/main/java/org/apache/ibatis/reflection/Reflector.java
- Code Duplication · Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/executor/SimpleExecutor.java
- Code Duplication · Edited copies of one member (6 members, 11+ corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BeanWrapper.java
- Code Duplication · Edited copy of a member (10 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java
- Code Duplication · Edited copy of a member (19 corresponding lines) src/main/java/org/apache/ibatis/io/ClassLoaderWrapper.java
- Code Duplication · Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/builder/ParameterExpression.java
- Code Duplication · Edited copy of a member (8 corresponding lines) src/main/java/org/apache/ibatis/scripting/xmltags/ForEachSqlNode.java
- Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java
- Code Duplication · Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/executor/statement/CallableStatementHandler.java
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/main/java/org/apache/ibatis/session/Configuration.java
- Code Duplication · Edited copies of one member (4 members, 9+ corresponding lines) src/main/java/org/apache/ibatis/builder/xml/XMLConfigBuilder.java
- Code Duplication · Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java
- Code Duplication · Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/executor/SimpleExecutor.java
- Code Duplication · Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java
- Code Duplication · Edited copy of a member (7 corresponding lines) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java
- Code Duplication · Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/binding/MapperMethod.java
- Code Duplication · Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java
- Code Duplication · Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java
- Code Duplication · Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java
- Code Duplication · Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java
- License Compliance · Banned license: com.mysql:mysql-connector-j
- Churn × Complexity Hotspots · Hotspot: src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Rebuild cost: about €140,000 · Estimate
| Cost to rebuild | €46,000 to €230,000, for 760 to 2,411 hours of work, about 0.9 person-years for 1 to 2 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.9 at a score of 64. 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: 35,358 lines of product code |
| 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: which parts of the code depend on which
| uses → | 1 cursor | 2 exceptions | 3 executor.parameter | 4 reflection.factory | 5 reflection.property | 6 datasource | 7 logging | 8 parsing | 9 reflection.wrapper | 10 transaction | 11 cache.decorators | 12 executor.loader.cglib | 13 executor.loader.javassist | 14 executor.result | 15 io | 16 scripting | 17 cache | 18 cache.impl | 19 executor.loader | 20 executor.resultset | 21 executor.statement | 22 executor | 23 type | 24 builder | 25 builder.annotation | 26 builder.xml | 27 session | 28 reflection | 29 transaction.jdbc | 30 transaction.managed | 31 binding | 32 datasource.unpooled | 33 datasource.pooled | 34 executor.keygen | 35 mapping | 36 annotations | 37 cursor.defaults | 38 scripting.xmltags | 39 session.defaults | 40 scripting.defaults |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 cursor | ||||||||||||||||||||||||||||||||||||||||
| 2 exceptions | ||||||||||||||||||||||||||||||||||||||||
| 3 executor.parameter | ||||||||||||||||||||||||||||||||||||||||
| 4 reflection.factory | ||||||||||||||||||||||||||||||||||||||||
| 5 reflection.property | ||||||||||||||||||||||||||||||||||||||||
| 6 datasource | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 logging | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 parsing | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 reflection.wrapper | 4 | 5 | 8 | |||||||||||||||||||||||||||||||||||||
| 10 transaction | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 cache.decorators | 2 | 10 | ||||||||||||||||||||||||||||||||||||||
| 12 executor.loader.cglib | 4 | 1 | 9 | 2 | ||||||||||||||||||||||||||||||||||||
| 13 executor.loader.javassist | 4 | 1 | 9 | 2 | ||||||||||||||||||||||||||||||||||||
| 14 executor.result | 1 | 2 | 1 | 5 | 1 | |||||||||||||||||||||||||||||||||||
| 15 io | 5 | |||||||||||||||||||||||||||||||||||||||
| 16 scripting | 1 | 1 | 1 | 1 | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 17 cache | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 cache.impl | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 executor.loader | 1 | 4 | 1 | 1 | 1 | 1 | 4 | 5 | 2 | 4 | ||||||||||||||||||||||||||||||
| 20 executor.resultset | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 6 | 5 | 3 | 11 | |||||||||||||||||||||||||||||
| 21 executor.statement | 5 | 3 | 1 | 1 | 5 | 1 | 12 | 11 | ||||||||||||||||||||||||||||||||
| 22 executor | 6 | 1 | 2 | 3 | 6 | 5 | 2 | 2 | 18 | 4 | 13 | |||||||||||||||||||||||||||||
| 23 type | 1 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 24 builder | 1 | 1 | 1 | 1 | 1 | 2 | 8 | 6 | 3 | 1 | 24 | |||||||||||||||||||||||||||||
| 25 builder.annotation | 2 | 1 | 2 | 2 | 1 | 6 | 6 | |||||||||||||||||||||||||||||||||
| 26 builder.xml | 1 | 5 | 1 | 1 | 6 | 4 | 1 | 4 | ||||||||||||||||||||||||||||||||
| 27 session | 2 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 3 | 4 | 2 | 1 | 1 | 2 | 1 | 1 | 10 | |||||||||||||||||
| 28 reflection | 1 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 29 transaction.jdbc | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 30 transaction.managed | 1 | 3 | 2 | |||||||||||||||||||||||||||||||||||||
| 31 binding | 1 | 1 | 13 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 32 datasource.unpooled | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 datasource.pooled | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 34 executor.keygen | 4 | 2 | 2 | 1 | 1 | 4 | ||||||||||||||||||||||||||||||||||
| 35 mapping | 1 | 1 | 1 | 2 | 4 | 6 | 2 | 1 | ||||||||||||||||||||||||||||||||
| 36 annotations | 1 | 1 | 6 | 5 | ||||||||||||||||||||||||||||||||||||
| 37 cursor.defaults | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 scripting.xmltags | 1 | 16 | 1 | 2 | 8 | 5 | 9 | |||||||||||||||||||||||||||||||||
| 39 session.defaults | 1 | 2 | 3 | 9 | 1 | |||||||||||||||||||||||||||||||||||
| 40 scripting.defaults | 1 | 1 | 2 | 3 | 4 | 5 | 2 |
6→2 datasource uses exceptions✕
- Connections
- 1 pair of types, where a type in datasource uses a type in exceptions.
- The types involved
org.apache.ibatis.datasource.DataSourceException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- datasource uses exceptions, so a change to exceptions can break datasource, while a change to datasource can't break exceptions.
- Position
- Below the diagonal: datasource uses a module listed above it, which is the healthy direction.
7→2 logging uses exceptions✕
- Connections
- 1 pair of types, where a type in logging uses a type in exceptions.
- The types involved
org.apache.ibatis.logging.LogException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- logging uses exceptions, so a change to exceptions can break logging, while a change to logging can't break exceptions.
- Position
- Below the diagonal: logging uses a module listed above it, which is the healthy direction.
8→2 parsing uses exceptions✕
- Connections
- 1 pair of types, where a type in parsing uses a type in exceptions.
- The types involved
org.apache.ibatis.parsing.ParsingException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- parsing uses exceptions, so a change to exceptions can break parsing, while a change to parsing can't break exceptions.
- Position
- Below the diagonal: parsing uses a module listed above it, which is the healthy direction.
9→4 reflection.wrapper uses reflection.factory✕
- Connections
- 4 pairs of types, where a type in reflection.wrapper uses a type in reflection.factory.
- The types involved
org.apache.ibatis.reflection.wrapper.BeanWrapper→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.reflection.wrapper.CollectionWrapper→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.reflection.wrapper.MapWrapper→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.reflection.wrapper.ObjectWrapper→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- reflection.wrapper uses reflection.factory, so a change to reflection.factory can break reflection.wrapper, while a change to reflection.wrapper can't break reflection.factory.
- Position
- Below the diagonal: reflection.wrapper uses a module listed above it, which is the healthy direction.
9→5 reflection.wrapper uses reflection.property✕
- Connections
- 5 pairs of types, where a type in reflection.wrapper uses a type in reflection.property.
- The types involved
org.apache.ibatis.reflection.wrapper.BaseWrapper→org.apache.ibatis.reflection.property.PropertyTokenizerorg.apache.ibatis.reflection.wrapper.BeanWrapper→org.apache.ibatis.reflection.property.PropertyTokenizerorg.apache.ibatis.reflection.wrapper.CollectionWrapper→org.apache.ibatis.reflection.property.PropertyTokenizerorg.apache.ibatis.reflection.wrapper.MapWrapper→org.apache.ibatis.reflection.property.PropertyTokenizerorg.apache.ibatis.reflection.wrapper.ObjectWrapper→org.apache.ibatis.reflection.property.PropertyTokenizer
- Direction
- reflection.wrapper uses reflection.property, so a change to reflection.property can break reflection.wrapper, while a change to reflection.wrapper can't break reflection.property.
- Position
- Below the diagonal: reflection.wrapper uses a module listed above it, which is the healthy direction.
9→28 reflection.wrapper uses reflection part of a loop✕
- Connections
- 8 pairs of types, where a type in reflection.wrapper uses a type in reflection.
- The types involved
org.apache.ibatis.reflection.wrapper.BaseWrapper→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.BeanWrapper→org.apache.ibatis.reflection.MetaClassorg.apache.ibatis.reflection.wrapper.BeanWrapper→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.CollectionWrapper→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.DefaultObjectWrapperFactory→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.MapWrapper→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.ObjectWrapper→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.reflection.wrapper.ObjectWrapperFactory→org.apache.ibatis.reflection.MetaObject
- Direction
- reflection.wrapper uses reflection, so a change to reflection can break reflection.wrapper, while a change to reflection.wrapper can't break reflection.
- 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 transaction uses exceptions✕
- Connections
- 1 pair of types, where a type in transaction uses a type in exceptions.
- The types involved
org.apache.ibatis.transaction.TransactionException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- transaction uses exceptions, so a change to exceptions can break transaction, while a change to transaction can't break exceptions.
- Position
- Below the diagonal: transaction uses a module listed above it, which is the healthy direction.
10→27 transaction uses session part of a loop✕
- Connections
- 1 pair of types, where a type in transaction uses a type in session.
- The types involved
org.apache.ibatis.transaction.TransactionFactory→org.apache.ibatis.session.TransactionIsolationLevel
- Direction
- transaction uses session, so a change to session can break transaction, while a change to transaction can't break session.
- 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→7 cache.decorators uses logging✕
- Connections
- 2 pairs of types, where a type in cache.decorators uses a type in logging.
- The types involved
org.apache.ibatis.cache.decorators.LoggingCache→org.apache.ibatis.logging.Logorg.apache.ibatis.cache.decorators.TransactionalCache→org.apache.ibatis.logging.Log
- Direction
- cache.decorators uses logging, so a change to logging can break cache.decorators, while a change to cache.decorators can't break logging.
- Position
- Below the diagonal: cache.decorators uses a module listed above it, which is the healthy direction.
11→17 cache.decorators uses cache part of a loop✕
- Connections
- 10 pairs of types, where a type in cache.decorators uses a type in cache.
- The types involved
org.apache.ibatis.cache.decorators.BlockingCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.FifoCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.LoggingCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.LruCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.ScheduledCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.SerializedCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.SoftCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.SynchronizedCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.TransactionalCache→org.apache.ibatis.cache.Cacheorg.apache.ibatis.cache.decorators.WeakCache→org.apache.ibatis.cache.Cache
- Direction
- cache.decorators uses cache, so a change to cache can break cache.decorators, while a change to cache.decorators can't break cache.
- 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→4 executor.loader.cglib uses reflection.factory✕
- Connections
- 4 pairs of types, where a type in executor.loader.cglib uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.loader.cglib.CglibProxyFactory→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.cglib.CglibSerialStateHolder→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.cglib.EnhancedDeserializationProxyImpl→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.cglib.EnhancedResultObjectProxyImpl→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.loader.cglib uses reflection.factory, so a change to reflection.factory can break executor.loader.cglib, while a change to executor.loader.cglib can't break reflection.factory.
- Position
- Below the diagonal: executor.loader.cglib uses a module listed above it, which is the healthy direction.
12→7 executor.loader.cglib uses logging✕
- Connections
- 1 pair of types, where a type in executor.loader.cglib uses a type in logging.
- The types involved
org.apache.ibatis.executor.loader.cglib.LogHolder→org.apache.ibatis.logging.Log
- Direction
- executor.loader.cglib uses logging, so a change to logging can break executor.loader.cglib, while a change to executor.loader.cglib can't break logging.
- Position
- Below the diagonal: executor.loader.cglib uses a module listed above it, which is the healthy direction.
12→19 executor.loader.cglib uses executor.loader part of a loop✕
- Connections
- 9 pairs of types, where a type in executor.loader.cglib uses a type in executor.loader.
- The types involved
org.apache.ibatis.executor.loader.cglib.CglibProxyFactory→org.apache.ibatis.executor.loader.LoadPairorg.apache.ibatis.executor.loader.cglib.CglibProxyFactory→org.apache.ibatis.executor.loader.ProxyFactoryorg.apache.ibatis.executor.loader.cglib.CglibProxyFactory→org.apache.ibatis.executor.loader.ResultLoaderMaporg.apache.ibatis.executor.loader.cglib.CglibSerialStateHolder→org.apache.ibatis.executor.loader.AbstractSerialStateHolderorg.apache.ibatis.executor.loader.cglib.CglibSerialStateHolder→org.apache.ibatis.executor.loader.LoadPairorg.apache.ibatis.executor.loader.cglib.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.AbstractEnhancedDeserializationProxyorg.apache.ibatis.executor.loader.cglib.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.AbstractSerialStateHolderorg.apache.ibatis.executor.loader.cglib.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.LoadPairorg.apache.ibatis.executor.loader.cglib.EnhancedResultObjectProxyImpl→org.apache.ibatis.executor.loader.ResultLoaderMap
- Direction
- executor.loader.cglib uses executor.loader, so a change to executor.loader can break executor.loader.cglib, while a change to executor.loader.cglib can't break executor.loader.
- 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→27 executor.loader.cglib uses session part of a loop✕
- Connections
- 2 pairs of types, where a type in executor.loader.cglib uses a type in session.
- The types involved
org.apache.ibatis.executor.loader.cglib.CglibProxyFactory→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.loader.cglib.EnhancedResultObjectProxyImpl→org.apache.ibatis.session.Configuration
- Direction
- executor.loader.cglib uses session, so a change to session can break executor.loader.cglib, while a change to executor.loader.cglib can't break session.
- 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 executor.loader.javassist uses reflection.factory✕
- Connections
- 4 pairs of types, where a type in executor.loader.javassist uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.loader.javassist.EnhancedDeserializationProxyImpl→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.javassist.EnhancedResultObjectProxyImpl→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.javassist.JavassistProxyFactory→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.javassist.JavassistSerialStateHolder→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.loader.javassist uses reflection.factory, so a change to reflection.factory can break executor.loader.javassist, while a change to executor.loader.javassist can't break reflection.factory.
- Position
- Below the diagonal: executor.loader.javassist uses a module listed above it, which is the healthy direction.
13→7 executor.loader.javassist uses logging✕
- Connections
- 1 pair of types, where a type in executor.loader.javassist uses a type in logging.
- The types involved
org.apache.ibatis.executor.loader.javassist.LogHolder→org.apache.ibatis.logging.Log
- Direction
- executor.loader.javassist uses logging, so a change to logging can break executor.loader.javassist, while a change to executor.loader.javassist can't break logging.
- Position
- Below the diagonal: executor.loader.javassist uses a module listed above it, which is the healthy direction.
13→19 executor.loader.javassist uses executor.loader part of a loop✕
- Connections
- 9 pairs of types, where a type in executor.loader.javassist uses a type in executor.loader.
- The types involved
org.apache.ibatis.executor.loader.javassist.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.AbstractEnhancedDeserializationProxyorg.apache.ibatis.executor.loader.javassist.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.AbstractSerialStateHolderorg.apache.ibatis.executor.loader.javassist.EnhancedDeserializationProxyImpl→org.apache.ibatis.executor.loader.LoadPairorg.apache.ibatis.executor.loader.javassist.EnhancedResultObjectProxyImpl→org.apache.ibatis.executor.loader.ResultLoaderMaporg.apache.ibatis.executor.loader.javassist.JavassistProxyFactory→org.apache.ibatis.executor.loader.LoadPairorg.apache.ibatis.executor.loader.javassist.JavassistProxyFactory→org.apache.ibatis.executor.loader.ProxyFactoryorg.apache.ibatis.executor.loader.javassist.JavassistProxyFactory→org.apache.ibatis.executor.loader.ResultLoaderMaporg.apache.ibatis.executor.loader.javassist.JavassistSerialStateHolder→org.apache.ibatis.executor.loader.AbstractSerialStateHolderorg.apache.ibatis.executor.loader.javassist.JavassistSerialStateHolder→org.apache.ibatis.executor.loader.LoadPair
- Direction
- executor.loader.javassist uses executor.loader, so a change to executor.loader can break executor.loader.javassist, while a change to executor.loader.javassist can't break executor.loader.
- 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→27 executor.loader.javassist uses session part of a loop✕
- Connections
- 2 pairs of types, where a type in executor.loader.javassist uses a type in session.
- The types involved
org.apache.ibatis.executor.loader.javassist.EnhancedResultObjectProxyImpl→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.loader.javassist.JavassistProxyFactory→org.apache.ibatis.session.Configuration
- Direction
- executor.loader.javassist uses session, so a change to session can break executor.loader.javassist, while a change to executor.loader.javassist can't break session.
- 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 executor.result uses exceptions✕
- Connections
- 1 pair of types, where a type in executor.result uses a type in exceptions.
- The types involved
org.apache.ibatis.executor.result.ResultMapException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- executor.result uses exceptions, so a change to exceptions can break executor.result, while a change to executor.result can't break exceptions.
- Position
- Below the diagonal: executor.result uses a module listed above it, which is the healthy direction.
14→4 executor.result uses reflection.factory✕
- Connections
- 2 pairs of types, where a type in executor.result uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.result.DefaultMapResultHandler→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.result.DefaultResultHandler→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.result uses reflection.factory, so a change to reflection.factory can break executor.result, while a change to executor.result can't break reflection.factory.
- Position
- Below the diagonal: executor.result uses a module listed above it, which is the healthy direction.
14→9 executor.result uses reflection.wrapper✕
- Connections
- 1 pair of types, where a type in executor.result uses a type in reflection.wrapper.
- The types involved
org.apache.ibatis.executor.result.DefaultMapResultHandler→org.apache.ibatis.reflection.wrapper.ObjectWrapperFactory
- Direction
- executor.result uses reflection.wrapper, so a change to reflection.wrapper can break executor.result, while a change to executor.result can't break reflection.wrapper.
- Position
- Below the diagonal: executor.result uses a module listed above it, which is the healthy direction.
14→27 executor.result uses session part of a loop✕
- Connections
- 5 pairs of types, where a type in executor.result uses a type in session.
- The types involved
org.apache.ibatis.executor.result.DefaultMapResultHandler→org.apache.ibatis.session.ResultContextorg.apache.ibatis.executor.result.DefaultMapResultHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.result.DefaultResultContext→org.apache.ibatis.session.ResultContextorg.apache.ibatis.executor.result.DefaultResultHandler→org.apache.ibatis.session.ResultContextorg.apache.ibatis.executor.result.DefaultResultHandler→org.apache.ibatis.session.ResultHandler
- Direction
- executor.result uses session, so a change to session can break executor.result, while a change to executor.result can't break session.
- 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→28 executor.result uses reflection part of a loop✕
- Connections
- 1 pair of types, where a type in executor.result uses a type in reflection.
- The types involved
org.apache.ibatis.executor.result.DefaultMapResultHandler→org.apache.ibatis.reflection.ReflectorFactory
- Direction
- executor.result uses reflection, so a change to reflection can break executor.result, while a change to executor.result can't break reflection.
- 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→7 io uses logging✕
- Connections
- 5 pairs of types, where a type in io uses a type in logging.
- The types involved
org.apache.ibatis.io.DefaultVFS→org.apache.ibatis.logging.Logorg.apache.ibatis.io.ExternalResources→org.apache.ibatis.logging.Logorg.apache.ibatis.io.JBoss6VFS→org.apache.ibatis.logging.Logorg.apache.ibatis.io.ResolverUtil→org.apache.ibatis.logging.Logorg.apache.ibatis.io.SerialFilterChecker→org.apache.ibatis.logging.Log
- Direction
- io uses logging, so a change to logging can break io, while a change to io can't break logging.
- Position
- Below the diagonal: io uses a module listed above it, which is the healthy direction.
16→2 scripting uses exceptions✕
- Connections
- 1 pair of types, where a type in scripting uses a type in exceptions.
- The types involved
org.apache.ibatis.scripting.ScriptingException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- scripting uses exceptions, so a change to exceptions can break scripting, while a change to scripting can't break exceptions.
- Position
- Below the diagonal: scripting uses a module listed above it, which is the healthy direction.
16→3 scripting uses executor.parameter✕
- Connections
- 1 pair of types, where a type in scripting uses a type in executor.parameter.
- The types involved
org.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- scripting uses executor.parameter, so a change to executor.parameter can break scripting, while a change to scripting can't break executor.parameter.
- Position
- Below the diagonal: scripting uses a module listed above it, which is the healthy direction.
16→8 scripting uses parsing✕
- Connections
- 1 pair of types, where a type in scripting uses a type in parsing.
- The types involved
org.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.parsing.XNode
- Direction
- scripting uses parsing, so a change to parsing can break scripting, while a change to scripting can't break parsing.
- Position
- Below the diagonal: scripting uses a module listed above it, which is the healthy direction.
16→27 scripting uses session part of a loop✕
- Connections
- 1 pair of types, where a type in scripting uses a type in session.
- The types involved
org.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.session.Configuration
- Direction
- scripting uses session, so a change to session can break scripting, while a change to scripting can't break session.
- 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→28 scripting uses reflection part of a loop✕
- Connections
- 1 pair of types, where a type in scripting uses a type in reflection.
- The types involved
org.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- scripting uses reflection, so a change to reflection can break scripting, while a change to scripting can't break reflection.
- 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→35 scripting uses mapping part of a loop✕
- Connections
- 3 pairs of types, where a type in scripting uses a type in mapping.
- The types involved
org.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.scripting.LanguageDriver→org.apache.ibatis.mapping.SqlSource
- Direction
- scripting uses mapping, so a change to mapping can break scripting, while a change to scripting can't break mapping.
- 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.
17→2 cache uses exceptions✕
- Connections
- 1 pair of types, where a type in cache uses a type in exceptions.
- The types involved
org.apache.ibatis.cache.CacheException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- cache uses exceptions, so a change to exceptions can break cache, while a change to cache can't break exceptions.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
17→11 cache uses cache.decorators✕
- Connections
- 1 pair of types, where a type in cache uses a type in cache.decorators.
- The types involved
org.apache.ibatis.cache.TransactionalCacheManager→org.apache.ibatis.cache.decorators.TransactionalCache
- Direction
- cache uses cache.decorators, so a change to cache.decorators can break cache, while a change to cache can't break cache.decorators.
- Position
- Below the diagonal: cache uses a module listed above it, which is the healthy direction.
18→17 cache.impl uses cache✕
- Connections
- 1 pair of types, where a type in cache.impl uses a type in cache.
- The types involved
org.apache.ibatis.cache.impl.PerpetualCache→org.apache.ibatis.cache.Cache
- Direction
- cache.impl uses cache, so a change to cache can break cache.impl, while a change to cache.impl can't break cache.
- Position
- Below the diagonal: cache.impl uses a module listed above it, which is the healthy direction.
19→1 executor.loader uses cursor✕
- Connections
- 1 pair of types, where a type in executor.loader uses a type in cursor.
- The types involved
org.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.cursor.Cursor
- Direction
- executor.loader uses cursor, so a change to cursor can break executor.loader, while a change to executor.loader can't break cursor.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→4 executor.loader uses reflection.factory✕
- Connections
- 4 pairs of types, where a type in executor.loader uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.loader.AbstractEnhancedDeserializationProxy→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.AbstractSerialStateHolder→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.ProxyFactory→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.loader uses reflection.factory, so a change to reflection.factory can break executor.loader, while a change to executor.loader can't break reflection.factory.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→7 executor.loader uses logging✕
- Connections
- 1 pair of types, where a type in executor.loader uses a type in logging.
- The types involved
org.apache.ibatis.executor.loader.LoadPair→org.apache.ibatis.logging.Log
- Direction
- executor.loader uses logging, so a change to logging can break executor.loader, while a change to executor.loader can't break logging.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→12 executor.loader uses executor.loader.cglib✕
- Connections
- 1 pair of types, where a type in executor.loader uses a type in executor.loader.cglib.
- The types involved
org.apache.ibatis.executor.loader.CglibProxyFactory→org.apache.ibatis.executor.loader.cglib.CglibProxyFactory
- Direction
- executor.loader uses executor.loader.cglib, so a change to executor.loader.cglib can break executor.loader, while a change to executor.loader can't break executor.loader.cglib.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→13 executor.loader uses executor.loader.javassist✕
- Connections
- 1 pair of types, where a type in executor.loader uses a type in executor.loader.javassist.
- The types involved
org.apache.ibatis.executor.loader.JavassistProxyFactory→org.apache.ibatis.executor.loader.javassist.JavassistProxyFactory
- Direction
- executor.loader uses executor.loader.javassist, so a change to executor.loader.javassist can break executor.loader, while a change to executor.loader can't break executor.loader.javassist.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→17 executor.loader uses cache✕
- Connections
- 1 pair of types, where a type in executor.loader uses a type in cache.
- The types involved
org.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.cache.CacheKey
- Direction
- executor.loader uses cache, so a change to cache can break executor.loader, while a change to executor.loader can't break cache.
- Position
- Below the diagonal: executor.loader uses a module listed above it, which is the healthy direction.
19→22 executor.loader uses executor part of a loop✕
- Connections
- 4 pairs of types, where a type in executor.loader uses a type in executor.
- The types involved
org.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.executor.BaseExecutororg.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.executor.BatchResultorg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.executor.ResultExtractor
- Direction
- executor.loader uses executor, so a change to executor can break executor.loader, while a change to executor.loader can't break executor.
- 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.
19→27 executor.loader uses session part of a loop✕
- Connections
- 5 pairs of types, where a type in executor.loader uses a type in session.
- The types involved
org.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.loader.LoadPair→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.loader.ProxyFactory→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.session.Configuration
- Direction
- executor.loader uses session, so a change to session can break executor.loader, while a change to executor.loader can't break session.
- 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.
19→28 executor.loader uses reflection part of a loop✕
- Connections
- 2 pairs of types, where a type in executor.loader uses a type in reflection.
- The types involved
org.apache.ibatis.executor.loader.LoadPair→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.executor.loader.ResultLoaderMap→org.apache.ibatis.reflection.MetaObject
- Direction
- executor.loader uses reflection, so a change to reflection can break executor.loader, while a change to executor.loader can't break reflection.
- 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.
19→35 executor.loader uses mapping part of a loop✕
- Connections
- 4 pairs of types, where a type in executor.loader uses a type in mapping.
- The types involved
org.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.loader.ClosedExecutor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.loader.ResultLoader→org.apache.ibatis.mapping.MappedStatement
- Direction
- executor.loader uses mapping, so a change to mapping can break executor.loader, while a change to executor.loader can't break mapping.
- 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.
20→1 executor.resultset uses cursor✕
- Connections
- 2 pairs of types, where a type in executor.resultset uses a type in cursor.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.resultset.ResultSetHandler→org.apache.ibatis.cursor.Cursor
- Direction
- executor.resultset uses cursor, so a change to cursor can break executor.resultset, while a change to executor.resultset can't break cursor.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→3 executor.resultset uses executor.parameter✕
- Connections
- 1 pair of types, where a type in executor.resultset uses a type in executor.parameter.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- executor.resultset uses executor.parameter, so a change to executor.parameter can break executor.resultset, while a change to executor.resultset can't break executor.parameter.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→4 executor.resultset uses reflection.factory✕
- Connections
- 2 pairs of types, where a type in executor.resultset uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.resultset.PendingConstructorCreation→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.resultset uses reflection.factory, so a change to reflection.factory can break executor.resultset, while a change to executor.resultset can't break reflection.factory.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→14 executor.resultset uses executor.result✕
- Connections
- 1 pair of types, where a type in executor.resultset uses a type in executor.result.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.executor.result.DefaultResultContext
- Direction
- executor.resultset uses executor.result, so a change to executor.result can break executor.resultset, while a change to executor.resultset can't break executor.result.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→17 executor.resultset uses cache✕
- Connections
- 1 pair of types, where a type in executor.resultset uses a type in cache.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.cache.CacheKey
- Direction
- executor.resultset uses cache, so a change to cache can break executor.resultset, while a change to executor.resultset can't break cache.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→19 executor.resultset uses executor.loader✕
- Connections
- 1 pair of types, where a type in executor.resultset uses a type in executor.loader.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.executor.loader.ResultLoaderMap
- Direction
- executor.resultset uses executor.loader, so a change to executor.loader can break executor.resultset, while a change to executor.resultset can't break executor.loader.
- Position
- Below the diagonal: executor.resultset uses a module listed above it, which is the healthy direction.
20→22 executor.resultset uses executor part of a loop✕
- Connections
- 1 pair of types, where a type in executor.resultset uses a type in executor.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.executor.Executor
- Direction
- executor.resultset uses executor, so a change to executor can break executor.resultset, while a change to executor.resultset can't break executor.
- 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.
20→23 executor.resultset uses type part of a loop✕
- Connections
- 6 pairs of types, where a type in executor.resultset uses a type in type.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.type.TypeHandlerRegistryorg.apache.ibatis.executor.resultset.ResultSetWrapper→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.executor.resultset.ResultSetWrapper→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.executor.resultset.ResultSetWrapper→org.apache.ibatis.type.TypeHandlerRegistryorg.apache.ibatis.executor.resultset.UnMappedColumnAutoMapping→org.apache.ibatis.type.TypeHandler
- Direction
- executor.resultset uses type, so a change to type can break executor.resultset, while a change to executor.resultset can't break type.
- 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.
20→27 executor.resultset uses session part of a loop✕
- Connections
- 5 pairs of types, where a type in executor.resultset uses a type in session.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.session.ResultContextorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.resultset.ResultSetWrapper→org.apache.ibatis.session.Configuration
- Direction
- executor.resultset uses session, so a change to session can break executor.resultset, while a change to executor.resultset can't break session.
- 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.
20→28 executor.resultset uses reflection part of a loop✕
- Connections
- 3 pairs of types, where a type in executor.resultset uses a type in reflection.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.reflection.ReflectorFactoryorg.apache.ibatis.executor.resultset.PendingRelation→org.apache.ibatis.reflection.MetaObject
- Direction
- executor.resultset uses reflection, so a change to reflection can break executor.resultset, while a change to executor.resultset can't break reflection.
- 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.
20→35 executor.resultset uses mapping part of a loop✕
- Connections
- 11 pairs of types, where a type in executor.resultset uses a type in mapping.
- The types involved
org.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.Discriminatororg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.executor.resultset.DefaultResultSetHandler→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.executor.resultset.PendingConstructorCreation→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.executor.resultset.PendingConstructorCreation→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.executor.resultset.PendingCreationKey→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.executor.resultset.PendingRelation→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.executor.resultset.ResultSetWrapper→org.apache.ibatis.mapping.ResultMap
- Direction
- executor.resultset uses mapping, so a change to mapping can break executor.resultset, while a change to executor.resultset can't break mapping.
- 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.
21→1 executor.statement uses cursor✕
- Connections
- 5 pairs of types, where a type in executor.statement uses a type in cursor.
- The types involved
org.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.statement.StatementHandler→org.apache.ibatis.cursor.Cursor
- Direction
- executor.statement uses cursor, so a change to cursor can break executor.statement, while a change to executor.statement can't break cursor.
- Position
- Below the diagonal: executor.statement uses a module listed above it, which is the healthy direction.
21→3 executor.statement uses executor.parameter✕
- Connections
- 3 pairs of types, where a type in executor.statement uses a type in executor.parameter.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.executor.parameter.ParameterHandlerorg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.executor.parameter.ParameterHandlerorg.apache.ibatis.executor.statement.StatementHandler→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- executor.statement uses executor.parameter, so a change to executor.parameter can break executor.statement, while a change to executor.statement can't break executor.parameter.
- Position
- Below the diagonal: executor.statement uses a module listed above it, which is the healthy direction.
21→4 executor.statement uses reflection.factory✕
- Connections
- 1 pair of types, where a type in executor.statement uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor.statement uses reflection.factory, so a change to reflection.factory can break executor.statement, while a change to executor.statement can't break reflection.factory.
- Position
- Below the diagonal: executor.statement uses a module listed above it, which is the healthy direction.
21→20 executor.statement uses executor.resultset✕
- Connections
- 1 pair of types, where a type in executor.statement uses a type in executor.resultset.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.executor.resultset.ResultSetHandler
- Direction
- executor.statement uses executor.resultset, so a change to executor.resultset can break executor.statement, while a change to executor.statement can't break executor.resultset.
- Position
- Below the diagonal: executor.statement uses a module listed above it, which is the healthy direction.
21→22 executor.statement uses executor part of a loop✕
- Connections
- 5 pairs of types, where a type in executor.statement uses a type in executor.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.executor.Executor
- Direction
- executor.statement uses executor, so a change to executor can break executor.statement, while a change to executor.statement can't break executor.
- 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.
21→23 executor.statement uses type part of a loop✕
- Connections
- 1 pair of types, where a type in executor.statement uses a type in type.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.type.TypeHandlerRegistry
- Direction
- executor.statement uses type, so a change to type can break executor.statement, while a change to executor.statement can't break type.
- 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.
21→27 executor.statement uses session part of a loop✕
- Connections
- 12 pairs of types, where a type in executor.statement uses a type in session.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.statement.StatementHandler→org.apache.ibatis.session.ResultHandler
- Direction
- executor.statement uses session, so a change to session can break executor.statement, while a change to executor.statement can't break session.
- 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.
21→35 executor.statement uses mapping part of a loop✕
- Connections
- 11 pairs of types, where a type in executor.statement uses a type in mapping.
- The types involved
org.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.statement.BaseStatementHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.statement.CallableStatementHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.statement.PreparedStatementHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.statement.RoutingStatementHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.statement.SimpleStatementHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.statement.StatementHandler→org.apache.ibatis.mapping.BoundSql
- Direction
- executor.statement uses mapping, so a change to mapping can break executor.statement, while a change to executor.statement can't break mapping.
- 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.
22→1 executor uses cursor✕
- Connections
- 6 pairs of types, where a type in executor uses a type in cursor.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.Executor→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.cursor.Cursororg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.cursor.Cursor
- Direction
- executor uses cursor, so a change to cursor can break executor, while a change to executor can't break cursor.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→2 executor uses exceptions✕
- Connections
- 1 pair of types, where a type in executor uses a type in exceptions.
- The types involved
org.apache.ibatis.executor.ExecutorException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- executor uses exceptions, so a change to exceptions can break executor, while a change to executor can't break exceptions.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→4 executor uses reflection.factory✕
- Connections
- 2 pairs of types, where a type in executor uses a type in reflection.factory.
- The types involved
org.apache.ibatis.executor.DeferredLoad→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.executor.ResultExtractor→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- executor uses reflection.factory, so a change to reflection.factory can break executor, while a change to executor can't break reflection.factory.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→7 executor uses logging✕
- Connections
- 3 pairs of types, where a type in executor uses a type in logging.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.logging.Logorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.logging.Logorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.logging.Log
- Direction
- executor uses logging, so a change to logging can break executor, while a change to executor can't break logging.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→10 executor uses transaction✕
- Connections
- 6 pairs of types, where a type in executor uses a type in transaction.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.executor.Executor→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.transaction.Transaction
- Direction
- executor uses transaction, so a change to transaction can break executor, while a change to executor can't break transaction.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→17 executor uses cache✕
- Connections
- 5 pairs of types, where a type in executor uses a type in cache.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.cache.CacheKeyorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.cache.CacheKeyorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.cache.TransactionalCacheManagerorg.apache.ibatis.executor.DeferredLoad→org.apache.ibatis.cache.CacheKeyorg.apache.ibatis.executor.Executor→org.apache.ibatis.cache.CacheKey
- Direction
- executor uses cache, so a change to cache can break executor, while a change to executor can't break cache.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→18 executor uses cache.impl✕
- Connections
- 2 pairs of types, where a type in executor uses a type in cache.impl.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.cache.impl.PerpetualCacheorg.apache.ibatis.executor.DeferredLoad→org.apache.ibatis.cache.impl.PerpetualCache
- Direction
- executor uses cache.impl, so a change to cache.impl can break executor, while a change to executor can't break cache.impl.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→21 executor uses executor.statement✕
- Connections
- 2 pairs of types, where a type in executor uses a type in executor.statement.
- The types involved
org.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.executor.statement.StatementHandlerorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.executor.statement.StatementHandler
- Direction
- executor uses executor.statement, so a change to executor.statement can break executor, while a change to executor can't break executor.statement.
- Position
- Below the diagonal: executor uses a module listed above it, which is the healthy direction.
22→27 executor uses session part of a loop✕
- Connections
- 18 pairs of types, where a type in executor uses a type in session.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.DeferredLoad→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.Executor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.Executor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.ResultExtractor→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.session.RowBounds
- Direction
- executor uses session, so a change to session can break executor, while a change to executor can't break session.
- 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.
22→28 executor uses reflection part of a loop✕
- Connections
- 4 pairs of types, where a type in executor uses a type in reflection.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.executor.DeferredLoad→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.executor.Executor→org.apache.ibatis.reflection.MetaObject
- Direction
- executor uses reflection, so a change to reflection can break executor, while a change to executor can't break reflection.
- 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.
22→35 executor uses mapping part of a loop✕
- Connections
- 13 pairs of types, where a type in executor uses a type in mapping.
- The types involved
org.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.BaseExecutor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.BatchExecutor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.BatchResult→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.CachingExecutor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.Executor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.Executor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.ReuseExecutor→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.executor.SimpleExecutor→org.apache.ibatis.mapping.MappedStatement
- Direction
- executor uses mapping, so a change to mapping can break executor, while a change to executor can't break mapping.
- 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.
23→2 type uses exceptions✕
- Connections
- 1 pair of types, where a type in type uses a type in exceptions.
- The types involved
org.apache.ibatis.type.TypeException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- type uses exceptions, so a change to exceptions can break type, while a change to type can't break exceptions.
- Position
- Below the diagonal: type uses a module listed above it, which is the healthy direction.
23→22 type uses executor✕
- Connections
- 1 pair of types, where a type in type uses a type in executor.
- The types involved
org.apache.ibatis.type.ConflictedTypeHandler→org.apache.ibatis.executor.ExecutorException
- Direction
- type uses executor, so a change to executor can break type, while a change to type can't break executor.
- Position
- Below the diagonal: type uses a module listed above it, which is the healthy direction.
23→27 type uses session part of a loop✕
- Connections
- 3 pairs of types, where a type in type uses a type in session.
- The types involved
org.apache.ibatis.type.BaseTypeHandler→org.apache.ibatis.session.Configurationorg.apache.ibatis.type.TypeHandlerRegistry→org.apache.ibatis.session.Configurationorg.apache.ibatis.type.UnknownTypeHandler→org.apache.ibatis.session.Configuration
- Direction
- type uses session, so a change to session can break type, while a change to type can't break session.
- 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.
24→2 builder uses exceptions✕
- Connections
- 1 pair of types, where a type in builder uses a type in exceptions.
- The types involved
org.apache.ibatis.builder.BuilderException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- builder uses exceptions, so a change to exceptions can break builder, while a change to builder can't break exceptions.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→5 builder uses reflection.property✕
- Connections
- 1 pair of types, where a type in builder uses a type in reflection.property.
- The types involved
org.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.reflection.property.PropertyTokenizer
- Direction
- builder uses reflection.property, so a change to reflection.property can break builder, while a change to builder can't break reflection.property.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→7 builder uses logging✕
- Connections
- 1 pair of types, where a type in builder uses a type in logging.
- The types involved
org.apache.ibatis.builder.ResultMappingConstructorResolver→org.apache.ibatis.logging.Log
- Direction
- builder uses logging, so a change to logging can break builder, while a change to builder can't break logging.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→8 builder uses parsing✕
- Connections
- 1 pair of types, where a type in builder uses a type in parsing.
- The types involved
org.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.parsing.TokenHandler
- Direction
- builder uses parsing, so a change to parsing can break builder, while a change to builder can't break parsing.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→16 builder uses scripting✕
- Connections
- 1 pair of types, where a type in builder uses a type in scripting.
- The types involved
org.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.scripting.LanguageDriver
- Direction
- builder uses scripting, so a change to scripting can break builder, while a change to builder can't break scripting.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→17 builder uses cache✕
- Connections
- 2 pairs of types, where a type in builder uses a type in cache.
- The types involved
org.apache.ibatis.builder.CacheRefResolver→org.apache.ibatis.cache.Cacheorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.cache.Cache
- Direction
- builder uses cache, so a change to cache can break builder, while a change to builder can't break cache.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→23 builder uses type✕
- Connections
- 8 pairs of types, where a type in builder uses a type in type.
- The types involved
org.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.type.TypeAliasRegistryorg.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.type.TypeHandlerRegistryorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.type.TypeHandler
- Direction
- builder uses type, so a change to type can break builder, while a change to builder can't break type.
- Position
- Below the diagonal: builder uses a module listed above it, which is the healthy direction.
24→27 builder uses session part of a loop✕
- Connections
- 6 pairs of types, where a type in builder uses a type in session.
- The types involved
org.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.ResultMappingConstructorResolver→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.SqlSourceBuilder→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.StaticSqlSource→org.apache.ibatis.session.Configuration
- Direction
- builder uses session, so a change to session can break builder, while a change to builder can't break session.
- 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.
24→28 builder uses reflection part of a loop✕
- Connections
- 3 pairs of types, where a type in builder uses a type in reflection.
- The types involved
org.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- builder uses reflection, so a change to reflection can break builder, while a change to builder can't break reflection.
- 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.
24→34 builder uses executor.keygen part of a loop✕
- Connections
- 1 pair of types, where a type in builder uses a type in executor.keygen.
- The types involved
org.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.executor.keygen.KeyGenerator
- Direction
- builder uses executor.keygen, so a change to executor.keygen can break builder, while a change to builder can't break executor.keygen.
- 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.
24→35 builder uses mapping part of a loop✕
- Connections
- 24 pairs of types, where a type in builder uses a type in mapping.
- The types involved
org.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.mapping.ParameterModeorg.apache.ibatis.builder.BaseBuilder→org.apache.ibatis.mapping.ResultSetTypeorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.Discriminatororg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ParameterMaporg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ParameterModeorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ResultFlagorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.ResultSetTypeorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.SqlCommandTypeorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.builder.MapperBuilderAssistant→org.apache.ibatis.mapping.StatementTypeorg.apache.ibatis.builder.ParameterMappingTokenHandler→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.builder.ResultMapResolver→org.apache.ibatis.mapping.Discriminatororg.apache.ibatis.builder.ResultMapResolver→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.builder.ResultMapResolver→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.builder.ResultMappingConstructorResolver→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.builder.SqlSourceBuilder→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.builder.SqlSourceBuilder→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.builder.StaticSqlSource→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.builder.StaticSqlSource→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.builder.StaticSqlSource→org.apache.ibatis.mapping.SqlSource
- Direction
- builder uses mapping, so a change to mapping can break builder, while a change to builder can't break mapping.
- 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.
25→16 builder.annotation uses scripting✕
- Connections
- 2 pairs of types, where a type in builder.annotation uses a type in scripting.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.scripting.LanguageDriverorg.apache.ibatis.builder.annotation.ProviderSqlSource→org.apache.ibatis.scripting.LanguageDriver
- Direction
- builder.annotation uses scripting, so a change to scripting can break builder.annotation, while a change to builder.annotation can't break scripting.
- Position
- Below the diagonal: builder.annotation uses a module listed above it, which is the healthy direction.
25→24 builder.annotation uses builder✕
- Connections
- 1 pair of types, where a type in builder.annotation uses a type in builder.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.builder.MapperBuilderAssistant
- Direction
- builder.annotation uses builder, so a change to builder can break builder.annotation, while a change to builder.annotation can't break builder.
- Position
- Below the diagonal: builder.annotation uses a module listed above it, which is the healthy direction.
25→27 builder.annotation uses session part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.annotation uses a type in session.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.annotation.ProviderSqlSource→org.apache.ibatis.session.Configuration
- Direction
- builder.annotation uses session, so a change to session can break builder.annotation, while a change to builder.annotation can't break session.
- 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.
25→28 builder.annotation uses reflection part of a loop✕
- Connections
- 2 pairs of types, where a type in builder.annotation uses a type in reflection.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.builder.annotation.ProviderSqlSource→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- builder.annotation uses reflection, so a change to reflection can break builder.annotation, while a change to builder.annotation can't break reflection.
- 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.
25→34 builder.annotation uses executor.keygen part of a loop✕
- Connections
- 1 pair of types, where a type in builder.annotation uses a type in executor.keygen.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.executor.keygen.KeyGenerator
- Direction
- builder.annotation uses executor.keygen, so a change to executor.keygen can break builder.annotation, while a change to builder.annotation can't break executor.keygen.
- 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.
25→35 builder.annotation uses mapping part of a loop✕
- Connections
- 6 pairs of types, where a type in builder.annotation uses a type in mapping.
- The types involved
org.apache.ibatis.builder.annotation.AnnotationWrapper→org.apache.ibatis.mapping.SqlCommandTypeorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.mapping.Discriminatororg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.mapping.ResultMappingorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.builder.annotation.ProviderSqlSource→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.builder.annotation.ProviderSqlSource→org.apache.ibatis.mapping.SqlSource
- Direction
- builder.annotation uses mapping, so a change to mapping can break builder.annotation, while a change to builder.annotation can't break mapping.
- 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.
25→36 builder.annotation uses annotations part of a loop✕
- Connections
- 6 pairs of types, where a type in builder.annotation uses a type in annotations.
- The types involved
org.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.Argorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.NamedResultMaporg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.Propertyorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.Resultorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.SelectKeyorg.apache.ibatis.builder.annotation.MapperAnnotationBuilder→org.apache.ibatis.annotations.TypeDiscriminator
- Direction
- builder.annotation uses annotations, so a change to annotations can break builder.annotation, while a change to builder.annotation can't break annotations.
- 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.
26→6 builder.xml uses datasource✕
- Connections
- 1 pair of types, where a type in builder.xml uses a type in datasource.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.datasource.DataSourceFactory
- Direction
- builder.xml uses datasource, so a change to datasource can break builder.xml, while a change to builder.xml can't break datasource.
- Position
- Below the diagonal: builder.xml uses a module listed above it, which is the healthy direction.
26→8 builder.xml uses parsing✕
- Connections
- 5 pairs of types, where a type in builder.xml uses a type in parsing.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.parsing.XPathParserorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.parsing.XPathParserorg.apache.ibatis.builder.xml.XMLStatementBuilder→org.apache.ibatis.parsing.XNode
- Direction
- builder.xml uses parsing, so a change to parsing can break builder.xml, while a change to builder.xml can't break parsing.
- Position
- Below the diagonal: builder.xml uses a module listed above it, which is the healthy direction.
26→10 builder.xml uses transaction✕
- Connections
- 1 pair of types, where a type in builder.xml uses a type in transaction.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.transaction.TransactionFactory
- Direction
- builder.xml uses transaction, so a change to transaction can break builder.xml, while a change to builder.xml can't break transaction.
- Position
- Below the diagonal: builder.xml uses a module listed above it, which is the healthy direction.
26→16 builder.xml uses scripting✕
- Connections
- 1 pair of types, where a type in builder.xml uses a type in scripting.
- The types involved
org.apache.ibatis.builder.xml.XMLStatementBuilder→org.apache.ibatis.scripting.LanguageDriver
- Direction
- builder.xml uses scripting, so a change to scripting can break builder.xml, while a change to builder.xml can't break scripting.
- Position
- Below the diagonal: builder.xml uses a module listed above it, which is the healthy direction.
26→24 builder.xml uses builder✕
- Connections
- 6 pairs of types, where a type in builder.xml uses a type in builder.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.builder.BaseBuilderorg.apache.ibatis.builder.xml.XMLIncludeTransformer→org.apache.ibatis.builder.MapperBuilderAssistantorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.builder.BaseBuilderorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.builder.MapperBuilderAssistantorg.apache.ibatis.builder.xml.XMLStatementBuilder→org.apache.ibatis.builder.BaseBuilderorg.apache.ibatis.builder.xml.XMLStatementBuilder→org.apache.ibatis.builder.MapperBuilderAssistant
- Direction
- builder.xml uses builder, so a change to builder can break builder.xml, while a change to builder.xml can't break builder.
- Position
- Below the diagonal: builder.xml uses a module listed above it, which is the healthy direction.
26→27 builder.xml uses session part of a loop✕
- Connections
- 4 pairs of types, where a type in builder.xml uses a type in session.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.xml.XMLIncludeTransformer→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.session.Configurationorg.apache.ibatis.builder.xml.XMLStatementBuilder→org.apache.ibatis.session.Configuration
- Direction
- builder.xml uses session, so a change to session can break builder.xml, while a change to builder.xml can't break session.
- 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.
26→28 builder.xml uses reflection part of a loop✕
- Connections
- 1 pair of types, where a type in builder.xml uses a type in reflection.
- The types involved
org.apache.ibatis.builder.xml.XMLConfigBuilder→org.apache.ibatis.reflection.ReflectorFactory
- Direction
- builder.xml uses reflection, so a change to reflection can break builder.xml, while a change to builder.xml can't break reflection.
- 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.
26→35 builder.xml uses mapping part of a loop✕
- Connections
- 4 pairs of types, where a type in builder.xml uses a type in mapping.
- The types involved
org.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.mapping.Discriminatororg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.mapping.ResultFlagorg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.builder.xml.XMLMapperBuilder→org.apache.ibatis.mapping.ResultMapping
- Direction
- builder.xml uses mapping, so a change to mapping can break builder.xml, while a change to builder.xml can't break mapping.
- 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 session uses cursor✕
- Connections
- 2 pairs of types, where a type in session uses a type in cursor.
- The types involved
org.apache.ibatis.session.SqlSession→org.apache.ibatis.cursor.Cursororg.apache.ibatis.session.SqlSessionManager→org.apache.ibatis.cursor.Cursor
- Direction
- session uses cursor, so a change to cursor can break session, while a change to session can't break cursor.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→2 session uses exceptions✕
- Connections
- 1 pair of types, where a type in session uses a type in exceptions.
- The types involved
org.apache.ibatis.session.SqlSessionException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- session uses exceptions, so a change to exceptions can break session, while a change to session can't break exceptions.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→3 session uses executor.parameter✕
- Connections
- 1 pair of types, where a type in session uses a type in executor.parameter.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- session uses executor.parameter, so a change to executor.parameter can break session, while a change to session can't break executor.parameter.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→4 session uses reflection.factory✕
- Connections
- 1 pair of types, where a type in session uses a type in reflection.factory.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- session uses reflection.factory, so a change to reflection.factory can break session, while a change to session can't break reflection.factory.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→7 session uses logging✕
- Connections
- 2 pairs of types, where a type in session uses a type in logging.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.logging.Logorg.apache.ibatis.session.LogHolder→org.apache.ibatis.logging.Log
- Direction
- session uses logging, so a change to logging can break session, while a change to session can't break logging.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→8 session uses parsing✕
- Connections
- 1 pair of types, where a type in session uses a type in parsing.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.parsing.XNode
- Direction
- session uses parsing, so a change to parsing can break session, while a change to session can't break parsing.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→9 session uses reflection.wrapper✕
- Connections
- 1 pair of types, where a type in session uses a type in reflection.wrapper.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.reflection.wrapper.ObjectWrapperFactory
- Direction
- session uses reflection.wrapper, so a change to reflection.wrapper can break session, while a change to session can't break reflection.wrapper.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→10 session uses transaction✕
- Connections
- 1 pair of types, where a type in session uses a type in transaction.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.transaction.Transaction
- Direction
- session uses transaction, so a change to transaction can break session, while a change to session can't break transaction.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→15 session uses io✕
- Connections
- 1 pair of types, where a type in session uses a type in io.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.io.VFS
- Direction
- session uses io, so a change to io can break session, while a change to session can't break io.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→16 session uses scripting✕
- Connections
- 2 pairs of types, where a type in session uses a type in scripting.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.scripting.LanguageDriverorg.apache.ibatis.session.Configuration→org.apache.ibatis.scripting.LanguageDriverRegistry
- Direction
- session uses scripting, so a change to scripting can break session, while a change to session can't break scripting.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→17 session uses cache✕
- Connections
- 1 pair of types, where a type in session uses a type in cache.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.cache.Cache
- Direction
- session uses cache, so a change to cache can break session, while a change to session can't break cache.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→19 session uses executor.loader✕
- Connections
- 1 pair of types, where a type in session uses a type in executor.loader.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.loader.ProxyFactory
- Direction
- session uses executor.loader, so a change to executor.loader can break session, while a change to session can't break executor.loader.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→20 session uses executor.resultset✕
- Connections
- 1 pair of types, where a type in session uses a type in executor.resultset.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.resultset.ResultSetHandler
- Direction
- session uses executor.resultset, so a change to executor.resultset can break session, while a change to session can't break executor.resultset.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→21 session uses executor.statement✕
- Connections
- 1 pair of types, where a type in session uses a type in executor.statement.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.statement.StatementHandler
- Direction
- session uses executor.statement, so a change to executor.statement can break session, while a change to session can't break executor.statement.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→22 session uses executor✕
- Connections
- 3 pairs of types, where a type in session uses a type in executor.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.Executororg.apache.ibatis.session.SqlSession→org.apache.ibatis.executor.BatchResultorg.apache.ibatis.session.SqlSessionManager→org.apache.ibatis.executor.BatchResult
- Direction
- session uses executor, so a change to executor can break session, while a change to session can't break executor.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→23 session uses type✕
- Connections
- 4 pairs of types, where a type in session uses a type in type.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.session.Configuration→org.apache.ibatis.type.TypeAliasRegistryorg.apache.ibatis.session.Configuration→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.session.Configuration→org.apache.ibatis.type.TypeHandlerRegistry
- Direction
- session uses type, so a change to type can break session, while a change to session can't break type.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→24 session uses builder✕
- Connections
- 2 pairs of types, where a type in session uses a type in builder.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.builder.CacheRefResolverorg.apache.ibatis.session.Configuration→org.apache.ibatis.builder.ResultMapResolver
- Direction
- session uses builder, so a change to builder can break session, while a change to session can't break builder.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→25 session uses builder.annotation✕
- Connections
- 1 pair of types, where a type in session uses a type in builder.annotation.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.builder.annotation.MethodResolver
- Direction
- session uses builder.annotation, so a change to builder.annotation can break session, while a change to session can't break builder.annotation.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→26 session uses builder.xml✕
- Connections
- 1 pair of types, where a type in session uses a type in builder.xml.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.builder.xml.XMLStatementBuilder
- Direction
- session uses builder.xml, so a change to builder.xml can break session, while a change to session can't break builder.xml.
- Position
- Below the diagonal: session uses a module listed above it, which is the healthy direction.
27→28 session uses reflection part of a loop✕
- Connections
- 2 pairs of types, where a type in session uses a type in reflection.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.session.Configuration→org.apache.ibatis.reflection.ReflectorFactory
- Direction
- session uses reflection, so a change to reflection can break session, while a change to session can't break reflection.
- 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→31 session uses binding part of a loop✕
- Connections
- 1 pair of types, where a type in session uses a type in binding.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.binding.MapperRegistry
- Direction
- session uses binding, so a change to binding can break session, while a change to session can't break binding.
- 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→34 session uses executor.keygen part of a loop✕
- Connections
- 1 pair of types, where a type in session uses a type in executor.keygen.
- The types involved
org.apache.ibatis.session.Configuration→org.apache.ibatis.executor.keygen.KeyGenerator
- Direction
- session uses executor.keygen, so a change to executor.keygen can break session, while a change to session can't break executor.keygen.
- 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→35 session uses mapping part of a loop✕
- Connections
- 10 pairs of types, where a type in session uses a type in mapping.
- The types involved
org.apache.ibatis.session.1→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.session.2→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.session.3→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.session.AutoMappingUnknownColumnBehavior→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.Environmentorg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.ParameterMaporg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.ResultMaporg.apache.ibatis.session.Configuration→org.apache.ibatis.mapping.ResultSetType
- Direction
- session uses mapping, so a change to mapping can break session, while a change to session can't break mapping.
- 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→2 reflection uses exceptions✕
- Connections
- 1 pair of types, where a type in reflection uses a type in exceptions.
- The types involved
org.apache.ibatis.reflection.ReflectionException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- reflection uses exceptions, so a change to exceptions can break reflection, while a change to reflection can't break exceptions.
- Position
- Below the diagonal: reflection uses a module listed above it, which is the healthy direction.
28→4 reflection uses reflection.factory✕
- Connections
- 2 pairs of types, where a type in reflection uses a type in reflection.factory.
- The types involved
org.apache.ibatis.reflection.MetaObject→org.apache.ibatis.reflection.factory.ObjectFactoryorg.apache.ibatis.reflection.SystemMetaObject→org.apache.ibatis.reflection.factory.ObjectFactory
- Direction
- reflection uses reflection.factory, so a change to reflection.factory can break reflection, while a change to reflection can't break reflection.factory.
- Position
- Below the diagonal: reflection uses a module listed above it, which is the healthy direction.
28→5 reflection uses reflection.property✕
- Connections
- 1 pair of types, where a type in reflection uses a type in reflection.property.
- The types involved
org.apache.ibatis.reflection.MetaClass→org.apache.ibatis.reflection.property.PropertyTokenizer
- Direction
- reflection uses reflection.property, so a change to reflection.property can break reflection, while a change to reflection can't break reflection.property.
- Position
- Below the diagonal: reflection uses a module listed above it, which is the healthy direction.
28→9 reflection uses reflection.wrapper✕
- Connections
- 3 pairs of types, where a type in reflection uses a type in reflection.wrapper.
- The types involved
org.apache.ibatis.reflection.MetaObject→org.apache.ibatis.reflection.wrapper.ObjectWrapperorg.apache.ibatis.reflection.MetaObject→org.apache.ibatis.reflection.wrapper.ObjectWrapperFactoryorg.apache.ibatis.reflection.SystemMetaObject→org.apache.ibatis.reflection.wrapper.ObjectWrapperFactory
- Direction
- reflection uses reflection.wrapper, so a change to reflection.wrapper can break reflection, while a change to reflection can't break reflection.wrapper.
- Position
- Below the diagonal: reflection uses a module listed above it, which is the healthy direction.
28→27 reflection uses session✕
- Connections
- 1 pair of types, where a type in reflection uses a type in session.
- The types involved
org.apache.ibatis.reflection.ParamNameResolver→org.apache.ibatis.session.Configuration
- Direction
- reflection uses session, so a change to session can break reflection, while a change to reflection can't break session.
- Position
- Below the diagonal: reflection uses a module listed above it, which is the healthy direction.
29→7 transaction.jdbc uses logging✕
- Connections
- 1 pair of types, where a type in transaction.jdbc uses a type in logging.
- The types involved
org.apache.ibatis.transaction.jdbc.JdbcTransaction→org.apache.ibatis.logging.Log
- Direction
- transaction.jdbc uses logging, so a change to logging can break transaction.jdbc, while a change to transaction.jdbc can't break logging.
- Position
- Below the diagonal: transaction.jdbc uses a module listed above it, which is the healthy direction.
29→10 transaction.jdbc uses transaction✕
- Connections
- 3 pairs of types, where a type in transaction.jdbc uses a type in transaction.
- The types involved
org.apache.ibatis.transaction.jdbc.JdbcTransaction→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.transaction.jdbc.JdbcTransactionFactory→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.transaction.jdbc.JdbcTransactionFactory→org.apache.ibatis.transaction.TransactionFactory
- Direction
- transaction.jdbc uses transaction, so a change to transaction can break transaction.jdbc, while a change to transaction.jdbc can't break transaction.
- Position
- Below the diagonal: transaction.jdbc uses a module listed above it, which is the healthy direction.
29→27 transaction.jdbc uses session✕
- Connections
- 2 pairs of types, where a type in transaction.jdbc uses a type in session.
- The types involved
org.apache.ibatis.transaction.jdbc.JdbcTransaction→org.apache.ibatis.session.TransactionIsolationLevelorg.apache.ibatis.transaction.jdbc.JdbcTransactionFactory→org.apache.ibatis.session.TransactionIsolationLevel
- Direction
- transaction.jdbc uses session, so a change to session can break transaction.jdbc, while a change to transaction.jdbc can't break session.
- Position
- Below the diagonal: transaction.jdbc uses a module listed above it, which is the healthy direction.
30→7 transaction.managed uses logging✕
- Connections
- 1 pair of types, where a type in transaction.managed uses a type in logging.
- The types involved
org.apache.ibatis.transaction.managed.ManagedTransaction→org.apache.ibatis.logging.Log
- Direction
- transaction.managed uses logging, so a change to logging can break transaction.managed, while a change to transaction.managed can't break logging.
- Position
- Below the diagonal: transaction.managed uses a module listed above it, which is the healthy direction.
30→10 transaction.managed uses transaction✕
- Connections
- 3 pairs of types, where a type in transaction.managed uses a type in transaction.
- The types involved
org.apache.ibatis.transaction.managed.ManagedTransaction→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.transaction.managed.ManagedTransactionFactory→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.transaction.managed.ManagedTransactionFactory→org.apache.ibatis.transaction.TransactionFactory
- Direction
- transaction.managed uses transaction, so a change to transaction can break transaction.managed, while a change to transaction.managed can't break transaction.
- Position
- Below the diagonal: transaction.managed uses a module listed above it, which is the healthy direction.
30→27 transaction.managed uses session✕
- Connections
- 2 pairs of types, where a type in transaction.managed uses a type in session.
- The types involved
org.apache.ibatis.transaction.managed.ManagedTransaction→org.apache.ibatis.session.TransactionIsolationLevelorg.apache.ibatis.transaction.managed.ManagedTransactionFactory→org.apache.ibatis.session.TransactionIsolationLevel
- Direction
- transaction.managed uses session, so a change to session can break transaction.managed, while a change to transaction.managed can't break session.
- Position
- Below the diagonal: transaction.managed uses a module listed above it, which is the healthy direction.
31→1 binding uses cursor✕
- Connections
- 1 pair of types, where a type in binding uses a type in cursor.
- The types involved
org.apache.ibatis.binding.MapperMethod→org.apache.ibatis.cursor.Cursor
- Direction
- binding uses cursor, so a change to cursor can break binding, while a change to binding can't break cursor.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
31→2 binding uses exceptions✕
- Connections
- 1 pair of types, where a type in binding uses a type in exceptions.
- The types involved
org.apache.ibatis.binding.BindingException→org.apache.ibatis.exceptions.PersistenceException
- Direction
- binding uses exceptions, so a change to exceptions can break binding, while a change to binding can't break exceptions.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
31→27 binding uses session✕
- Connections
- 13 pairs of types, where a type in binding uses a type in session.
- The types involved
org.apache.ibatis.binding.DefaultMethodInvoker→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MapperMethod→org.apache.ibatis.session.Configurationorg.apache.ibatis.binding.MapperMethod→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MapperMethodInvoker→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MapperProxy→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MapperProxyFactory→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MapperRegistry→org.apache.ibatis.session.Configurationorg.apache.ibatis.binding.MapperRegistry→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.MethodSignature→org.apache.ibatis.session.Configurationorg.apache.ibatis.binding.MethodSignature→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.binding.MethodSignature→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.binding.PlainMethodInvoker→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.binding.SqlCommand→org.apache.ibatis.session.Configuration
- Direction
- binding uses session, so a change to session can break binding, while a change to binding can't break session.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
31→28 binding uses reflection✕
- Connections
- 1 pair of types, where a type in binding uses a type in reflection.
- The types involved
org.apache.ibatis.binding.MethodSignature→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- binding uses reflection, so a change to reflection can break binding, while a change to binding can't break reflection.
- Position
- Below the diagonal: binding uses a module listed above it, which is the healthy direction.
31→35 binding uses mapping part of a loop✕
- Connections
- 2 pairs of types, where a type in binding uses a type in mapping.
- The types involved
org.apache.ibatis.binding.SqlCommand→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.binding.SqlCommand→org.apache.ibatis.mapping.SqlCommandType
- Direction
- binding uses mapping, so a change to mapping can break binding, while a change to binding can't break mapping.
- 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→6 datasource.unpooled uses datasource✕
- Connections
- 1 pair of types, where a type in datasource.unpooled uses a type in datasource.
- The types involved
org.apache.ibatis.datasource.unpooled.UnpooledDataSourceFactory→org.apache.ibatis.datasource.DataSourceFactory
- Direction
- datasource.unpooled uses datasource, so a change to datasource can break datasource.unpooled, while a change to datasource.unpooled can't break datasource.
- Position
- Below the diagonal: datasource.unpooled uses a module listed above it, which is the healthy direction.
32→28 datasource.unpooled uses reflection✕
- Connections
- 1 pair of types, where a type in datasource.unpooled uses a type in reflection.
- The types involved
org.apache.ibatis.datasource.unpooled.UnpooledDataSourceFactory→org.apache.ibatis.reflection.MetaObject
- Direction
- datasource.unpooled uses reflection, so a change to reflection can break datasource.unpooled, while a change to datasource.unpooled can't break reflection.
- Position
- Below the diagonal: datasource.unpooled uses a module listed above it, which is the healthy direction.
33→7 datasource.pooled uses logging✕
- Connections
- 1 pair of types, where a type in datasource.pooled uses a type in logging.
- The types involved
org.apache.ibatis.datasource.pooled.PooledDataSource→org.apache.ibatis.logging.Log
- Direction
- datasource.pooled uses logging, so a change to logging can break datasource.pooled, while a change to datasource.pooled can't break logging.
- Position
- Below the diagonal: datasource.pooled uses a module listed above it, which is the healthy direction.
33→32 datasource.pooled uses datasource.unpooled✕
- Connections
- 2 pairs of types, where a type in datasource.pooled uses a type in datasource.unpooled.
- The types involved
org.apache.ibatis.datasource.pooled.PooledDataSource→org.apache.ibatis.datasource.unpooled.UnpooledDataSourceorg.apache.ibatis.datasource.pooled.PooledDataSourceFactory→org.apache.ibatis.datasource.unpooled.UnpooledDataSourceFactory
- Direction
- datasource.pooled uses datasource.unpooled, so a change to datasource.unpooled can break datasource.pooled, while a change to datasource.pooled can't break datasource.unpooled.
- Position
- Below the diagonal: datasource.pooled uses a module listed above it, which is the healthy direction.
34→22 executor.keygen uses executor✕
- Connections
- 4 pairs of types, where a type in executor.keygen uses a type in executor.
- The types involved
org.apache.ibatis.executor.keygen.Jdbc3KeyGenerator→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.keygen.KeyGenerator→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.keygen.NoKeyGenerator→org.apache.ibatis.executor.Executororg.apache.ibatis.executor.keygen.SelectKeyGenerator→org.apache.ibatis.executor.Executor
- Direction
- executor.keygen uses executor, so a change to executor can break executor.keygen, while a change to executor.keygen can't break executor.
- Position
- Below the diagonal: executor.keygen uses a module listed above it, which is the healthy direction.
34→23 executor.keygen uses type✕
- Connections
- 2 pairs of types, where a type in executor.keygen uses a type in type.
- The types involved
org.apache.ibatis.executor.keygen.KeyAssigner→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.executor.keygen.KeyAssigner→org.apache.ibatis.type.TypeHandlerRegistry
- Direction
- executor.keygen uses type, so a change to type can break executor.keygen, while a change to executor.keygen can't break type.
- Position
- Below the diagonal: executor.keygen uses a module listed above it, which is the healthy direction.
34→27 executor.keygen uses session✕
- Connections
- 2 pairs of types, where a type in executor.keygen uses a type in session.
- The types involved
org.apache.ibatis.executor.keygen.Jdbc3KeyGenerator→org.apache.ibatis.session.Configurationorg.apache.ibatis.executor.keygen.KeyAssigner→org.apache.ibatis.session.Configuration
- Direction
- executor.keygen uses session, so a change to session can break executor.keygen, while a change to executor.keygen can't break session.
- Position
- Below the diagonal: executor.keygen uses a module listed above it, which is the healthy direction.
34→28 executor.keygen uses reflection✕
- Connections
- 1 pair of types, where a type in executor.keygen uses a type in reflection.
- The types involved
org.apache.ibatis.executor.keygen.SelectKeyGenerator→org.apache.ibatis.reflection.MetaObject
- Direction
- executor.keygen uses reflection, so a change to reflection can break executor.keygen, while a change to executor.keygen can't break reflection.
- Position
- Below the diagonal: executor.keygen uses a module listed above it, which is the healthy direction.
34→31 executor.keygen uses binding✕
- Connections
- 1 pair of types, where a type in executor.keygen uses a type in binding.
- The types involved
org.apache.ibatis.executor.keygen.Jdbc3KeyGenerator→org.apache.ibatis.binding.ParamMap
- Direction
- executor.keygen uses binding, so a change to binding can break executor.keygen, while a change to executor.keygen can't break binding.
- Position
- Below the diagonal: executor.keygen uses a module listed above it, which is the healthy direction.
34→35 executor.keygen uses mapping part of a loop✕
- Connections
- 4 pairs of types, where a type in executor.keygen uses a type in mapping.
- The types involved
org.apache.ibatis.executor.keygen.Jdbc3KeyGenerator→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.keygen.KeyGenerator→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.keygen.NoKeyGenerator→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.executor.keygen.SelectKeyGenerator→org.apache.ibatis.mapping.MappedStatement
- Direction
- executor.keygen uses mapping, so a change to mapping can break executor.keygen, while a change to executor.keygen can't break mapping.
- 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→7 mapping uses logging✕
- Connections
- 1 pair of types, where a type in mapping uses a type in logging.
- The types involved
org.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.logging.Log
- Direction
- mapping uses logging, so a change to logging can break mapping, while a change to mapping can't break logging.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→10 mapping uses transaction✕
- Connections
- 1 pair of types, where a type in mapping uses a type in transaction.
- The types involved
org.apache.ibatis.mapping.Environment→org.apache.ibatis.transaction.TransactionFactory
- Direction
- mapping uses transaction, so a change to transaction can break mapping, while a change to mapping can't break transaction.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→16 mapping uses scripting✕
- Connections
- 1 pair of types, where a type in mapping uses a type in scripting.
- The types involved
org.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.scripting.LanguageDriver
- Direction
- mapping uses scripting, so a change to scripting can break mapping, while a change to mapping can't break scripting.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→17 mapping uses cache✕
- Connections
- 2 pairs of types, where a type in mapping uses a type in cache.
- The types involved
org.apache.ibatis.mapping.CacheBuilder→org.apache.ibatis.cache.Cacheorg.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.cache.Cache
- Direction
- mapping uses cache, so a change to cache can break mapping, while a change to mapping can't break cache.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→23 mapping uses type✕
- Connections
- 4 pairs of types, where a type in mapping uses a type in type.
- The types involved
org.apache.ibatis.mapping.ParameterMapping→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.mapping.ParameterMapping→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.mapping.ResultMapping→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.mapping.ResultMapping→org.apache.ibatis.type.TypeHandler
- Direction
- mapping uses type, so a change to type can break mapping, while a change to mapping can't break type.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→27 mapping uses session✕
- Connections
- 6 pairs of types, where a type in mapping uses a type in session.
- The types involved
org.apache.ibatis.mapping.BoundSql→org.apache.ibatis.session.Configurationorg.apache.ibatis.mapping.Builder→org.apache.ibatis.session.Configurationorg.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.session.Configurationorg.apache.ibatis.mapping.ParameterMapping→org.apache.ibatis.session.Configurationorg.apache.ibatis.mapping.ResultMap→org.apache.ibatis.session.Configurationorg.apache.ibatis.mapping.ResultMapping→org.apache.ibatis.session.Configuration
- Direction
- mapping uses session, so a change to session can break mapping, while a change to mapping can't break session.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→28 mapping uses reflection✕
- Connections
- 2 pairs of types, where a type in mapping uses a type in reflection.
- The types involved
org.apache.ibatis.mapping.BoundSql→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- mapping uses reflection, so a change to reflection can break mapping, while a change to mapping can't break reflection.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
35→34 mapping uses executor.keygen✕
- Connections
- 1 pair of types, where a type in mapping uses a type in executor.keygen.
- The types involved
org.apache.ibatis.mapping.MappedStatement→org.apache.ibatis.executor.keygen.KeyGenerator
- Direction
- mapping uses executor.keygen, so a change to executor.keygen can break mapping, while a change to mapping can't break executor.keygen.
- Position
- Below the diagonal: mapping uses a module listed above it, which is the healthy direction.
36→16 annotations uses scripting✕
- Connections
- 1 pair of types, where a type in annotations uses a type in scripting.
- The types involved
org.apache.ibatis.annotations.Lang→org.apache.ibatis.scripting.LanguageDriver
- Direction
- annotations uses scripting, so a change to scripting can break annotations, while a change to annotations can't break scripting.
- Position
- Below the diagonal: annotations uses a module listed above it, which is the healthy direction.
36→17 annotations uses cache✕
- Connections
- 1 pair of types, where a type in annotations uses a type in cache.
- The types involved
org.apache.ibatis.annotations.CacheNamespace→org.apache.ibatis.cache.Cache
- Direction
- annotations uses cache, so a change to cache can break annotations, while a change to annotations can't break cache.
- Position
- Below the diagonal: annotations uses a module listed above it, which is the healthy direction.
36→23 annotations uses type✕
- Connections
- 6 pairs of types, where a type in annotations uses a type in type.
- The types involved
org.apache.ibatis.annotations.Arg→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.annotations.Arg→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.annotations.Result→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.annotations.Result→org.apache.ibatis.type.TypeHandlerorg.apache.ibatis.annotations.TypeDiscriminator→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.annotations.TypeDiscriminator→org.apache.ibatis.type.TypeHandler
- Direction
- annotations uses type, so a change to type can break annotations, while a change to annotations can't break type.
- Position
- Below the diagonal: annotations uses a module listed above it, which is the healthy direction.
36→35 annotations uses mapping✕
- Connections
- 5 pairs of types, where a type in annotations uses a type in mapping.
- The types involved
org.apache.ibatis.annotations.Many→org.apache.ibatis.mapping.FetchTypeorg.apache.ibatis.annotations.One→org.apache.ibatis.mapping.FetchTypeorg.apache.ibatis.annotations.Options→org.apache.ibatis.mapping.ResultSetTypeorg.apache.ibatis.annotations.Options→org.apache.ibatis.mapping.StatementTypeorg.apache.ibatis.annotations.SelectKey→org.apache.ibatis.mapping.StatementType
- Direction
- annotations uses mapping, so a change to mapping can break annotations, while a change to annotations can't break mapping.
- Position
- Below the diagonal: annotations uses a module listed above it, which is the healthy direction.
37→1 cursor.defaults uses cursor✕
- Connections
- 1 pair of types, where a type in cursor.defaults uses a type in cursor.
- The types involved
org.apache.ibatis.cursor.defaults.DefaultCursor→org.apache.ibatis.cursor.Cursor
- Direction
- cursor.defaults uses cursor, so a change to cursor can break cursor.defaults, while a change to cursor.defaults can't break cursor.
- Position
- Below the diagonal: cursor.defaults uses a module listed above it, which is the healthy direction.
37→20 cursor.defaults uses executor.resultset✕
- Connections
- 2 pairs of types, where a type in cursor.defaults uses a type in executor.resultset.
- The types involved
org.apache.ibatis.cursor.defaults.DefaultCursor→org.apache.ibatis.executor.resultset.DefaultResultSetHandlerorg.apache.ibatis.cursor.defaults.DefaultCursor→org.apache.ibatis.executor.resultset.ResultSetWrapper
- Direction
- cursor.defaults uses executor.resultset, so a change to executor.resultset can break cursor.defaults, while a change to cursor.defaults can't break executor.resultset.
- Position
- Below the diagonal: cursor.defaults uses a module listed above it, which is the healthy direction.
37→27 cursor.defaults uses session✕
- Connections
- 3 pairs of types, where a type in cursor.defaults uses a type in session.
- The types involved
org.apache.ibatis.cursor.defaults.DefaultCursor→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.cursor.defaults.ObjectWrapperResultHandler→org.apache.ibatis.session.ResultContextorg.apache.ibatis.cursor.defaults.ObjectWrapperResultHandler→org.apache.ibatis.session.ResultHandler
- Direction
- cursor.defaults uses session, so a change to session can break cursor.defaults, while a change to cursor.defaults can't break session.
- Position
- Below the diagonal: cursor.defaults uses a module listed above it, which is the healthy direction.
37→35 cursor.defaults uses mapping✕
- Connections
- 1 pair of types, where a type in cursor.defaults uses a type in mapping.
- The types involved
org.apache.ibatis.cursor.defaults.DefaultCursor→org.apache.ibatis.mapping.ResultMap
- Direction
- cursor.defaults uses mapping, so a change to mapping can break cursor.defaults, while a change to cursor.defaults can't break mapping.
- Position
- Below the diagonal: cursor.defaults uses a module listed above it, which is the healthy direction.
38→3 scripting.xmltags uses executor.parameter✕
- Connections
- 1 pair of types, where a type in scripting.xmltags uses a type in executor.parameter.
- The types involved
org.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- scripting.xmltags uses executor.parameter, so a change to executor.parameter can break scripting.xmltags, while a change to scripting.xmltags can't break executor.parameter.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→8 scripting.xmltags uses parsing✕
- Connections
- 16 pairs of types, where a type in scripting.xmltags uses a type in parsing.
- The types involved
org.apache.ibatis.scripting.xmltags.BindHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.BindingTokenParser→org.apache.ibatis.parsing.TokenHandlerorg.apache.ibatis.scripting.xmltags.ChooseHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.DynamicCheckerTokenParser→org.apache.ibatis.parsing.TokenHandlerorg.apache.ibatis.scripting.xmltags.DynamicContext→org.apache.ibatis.parsing.GenericTokenParserorg.apache.ibatis.scripting.xmltags.ForEachHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.IfHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.NodeHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.OtherwiseHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.SetHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.TextSqlNode→org.apache.ibatis.parsing.GenericTokenParserorg.apache.ibatis.scripting.xmltags.TextSqlNode→org.apache.ibatis.parsing.TokenHandlerorg.apache.ibatis.scripting.xmltags.TrimHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.WhereHandler→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.parsing.XNodeorg.apache.ibatis.scripting.xmltags.XMLScriptBuilder→org.apache.ibatis.parsing.XNode
- Direction
- scripting.xmltags uses parsing, so a change to parsing can break scripting.xmltags, while a change to scripting.xmltags can't break parsing.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→16 scripting.xmltags uses scripting✕
- Connections
- 1 pair of types, where a type in scripting.xmltags uses a type in scripting.
- The types involved
org.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.scripting.LanguageDriver
- Direction
- scripting.xmltags uses scripting, so a change to scripting can break scripting.xmltags, while a change to scripting.xmltags can't break scripting.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→24 scripting.xmltags uses builder✕
- Connections
- 2 pairs of types, where a type in scripting.xmltags uses a type in builder.
- The types involved
org.apache.ibatis.scripting.xmltags.DynamicContext→org.apache.ibatis.builder.ParameterMappingTokenHandlerorg.apache.ibatis.scripting.xmltags.XMLScriptBuilder→org.apache.ibatis.builder.BaseBuilder
- Direction
- scripting.xmltags uses builder, so a change to builder can break scripting.xmltags, while a change to scripting.xmltags can't break builder.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→27 scripting.xmltags uses session✕
- Connections
- 8 pairs of types, where a type in scripting.xmltags uses a type in session.
- The types involved
org.apache.ibatis.scripting.xmltags.DynamicContext→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.DynamicSqlSource→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.ForEachSqlNode→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.SetSqlNode→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.TrimSqlNode→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.WhereSqlNode→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.xmltags.XMLScriptBuilder→org.apache.ibatis.session.Configuration
- Direction
- scripting.xmltags uses session, so a change to session can break scripting.xmltags, while a change to scripting.xmltags can't break session.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→28 scripting.xmltags uses reflection✕
- Connections
- 5 pairs of types, where a type in scripting.xmltags uses a type in reflection.
- The types involved
org.apache.ibatis.scripting.xmltags.ContextMap→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.scripting.xmltags.DynamicContext→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.scripting.xmltags.DynamicSqlSource→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.scripting.xmltags.XMLScriptBuilder→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- scripting.xmltags uses reflection, so a change to reflection can break scripting.xmltags, while a change to scripting.xmltags can't break reflection.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
38→35 scripting.xmltags uses mapping✕
- Connections
- 9 pairs of types, where a type in scripting.xmltags uses a type in mapping.
- The types involved
org.apache.ibatis.scripting.xmltags.DynamicContext→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.scripting.xmltags.DynamicSqlSource→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.scripting.xmltags.DynamicSqlSource→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.scripting.xmltags.FilteredDynamicContext→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.scripting.xmltags.PrefixedContext→org.apache.ibatis.mapping.ParameterMappingorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.scripting.xmltags.XMLLanguageDriver→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.scripting.xmltags.XMLScriptBuilder→org.apache.ibatis.mapping.SqlSource
- Direction
- scripting.xmltags uses mapping, so a change to mapping can break scripting.xmltags, while a change to scripting.xmltags can't break mapping.
- Position
- Below the diagonal: scripting.xmltags uses a module listed above it, which is the healthy direction.
39→1 session.defaults uses cursor✕
- Connections
- 1 pair of types, where a type in session.defaults uses a type in cursor.
- The types involved
org.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.cursor.Cursor
- Direction
- session.defaults uses cursor, so a change to cursor can break session.defaults, while a change to session.defaults can't break cursor.
- Position
- Below the diagonal: session.defaults uses a module listed above it, which is the healthy direction.
39→10 session.defaults uses transaction✕
- Connections
- 2 pairs of types, where a type in session.defaults uses a type in transaction.
- The types involved
org.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.transaction.Transactionorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.transaction.TransactionFactory
- Direction
- session.defaults uses transaction, so a change to transaction can break session.defaults, while a change to session.defaults can't break transaction.
- Position
- Below the diagonal: session.defaults uses a module listed above it, which is the healthy direction.
39→22 session.defaults uses executor✕
- Connections
- 3 pairs of types, where a type in session.defaults uses a type in executor.
- The types involved
org.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.executor.BatchResultorg.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.executor.Executororg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.executor.Executor
- Direction
- session.defaults uses executor, so a change to executor can break session.defaults, while a change to session.defaults can't break executor.
- Position
- Below the diagonal: session.defaults uses a module listed above it, which is the healthy direction.
39→27 session.defaults uses session✕
- Connections
- 9 pairs of types, where a type in session.defaults uses a type in session.
- The types involved
org.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.session.Configurationorg.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.session.ResultHandlerorg.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.session.RowBoundsorg.apache.ibatis.session.defaults.DefaultSqlSession→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.session.Configurationorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.session.ExecutorTypeorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.session.SqlSessionorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.session.SqlSessionFactoryorg.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.session.TransactionIsolationLevel
- Direction
- session.defaults uses session, so a change to session can break session.defaults, while a change to session.defaults can't break session.
- Position
- Below the diagonal: session.defaults uses a module listed above it, which is the healthy direction.
39→35 session.defaults uses mapping✕
- Connections
- 1 pair of types, where a type in session.defaults uses a type in mapping.
- The types involved
org.apache.ibatis.session.defaults.DefaultSqlSessionFactory→org.apache.ibatis.mapping.Environment
- Direction
- session.defaults uses mapping, so a change to mapping can break session.defaults, while a change to session.defaults can't break mapping.
- Position
- Below the diagonal: session.defaults uses a module listed above it, which is the healthy direction.
40→3 scripting.defaults uses executor.parameter✕
- Connections
- 1 pair of types, where a type in scripting.defaults uses a type in executor.parameter.
- The types involved
org.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.executor.parameter.ParameterHandler
- Direction
- scripting.defaults uses executor.parameter, so a change to executor.parameter can break scripting.defaults, while a change to scripting.defaults can't break executor.parameter.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→8 scripting.defaults uses parsing✕
- Connections
- 1 pair of types, where a type in scripting.defaults uses a type in parsing.
- The types involved
org.apache.ibatis.scripting.defaults.RawLanguageDriver→org.apache.ibatis.parsing.XNode
- Direction
- scripting.defaults uses parsing, so a change to parsing can break scripting.defaults, while a change to scripting.defaults can't break parsing.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→23 scripting.defaults uses type✕
- Connections
- 2 pairs of types, where a type in scripting.defaults uses a type in type.
- The types involved
org.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.type.JdbcTypeorg.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.type.TypeHandlerRegistry
- Direction
- scripting.defaults uses type, so a change to type can break scripting.defaults, while a change to scripting.defaults can't break type.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→27 scripting.defaults uses session✕
- Connections
- 3 pairs of types, where a type in scripting.defaults uses a type in session.
- The types involved
org.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.defaults.RawLanguageDriver→org.apache.ibatis.session.Configurationorg.apache.ibatis.scripting.defaults.RawSqlSource→org.apache.ibatis.session.Configuration
- Direction
- scripting.defaults uses session, so a change to session can break scripting.defaults, while a change to scripting.defaults can't break session.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→28 scripting.defaults uses reflection✕
- Connections
- 4 pairs of types, where a type in scripting.defaults uses a type in reflection.
- The types involved
org.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.reflection.MetaClassorg.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.reflection.MetaObjectorg.apache.ibatis.scripting.defaults.RawLanguageDriver→org.apache.ibatis.reflection.ParamNameResolverorg.apache.ibatis.scripting.defaults.RawSqlSource→org.apache.ibatis.reflection.ParamNameResolver
- Direction
- scripting.defaults uses reflection, so a change to reflection can break scripting.defaults, while a change to scripting.defaults can't break reflection.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→35 scripting.defaults uses mapping✕
- Connections
- 5 pairs of types, where a type in scripting.defaults uses a type in mapping.
- The types involved
org.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.scripting.defaults.DefaultParameterHandler→org.apache.ibatis.mapping.MappedStatementorg.apache.ibatis.scripting.defaults.RawLanguageDriver→org.apache.ibatis.mapping.SqlSourceorg.apache.ibatis.scripting.defaults.RawSqlSource→org.apache.ibatis.mapping.BoundSqlorg.apache.ibatis.scripting.defaults.RawSqlSource→org.apache.ibatis.mapping.SqlSource
- Direction
- scripting.defaults uses mapping, so a change to mapping can break scripting.defaults, while a change to scripting.defaults can't break mapping.
- Position
- Below the diagonal: scripting.defaults uses a module listed above it, which is the healthy direction.
40→38 scripting.defaults uses scripting.xmltags✕
- Connections
- 2 pairs of types, where a type in scripting.defaults uses a type in scripting.xmltags.
- The types involved
org.apache.ibatis.scripting.defaults.RawLanguageDriver→org.apache.ibatis.scripting.xmltags.XMLLanguageDriverorg.apache.ibatis.scripting.defaults.RawSqlSource→org.apache.ibatis.scripting.xmltags.SqlNode
- Direction
- scripting.defaults uses scripting.xmltags, so a change to scripting.xmltags can break scripting.defaults, while a change to scripting.defaults can't break scripting.xmltags.
- Position
- Below the diagonal: scripting.defaults 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: 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; Add a build/run (quick start) section to the root README — the first thing a newcomer needs; 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).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +6.4 pts | Medium | Architecture documentation |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +4.3 pts | Medium | Documentation (README) |
| Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with BatchExecutorTest.java, CachingBatchExecutorTest.java, CachingReuseExecutorTest.java. | +1.7 pts | Low | Test Quality |
| 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 |
| Resolve the 1 Banned license finding(s) in License Compliance. | +0.9 pts | Low | License Compliance |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +0.8 pts | Low | Bus Factor |
| Swallowed exception (caught, then discarded) | +1.3 pts | Medium | Exception handling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 5.7 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java | 7.0 | Mixed | Cognitive Complexity: EnhancedResultObjectProxyImpl.intercept (cognitive 18) |
| src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java | 7.0 | Mixed | Test Quality: No assertions: createInstanceWithAbstractClass |
| src/test/java/org/apache/ibatis/submitted/keygen/Jdbc3KeyGeneratorTest.java | 7.0 | Mixed | Test Quality: No assertions: shouldErrorUndefineProperty |
| src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java | 7.1 | Mixed | Code Duplication: Edited copy of a member (22 corresponding lines) |
| src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java | 7.1 | Mixed | Cyclomatic Complexity: PooledDataSource.popConnection (cyclomatic 22) |
| src/main/java/org/apache/ibatis/session/Configuration.java | 7.1 | Mixed | Cognitive Complexity: Configuration.checkGloballyForDiscriminatedNestedResultMaps (cognitive 16) |
| src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java | 7.1 | Mixed | Test Quality: No assertions: parseIsTwice |
| src/main/java/org/apache/ibatis/io/DefaultVFS.java | 7.2 | Mixed | Cyclomatic Complexity: DefaultVFS.list (cyclomatic 23) |
| src/main/java/org/apache/ibatis/reflection/Reflector.java | 7.2 | Mixed | Cognitive Complexity: Reflector.resolveGetterConflicts (cognitive 20) |
| src/test/java/org/apache/ibatis/submitted/lazyload_common_property/CommonPropertyLazyLoadTest.java | 7.2 | Mixed | Test Quality: No assertions: lazyLoadSkipFirstAncestor |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/test/java/org/apache/ibatis/submitted/typebasedtypehandlerresolution/CsvTypeHandler.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java | 7.4 | Mixed | Cyclomatic Complexity: ProviderSqlSource.<init> (cyclomatic 17) |
| src/main/java/org/apache/ibatis/binding/MapperMethod.java | 7.4 | Mixed | Cyclomatic Complexity: MapperMethod.execute (cyclomatic 16) |
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.8, 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, 270 of 296 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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 READ here — but this repository measures it: a coverage step in CI (`jacoco:report`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- 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. This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — 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. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — 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 the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D26 Project Cohesion — 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. `(repository root)` (35358 LoC, 359 module-visible types across 52 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 162 commits in the last 90 days, yet 109 of 136 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
- AX1 Captive dependencies — 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 reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in src/main/java/org/apache/ibatis/type/TypeAliasRegistry.java, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- C1 Data Protection — 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — 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. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — 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. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — 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 reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Java is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- S1 Web-Security Posture — 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X17 Uncapped recursion over a caller-supplied document — 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 reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- 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.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- 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.
- 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.
- 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
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DefaultParameterHandler.setParameters at 26.
What to do
- Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with DefaultParameterHandler.setParameters (cyclomatic 26), DefaultVFS.list (cyclomatic 23), PooledDataSource.popConnection (cyclomatic 22). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cyclomatic Complexity from 8.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
44 method(s) exceeded the cognitive complexity threshold of 15; the worst was DefaultParameterHandler.setParameters at 114.
What to do
- Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with DefaultParameterHandler.setParameters (cognitive 114), PooledDataSource.popConnection (cognitive 70), DefaultVFS.list (cognitive 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 5.9 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
18 god class(es) detected.
What to do
- Resolve the 12 TooManyMethods finding(s) in God Classes — start with Configuration.java, DefaultResultSetHandler.java, PooledDataSource.java. — One of this dimension's main actionable groups (12 warning-level).
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with DefaultResultSetHandler.java, Configuration.java, MapperAnnotationBuilder.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 FileTooLong finding(s) in God Classes — start with DefaultResultSetHandler.java, Configuration.java, MapperAnnotationBuilder.java. — One of this dimension's main actionable groups (3 warning-level).
D4 · Code Duplication
20 duplicated block group(s) detected. A further 40 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 6 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with TypeAliasRegistry.java, BatchExecutor.java, MapperMethod.java. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 4 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with Reflector.java, MapperAnnotationBuilder.java, SimpleExecutor.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with MapWrapper.java (2), ParameterExpression.java, CallableStatementHandler.java. — One of this dimension's main actionable groups (4 warning-level).
D6 · Cohesion (LCOM4)
1 of 107 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with BaseBuilder.java. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
10 skipped (10 with a documented reason), 73 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1939 tests.
What to do
- Resolve the 6 No assertions (empty test) finding(s) in Test Quality — start with BatchExecutorTest.java, CachingBatchExecutorTest.java, CachingReuseExecutorTest.java. — One of this dimension's main actionable groups (6 issue-level).
- Resolve the 67 No assertions finding(s) in Test Quality — start with XmlMapperBuilderTest.java (9), Jdbc3KeyGeneratorTest.java (7), XmlConfigBuilderTest.java (5). — One of this dimension's main actionable groups (67 warning-level).
D12 · Dependency Hygiene
15 outdated artifact(s) of 59 resolved by the build, graded against Maven Central. The poms themselves state a version for only 32 of 33 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
1 of 32 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 1 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java (4×26=104)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with DefaultParameterHandler.java. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
9 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java. Counted over 132 of the 393 production source files in this repository: 257 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
D17 · Explicit Debt
10 deducted task-comment markers across 35358 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 10 TodoComment finding(s) in Explicit Debt — start with MapperAnnotationBuilder.java (3), CsvTypeHandler.java (2), BaseExecutorTest.java. — One of this dimension's main actionable groups (10 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D27 · Navigability
70 % of calls cross a namespace and 21 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. semgrep hit a parse error in 1 file(s) — `mvnw` (lines 228–232, lines 284–288) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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 1 platform declaration(s) and 33 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
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
- `SqlSession` declares 30 abstract methods: `clearCache`, `close`, `commit`, `commit`, `delete`, `delete`, `flushStatements`, `getConfiguration`, `getConnection`, `getMapper`, `insert`, `insert`, `rollback`, `rollback`, `select`, `select`, `select`, `selectCursor`, `selectCursor`, `selectCursor`, `selectList`, `selectList`, `selectList`, `selectMap`, `selectMap`, `selectMap`, `selectOne`, `selectOne`, `update`, `update`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. Those 30 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/main/java/org/apache/ibatis/session/SqlSession.java:32
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×13) — src/test/java/org/apache/ibatis/builder/xsd/XmlConfigBuilderTest.java:61, src/test/java/org/apache/ibatis/builder/xsd/XmlMapperBuilderTest.java:30, src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:44, …
What to do
- Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
- 1 public type in `org.apache.ibatis.cache.impl` is marked as implementation by its own namespace, folder or name: `PerpetualCache` (src/main/java/org/apache/ibatis/cache/impl/PerpetualCache.java:27, `impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/cache/impl/PerpetualCache.java:27
- 1 public type in `org.apache.ibatis.logging.commons` is marked as implementation by its own namespace, folder or name: `JakartaCommonsLoggingImpl` (src/main/java/org/apache/ibatis/logging/commons/JakartaCommonsLoggingImpl.java:24, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/commons/JakartaCommonsLoggingImpl.java:24
- 1 public type in `org.apache.ibatis.logging.jdk14` is marked as implementation by its own namespace, folder or name: `Jdk14LoggingImpl` (src/main/java/org/apache/ibatis/logging/jdk14/Jdk14LoggingImpl.java:26, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/jdk14/Jdk14LoggingImpl.java:26
- 1 public type in `org.apache.ibatis.logging.log4j` is marked as implementation by its own namespace, folder or name: `Log4jImpl` (src/main/java/org/apache/ibatis/logging/log4j/Log4jImpl.java:28, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/log4j/Log4jImpl.java:28
- 3 public types in `org.apache.ibatis.logging.log4j2` are marked as implementation by their own namespace, folder or name: `Log4j2AbstractLoggerImpl` (src/main/java/org/apache/ibatis/logging/log4j2/Log4j2AbstractLoggerImpl.java:31, name ends in `Impl`), `Log4j2Impl` (src/main/java/org/apache/ibatis/logging/log4j2/Log4j2Impl.java:26, name ends in `Impl`), `Log4j2LoggerImpl` (src/main/java/org/apache/ibatis/logging/log4j2/Log4j2LoggerImpl.java:27, 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/main/java/org/apache/ibatis/logging/log4j2/Log4j2AbstractLoggerImpl.java:31
- 1 public type in `org.apache.ibatis.logging.nologging` is marked as implementation by its own namespace, folder or name: `NoLoggingImpl` (src/main/java/org/apache/ibatis/logging/nologging/NoLoggingImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/nologging/NoLoggingImpl.java:23
- 1 public type in `org.apache.ibatis.logging.slf4j` is marked as implementation by its own namespace, folder or name: `Slf4jImpl` (src/main/java/org/apache/ibatis/logging/slf4j/Slf4jImpl.java:28, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/slf4j/Slf4jImpl.java:28
- 1 public type in `org.apache.ibatis.logging.stdout` is marked as implementation by its own namespace, folder or name: `StdOutImpl` (src/main/java/org/apache/ibatis/logging/stdout/StdOutImpl.java:23, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — src/main/java/org/apache/ibatis/logging/stdout/StdOutImpl.java:23
What to do
- Hide `org.apache.ibatis.cache.impl` (`PerpetualCache`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.commons` (`JakartaCommonsLoggingImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.jdk14` (`Jdk14LoggingImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.log4j` (`Log4jImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.log4j2` (`Log4j2AbstractLoggerImpl`, `Log4j2Impl`, `Log4j2LoggerImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.nologging` (`NoLoggingImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.slf4j` (`Slf4jImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `org.apache.ibatis.logging.stdout` (`StdOutImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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.
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X20 · Mistyped argument guard
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:150, src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:158
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×8) — src/main/java/org/apache/ibatis/logging/LogFactory.java:100, src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:172, src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:202, …
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
X5 · Nullable reference types
- 0/52 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`.
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).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 65% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98% | Exemplary | Strongest area. |
| Maturity | 57% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 69% | Adequate | Acceptable, with room to improve. |
| Security | 71% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 3 check(s) recorded observations but carry no score
- D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 65 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean.
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- 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.
- D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
- 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.
- D5 Coupling — Not applicable — this Maven build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (38 value object(s))
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (48 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 48 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- P2 Observability — This repository's JVM source (1 module(s), 393 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X12 Unreachable branch — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X13 Undrained process stream — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- 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
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — 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 — 11 finding(s)
- No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/BatchExecutorTest.java:24
- No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingBatchExecutorTest.java:24
- No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingReuseExecutorTest.java:24
- No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingSimpleExecutorTest.java:24
- No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/ReuseExecutorTest.java:26
- No assertions (empty test): shouldInstantiatePropertyValue src/test/java/org/apache/ibatis/reflection/wrapper/BeanWrapperUnitTest.java:203
- Test declared unreliable: shouldParseFastOnJdk7u6 src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:101
- Banned license: com.mysql:mysql-connector-j
- REDACTED
- REDACTED
- REDACTED
Serious — 225 finding(s)
- No assertions: shouldFailWhenSelectingOneBlogWithNonExistentNestedParam src/test/java/org/apache/ibatis/binding/BindingTest.java:549
- No assertions: verifyErrorMessageFromInsertAfterSelectKey src/test/java/org/apache/ibatis/binding/BindingTest.java:170
- No assertions: verifyErrorMessageFromSelectKey src/test/java/org/apache/ibatis/binding/BindingTest.java:152
- No assertions: parseIsTwice src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:274
- No assertions: propertiesSpecifyResourceAndUrlAtSameTime src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:323
- No assertions: registerJavaTypeInitializingTypeHandler src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:158
- No assertions: unknownJavaTypeOnTypeHandler src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:305
- No assertions: unknownSettings src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:287
- No assertions: createInstanceWithAbstractClass src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:133
- No assertions: resolveClassWithNotFound src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:142
- No assertions: resolveJdbcTypeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:103
- No assertions: resolveParameterModeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:123
- No assertions: resolveResultSetTypeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:113
- No assertions: resolveTypeHandlerNoAssignable src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:161
- No assertions: setCurrentNamespaceValueIsNull src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:172
- No assertions: useCacheRefNamespaceIsNull src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:180
- No assertions: useCacheRefNamespaceIsUndefined src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:188
- No assertions: shouldKeepGenericTypes src/test/java/org/apache/ibatis/executor/loader/SerializableProxyTest.java:46
- No assertions: notSpecifyTimeout src/test/java/org/apache/ibatis/executor/statement/BaseStatementHandlerTest.java:61
- No assertions: changingDelimiterShouldNotCauseRunnerFail src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:142
- No assertions: commentAfterStatementDelimiterShouldNotCauseRunnerFail src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:112
- No assertions: initializingFailure src/test/java/org/apache/ibatis/mapping/CacheBuilderTest.java:41
- No assertions: shouldIgnoreBestMatchSetterIfGetterIsAmbiguous src/test/java/org/apache/ibatis/reflection/ReflectorTest.java:368
- No assertions: registerByInstanceNull src/test/java/org/apache/ibatis/scripting/LanguageDriverRegistryTest.java:90
- No assertions: registerByTypeDoesNotCreateNewInstance src/test/java/org/apache/ibatis/scripting/LanguageDriverRegistryTest.java:65
- TooManyMethods: Configuration src/main/java/org/apache/ibatis/session/Configuration.java:103
- TooManyMethods: DefaultResultSetHandler src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:81
- TooManyMethods: PooledDataSource src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:43
- TooManyMethods: SqlSessionManager src/main/java/org/apache/ibatis/session/SqlSessionManager.java:35
- TooManyMethods: AbstractSQL src/main/java/org/apache/ibatis/jdbc/AbstractSQL.java:32
- TooManyMethods: XNode src/main/java/org/apache/ibatis/parsing/XNode.java:33
- TooManyMethods: XPathParser REDACTED:47
- TooManyMethods: DefaultSqlSession src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSession.java:46
- TooManyMethods: TypeHandlerRegistry src/main/java/org/apache/ibatis/type/TypeHandlerRegistry.java:61
- TooManyMethods: UnpooledDataSource src/main/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSource.java:39
- TooManyMethods: Reflector src/main/java/org/apache/ibatis/reflection/Reflector.java:54
- TooManyMethods: MapperAnnotationBuilder src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:104
- TodoComment src/test/java/org/apache/ibatis/submitted/typebasedtypehandlerresolution/CsvTypeHandler.java:76
- TodoComment src/test/java/org/apache/ibatis/submitted/typebasedtypehandlerresolution/CsvTypeHandler.java:82
- TodoComment src/test/java/org/apache/ibatis/executor/BaseExecutorTest.java:340
- TodoComment src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:36
- TodoComment src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:594
- TodoComment src/main/java/org/apache/ibatis/executor/result/DefaultMapResultHandler.java:52
- TodoComment src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:93
- TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:293
- TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:306
- TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:410
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/logging/LogFactory.java:100
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:172
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:202
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/io/DefaultVFS.java:168
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:312
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:357
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:371
- Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:593
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/type/TypeAliasRegistry.java:135
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/executor/BatchExecutor.java:83
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/binding/MapperMethod.java:159
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSession.java:120
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/reflection/MetaClass.java:131
- Edited copy of a member (11 corresponding lines) src/main/java/org/apache/ibatis/executor/SimpleExecutor.java:43
- Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/reflection/Reflector.java:108
- Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:540
- Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/executor/SimpleExecutor.java:72
- Edited copy of a member (6 corresponding lines) src/main/java/org/apache/ibatis/binding/MapperMethod.java:208
- Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/builder/ParameterExpression.java:66
- Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/executor/statement/CallableStatementHandler.java:49
- Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java:53
- Edited copy of a member (9 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java:42
- Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java:37
- Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java:43
- Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/type/MonthTypeHandler.java:49
- Edited copy of a member (4 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:199
- Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:504
- Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:40
- Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:94
- Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:113
- ClassTooLong: DefaultResultSetHandler src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:81
- ClassTooLong: Configuration src/main/java/org/apache/ibatis/session/Configuration.java:103
- ClassTooLong: MapperAnnotationBuilder src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:104
- FileTooLong: resultset/DefaultResultSetHandler.java src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java
- FileTooLong: session/Configuration.java src/main/java/org/apache/ibatis/session/Configuration.java
- FileTooLong: annotation/MapperAnnotationBuilder.java src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java
- REDACTED
- REDACTED
- Edited copy of a member (19 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:501
- Edited copy of a member (19 corresponding lines) src/main/java/org/apache/ibatis/io/ClassLoaderWrapper.java:133
- Edited copy of a member (16 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/MapWrapper.java:79
- Edited copy of a member (16 corresponding lines) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:128
- Edited copy of a member (14 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BeanWrapper.java:186
- Edited copy of a member (14 corresponding lines) src/main/java/org/apache/ibatis/builder/xml/XMLMapperBuilder.java:336
- Edited copy of a member (10 corresponding lines) src/main/java/org/apache/ibatis/logging/jdbc/ResultSetLogger.java:92
- Edited copy of a member (10 corresponding lines) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:529
- Edited copy of a member (7 corresponding lines) src/main/java/org/apache/ibatis/reflection/Reflector.java:263
- Edited copy of a member (7 corresponding lines) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java:96
- Duplicated block (10 lines × 2) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1005
- Duplicated block (10 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:102
- Duplicated block (7 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:129
- Duplicated block (7 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:190
- Swallowed exception (caught, then discarded) src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:150
- Swallowed exception (caught, then discarded) src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:158
- DefaultParameterHandler.setParameters (cyclomatic 26) src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:95
- DefaultVFS.list (cyclomatic 23) src/main/java/org/apache/ibatis/io/DefaultVFS.java:58
- PooledDataSource.popConnection (cyclomatic 22) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:435
- MapperAnnotationBuilder.getReturnType (cyclomatic 21) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:444
- CacheBuilder.setCacheProperties (cyclomatic 21) src/main/java/org/apache/ibatis/mapping/CacheBuilder.java:142
- MapperAnnotationBuilder.parseStatement (cyclomatic 18) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:332
- ProviderSqlSource.<init> (cyclomatic 17) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:100
- DefaultResultSetHandler.handleRowValuesForNestedResultMap (cyclomatic 17) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1146
- MapperMethod.execute (cyclomatic 16) src/main/java/org/apache/ibatis/binding/MapperMethod.java:57
- DefaultVFS.findJarForResource (cyclomatic 16) src/main/java/org/apache/ibatis/io/DefaultVFS.java:234
- Builder.build (cyclomatic 16) src/main/java/org/apache/ibatis/mapping/ResultMap.java:89
- Hotspot: src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:95
- DefaultParameterHandler.setParameters (cognitive 114) src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:95
- PooledDataSource.popConnection (cognitive 70) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:435
- DefaultVFS.list (cognitive 64) src/main/java/org/apache/ibatis/io/DefaultVFS.java:58
- MapperAnnotationBuilder.getReturnType (cognitive 37) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:444
- DefaultResultSetHandler.createAutomaticMappings (cognitive 32) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:625
- ParamNameResolver.<init> (cognitive 32) src/main/java/org/apache/ibatis/reflection/ParamNameResolver.java:70
- MapperAnnotationBuilder.parseStatement (cognitive 30) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:332
- DefaultResultSetHandler.handleOutputParameters (cognitive 29) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:153
- TypeHandlerRegistry.getSmartHandler (cognitive 29) src/main/java/org/apache/ibatis/type/TypeHandlerRegistry.java:286
- ResultMappingConstructorResolver.filterBasedOnType (cognitive 28) src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:191
- DefaultResultSetHandler.applyNestedPendingConstructorCreations (cognitive 28) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1274
- DefaultResultSetHandler.applyNestedResultMappings (cognitive 28) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1401
- CacheBuilder.setCacheProperties (cognitive 28) src/main/java/org/apache/ibatis/mapping/CacheBuilder.java:142
- XMLStatementBuilder.parseStatementNode (cognitive 27) src/main/java/org/apache/ibatis/builder/xml/XMLStatementBuilder.java:71
- ProviderSqlSource.<init> (cognitive 26) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:100
- DefaultResultSetHandler.handleRowValuesForNestedResultMap (cognitive 26) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1146
- ProviderSqlSource.createSqlSource (cognitive 25) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:169
- Builder.build (cognitive 25) src/main/java/org/apache/ibatis/mapping/ResultMap.java:89
- GenericTokenParser.parse (cognitive 25) src/main/java/org/apache/ibatis/parsing/GenericTokenParser.java:33
- BaseExecutor.createCacheKey (cognitive 23) src/main/java/org/apache/ibatis/executor/BaseExecutor.java:199
- DefaultResultSetHandler.applyPropertyMappings (cognitive 22) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:545
- PreparedStatementLogger.invoke (cognitive 22) src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:44
- DefaultResultSetHandler.createParameterizedResultObject (cognitive 21) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:796
- DefaultResultSetHandler.linkNestedPendingCreations (cognitive 21) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1205
- TypeParameterResolver.scanSuperTypes (cognitive 21) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java:189
- PooledDataSource.pushConnection (cognitive 20) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:391
- DefaultResultSetHandler.applyArgNameBasedConstructorAutoMapping (cognitive 20) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:932
- DefaultResultSetHandler.createRowKeyForMappedProperties (cognitive 20) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1535
- DefaultVFS.findJarForResource (cognitive 20) src/main/java/org/apache/ibatis/io/DefaultVFS.java:234
- Reflector.resolveGetterConflicts (cognitive 20) src/main/java/org/apache/ibatis/reflection/Reflector.java:115
- PooledDataSource.pingConnection (cognitive 19) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:561
- TypeParameterResolver.resolveTypeVar (cognitive 19) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java:144
- ParameterMappingTokenHandler.buildParameterMapping (cognitive 18) src/main/java/org/apache/ibatis/builder/ParameterMappingTokenHandler.java:85
- ParameterMappingTokenHandler.figureOutJavaType (cognitive 18) src/main/java/org/apache/ibatis/builder/ParameterMappingTokenHandler.java:140
- SelectKeyGenerator.processGeneratedKeys (cognitive 18) src/main/java/org/apache/ibatis/executor/keygen/SelectKeyGenerator.java:58
- EnhancedResultObjectProxyImpl.intercept (cognitive 18) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:138
- EnhancedResultObjectProxyImpl.invoke (cognitive 18) src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:135
- DefaultResultSetHandler.getRowValue (cognitive 18) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:493
- SqlRunner.insert (cognitive 18) src/main/java/org/apache/ibatis/jdbc/SqlRunner.java:112
- MapperAnnotationBuilder.parse (cognitive 17) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:122
- XMLIncludeTransformer.applyIncludes (cognitive 17) src/main/java/org/apache/ibatis/builder/xml/XMLIncludeTransformer.java:61
- ConstructorMetaInfo.getArgNames (cognitive 17) src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:324
- ResultExtractor.extractObjectFromList (cognitive 16) src/main/java/org/apache/ibatis/executor/ResultExtractor.java:37
- Configuration.checkGloballyForDiscriminatedNestedResultMaps (cognitive 16) src/main/java/org/apache/ibatis/session/Configuration.java:1093
- Edited copy of a member (34 corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BaseWrapper.java:45
- Edited copies of one member (3 members, 30+ corresponding lines) src/main/java/org/apache/ibatis/reflection/ArrayUtil.java:33
- Edited copy of a member (40 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:138
- Edited copy of a member (21 corresponding lines) src/main/java/org/apache/ibatis/logging/jdbc/ConnectionLogger.java:44
- Edited copy of a member (26 corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:78
- Edited copy of a member (22 corresponding lines) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:69
- Edited copy of a member (15 corresponding lines) src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSessionFactory.java:95
- Edited copies of one member (6 members, 11+ corresponding lines) src/main/java/org/apache/ibatis/reflection/wrapper/BeanWrapper.java:83
- Edited copy of a member (8 corresponding lines) src/main/java/org/apache/ibatis/scripting/xmltags/ForEachSqlNode.java:134
- Edited copies of one member (4 members, 8+ corresponding lines) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:128
- Edited copies of one member (3 members, 15+ corresponding lines) src/main/java/org/apache/ibatis/session/Configuration.java:995
- Edited copies of one member (4 members, 9+ corresponding lines) src/main/java/org/apache/ibatis/builder/xml/XMLConfigBuilder.java:198
- Duplicated block (18–19 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:73
- Duplicated block (16 lines × 2) src/main/java/org/apache/ibatis/session/SqlSessionFactoryBuilder.java:48
- Duplicated block (13–15 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:82
- Duplicated block (12 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158
- Duplicated block (11 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:139
- Duplicated block (9–10 lines × 2) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:637
- Duplicated block (8–9 lines × 2) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:463
- Duplicated block (6–7 lines × 3) src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:54
- Duplicated block (79 lines × 2) src/main/java/org/apache/ibatis/jdbc/SelectBuilder.java:32
- Duplicated block (5 lines × 2) src/main/java/org/apache/ibatis/executor/BaseExecutor.java:135
- Duplicated block (9 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:117
- Duplicated block (5 lines × 3) src/main/java/org/apache/ibatis/logging/jdbc/ConnectionLogger.java:78
- Low cohesion: BaseBuilder (LCOM4 5) src/main/java/org/apache/ibatis/builder/BaseBuilder.java:35
- Coverage collected but not gated
Minor — 35 finding(s)
- Disabled test src/test/java/org/apache/ibatis/builder/xsd/XmlConfigBuilderTest.java:61
- Disabled test src/test/java/org/apache/ibatis/builder/xsd/XmlMapperBuilderTest.java:30
- Disabled test src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:44
- Disabled test src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:52
- Disabled test src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:101
- Disabled test src/test/java/org/apache/ibatis/submitted/collection_in_constructor/CollectionInConstructorTest.java:135
- Disabled test src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:68
- Disabled test src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:79
- Disabled test src/test/java/org/apache/ibatis/submitted/initialized_collection_property/AuthorDAOTest.java:56
- Disabled test src/test/java/org/apache/ibatis/submitted/lazyload_proxyfactory_comparison/JavassistLazyTest.java:20
- Disabled test src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:131
- Disabled test src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:151
- Disabled test src/test/java/org/apache/ibatis/submitted/timestamp_with_timezone/TimestampWithTimezoneTypeHandlerTest.java:78
- Implementation type on the public API src/main/java/org/apache/ibatis/cache/impl/PerpetualCache.java:27
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/commons/JakartaCommonsLoggingImpl.java:24
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/jdk14/Jdk14LoggingImpl.java:26
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/log4j/Log4jImpl.java:28
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/log4j2/Log4j2AbstractLoggerImpl.java:31
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/nologging/NoLoggingImpl.java:23
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/slf4j/Slf4jImpl.java:28
- Implementation type on the public API src/main/java/org/apache/ibatis/logging/stdout/StdOutImpl.java:23
- Duplicated predicate src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:464
- Duplicated predicate src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158
- Duplicated predicate src/main/java/org/apache/ibatis/builder/xml/XMLStatementBuilder.java:126
- Duplicated predicate src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:159
- Fat interface: SqlSession (30 abstract methods) src/main/java/org/apache/ibatis/session/SqlSession.java:32
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- Java packages are not null-marked everywhere
Minor — 25 finding(s)
- Skipped (documented): shouldRegisterDynamicallyLoadedDriver src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:46
- Skipped (documented): shouldRunScriptsBySendingFullScriptAtOnce src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:53
- Skipped (documented): shouldParseFastOnJdk7u6 src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:103
- Skipped (documented): testPartiallyImmutableObject src/test/java/org/apache/ibatis/submitted/collection_in_constructor/CollectionInConstructorTest.java:137
- Skipped (documented): shouldGetAllUsers_Annotated src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:69
- Skipped (documented): shouldGetFirstFourUsers_Annotated src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:80
- Skipped (documented): shouldNotOverwriteCollectionOnNestedQuery src/test/java/org/apache/ibatis/submitted/initialized_collection_property/AuthorDAOTest.java:58
- Skipped (documented): annotatedUpdateTable2WithGeneratedKey src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:132
- Skipped (documented): annotatedUpdateTable2WithGeneratedKeyXml src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:152
- Skipped (documented): shouldInsertOffsetTime src/test/java/org/apache/ibatis/submitted/timestamp_with_timezone/TimestampWithTimezoneTypeHandlerTest.java:80
- Outdated (compile (optional) -- module org.objectweb.asm): org.ow2.asm:asm
- Outdated (test -- module org.jspecify): org.jspecify:jspecify
- Outdated (test -- module org.objenesis [auto]): org.objenesis:objenesis
- Outdated (test -- module org.apache.commons.lang3): org.apache.commons:commons-lang3
- Outdated (test -- module org.checkerframework.checker.qual): org.checkerframework:checker-qual
- Outdated (test -- module com.google.protobuf [auto]): com.google.protobuf:protobuf-java
- Outdated (test -- module testcontainers (auto)): org.testcontainers:testcontainers
- Outdated (test -- module hamcrest.core (auto)): org.hamcrest:hamcrest-core
- Outdated (test -- module org.apache.commons.compress): org.apache.commons:commons-compress
- Outdated (test -- module org.jetbrains.annotations [auto]): org.jetbrains:annotations
- Outdated (test -- module com.github.dockerjava.api [auto]): com.github.docker-java:docker-java-api
- Outdated (test -- module com.fasterxml.jackson.annotation): com.fasterxml.jackson.core:jackson-annotations
- Outdated (test -- module com.github.dockerjava.transport.zerodep [auto]): com.github.docker-java:docker-java-transport-zerodep
- Outdated (test -- module com.github.dockerjava.transport [auto]): com.github.docker-java:docker-java-transport
- Outdated (test -- module com.sun.jna [auto]): net.java.dev.jna:jna
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c891aae8796143789ef117f6eeb762a3/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| 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-c891aae8796143789ef117f6eeb762a3/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| 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 . | 3 | artifacts/raw/semgrep.json |
| 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 . | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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 . | 0 | artifacts/raw/osv-scanner.json |