mybatis/mybatis-3

Executive summary

mybatis/mybatis-3 scores 61 out of 100 and is rated Adequate, while four of its five lenses score higher still: Architecture at 88, Code Health at 65 and Production Readiness at 64, all rated Adequate, and Security and Compliance at 86, rated Strong.

The score is lower than those four because the weakest lens counts most, and here that is Maturity, which scores 52 and is rated Adequate. Its Architecture documentation dimension scores 0 out of 10, and until that reaches 4, Maturity can't be rated higher than Adequate. The first actions are to resolve the 3 Documentation finding(s) in Documentation Quality and to record your significant design decisions, and if Maturity rose to 70, the score would rise from 61 to about 68.

Ten findings are critical: six in Test Quality, three in Static Analysis (SAST) and one in Test Reliability.

Watchdog couldn't measure 19 dimensions in this code, among them Code Coverage, Dependency Hygiene and License Compliance, so they are left out of the score. The product code is 35,307 lines, which would take an estimated 0.9 person-years, around €130,000, to rebuild.

Code Health 65 Adequate, capped by Nullable reference types Architecture 88 Adequate, capped by Project Cohesion Maturity 52 Adequate, capped by Architecture documentation Production Readiness 64 Adequate Security and Compliance 86 Strong

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Maturity 52 · counts for 47%Production Readiness 64 · counts for 26%Code Health 65 · counts for 14%Security and Compliance 86 · counts for 8%Architecture 88 · counts for 4%

If Maturity rose from 52 to 70, the lowest score rated Strong, the score would rise from 61 to about 68.

Code composition: what the lines of code are

Product code 35%Tests 65%

New since the last survey: 2 findings

These 2 critical or serious findings weren't in the previous survey, on 10 October 2026.

Test Quality · No assertions (empty test): shouldInstantiatePropertyValue src/test/java/org/apache/ibatis/reflection/wrapper/BeanWrapperUnitTest.java
Static Analysis (SAST) · REDACTED

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 68 findings

These 68 critical or serious findings were in the previous survey, on 10 October 2026, and are gone from this one.

Test Quality · No assertions: annotatedSubject src/test/java/org/apache/ibatis/autoconstructor/AutoConstructorTest.java
Test Quality · No assertions: extensiveSubject src/test/java/org/apache/ibatis/autoconstructor/AutoConstructorTest.java
Test Quality · No assertions: shouldReconnectWhenServerKilledLeakedConnection src/test/java/org/apache/ibatis/datasource/pooled/MysqlTimeoutTest.java
Test Quality · No assertions: shouldInstantiateAndThrowAllCustomExceptions src/test/java/org/apache/ibatis/exceptions/GeneralExceptionsTest.java
Test Quality · No assertions: shouldRunScriptsUsingConnection src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java
Test Quality · No assertions: shouldRunScriptsUsingProperties src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java
Test Quality · No assertions: constructorWithDocument src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithDocumentValidation src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithDocumentValidationVariables src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithDocumentValidationVariablesEntityResolver src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithInputStream src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithInputStreamValidation src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithInputStreamValidationVariables src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithInputStreamValidationVariablesEntityResolver src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithReader src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithReaderValidation src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithReaderValidationVariables src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithReaderValidationVariablesEntityResolver src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithString src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithStringValidation src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithStringValidationVariables src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: constructorWithStringValidationVariablesEntityResolver src/test/java/org/apache/ibatis/parsing/XPathParserTest.java
Test Quality · No assertions: shouldInstantiatePropertyValue src/test/java/org/apache/ibatis/reflection/wrapper/BeanWrapperUnitTest.java
Test Quality · No assertions: shouldGetArticles src/test/java/org/apache/ibatis/submitted/constructor_columnprefix/ConstructorColumnPrefixTest.java
Test Quality · No assertions: shouldGetArticlesAnno src/test/java/org/apache/ibatis/submitted/constructor_columnprefix/ConstructorColumnPrefixTest.java
Test Quality · No assertions: withNonEmptyList src/test/java/org/apache/ibatis/submitted/emptycollection/DaoTest.java
Test Quality · No assertions: withNonEmptyListNoCollectionId src/test/java/org/apache/ibatis/submitted/emptycollection/DaoTest.java
Test Quality · No assertions: shouldInvokingSetterInvalidateLazyLoading_Cglib src/test/java/org/apache/ibatis/submitted/lazy_properties/LazyPropertiesTest.java
Test Quality · No assertions: shouldInvokingSetterInvalidateLazyLoading_Javassist src/test/java/org/apache/ibatis/submitted/lazy_properties/LazyPropertiesTest.java
Test Quality · No assertions: nestedCursorAssociation src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursorConstructorAssociation src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursorsConstructorCollection src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursorsTypeHandler src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursorsTypeHandlerConstructor src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursors_Automap src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursors_Callable src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursors_Prepared src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: nestedCursors_Statement src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: shouldImplicitCursors_Callable src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: shouldImplicitCursors_Prepared src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: shouldImplicitCursors_Statement src/test/java/org/apache/ibatis/submitted/oracle_cursor/OracleCursorTest.java
Test Quality · No assertions: it src/test/java/org/apache/ibatis/submitted/quotedcolumnnames/QuotedColumnNamesTest.java
Test Quality · No assertions: itWithResultMap src/test/java/org/apache/ibatis/submitted/quotedcolumnnames/QuotedColumnNamesTest.java
Test Quality · No assertions: shouldUseDynamicSqlSourceForAnStatementWithInlineArguments src/test/java/org/apache/ibatis/submitted/raw_sql_source/RawSqlSourceTest.java
Test Quality · No assertions: shouldUseDynamicSqlSourceForAnStatementWithXmlTags src/test/java/org/apache/ibatis/submitted/raw_sql_source/RawSqlSourceTest.java
Test Quality · No assertions: shouldUseRawSqlSourceForAnStaticStatement src/test/java/org/apache/ibatis/submitted/raw_sql_source/RawSqlSourceTest.java
Test Quality · No assertions: withCallable src/test/java/org/apache/ibatis/submitted/result_set_type/ResultSetTypeTest.java
Test Quality · No assertions: withPrepared src/test/java/org/apache/ibatis/submitted/result_set_type/ResultSetTypeTest.java
Test Quality · No assertions: withStatement src/test/java/org/apache/ibatis/submitted/result_set_type/ResultSetTypeTest.java
Test Quality · No assertions: multipleCrossIncludeJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleCrossIncludeTest.java
Test Quality · No assertions: multipleCrossIncludeXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleCrossIncludeTest.java
Test Quality · No assertions: multipleIncludeJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleIncludeTest.java
Test Quality · No assertions: multipleIncludeXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleIncludeTest.java
Test Quality · No assertions: multipleReverseIncludeJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleReverseIncludeTest.java
Test Quality · No assertions: multipleReverseIncludeXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/MultipleReverseIncludeTest.java
Test Quality · No assertions: crossReferenceJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ParameterMapReferenceTest.java
Test Quality · No assertions: crossReferenceXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ParameterMapReferenceTest.java
Test Quality · No assertions: externalExtendsJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ResultMapExtendsTest.java
Test Quality · No assertions: externalExtendsXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ResultMapExtendsTest.java
Test Quality · No assertions: crossReferenceJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ResultMapReferenceTest.java
Test Quality · No assertions: crossReferenceXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ResultMapReferenceTest.java
Test Quality · No assertions: reverseIncludeJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ReverseIncludeTest.java
Test Quality · No assertions: reverseIncludeXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/ReverseIncludeTest.java
Test Quality · No assertions: crossReferenceJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/SameIdTest.java
Test Quality · No assertions: crossReferenceXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/SameIdTest.java
Test Quality · No assertions: crossReferenceJavaConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/XmlExternalRefTest.java
Test Quality · No assertions: crossReferenceXmlConfig src/test/java/org/apache/ibatis/submitted/xml_external_ref/XmlExternalRefTest.java
Test Quality · No assertions: setAutoCommitOnClose src/test/java/org/apache/ibatis/transaction/jdbc/JdbcTransactionTest.java

Rebuild cost: about €130,000 · Estimate

Cost to rebuild	€44,000 to €220,000, for 729 to 2,313 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.8 at a score of 61. 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,307 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3).

Raises the score by about 8 points · Low effort · Documentation Quality

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.

Raises the score by about 9 points · Medium effort · Architecture documentation

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.

Raises the score by about 5 points · Medium effort · Documentation (README)

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk

This code would cost about €130,000 to build again, about 0.9 person-years of work. Its weakest lens is Maturity, at 52 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.

Based on: the rebuild estimate · the Maturity grade · how much each lens counts

What to do: Start with the Maturity actions in Top priorities.

If you do one thing first · First action

Resolve the 3 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 8 points for low effort, because it clears the 3 Documentation Quality findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

52 modules, with 199 dependencies between them. 2 loops run through 22 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 12 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
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	31 binding	32 datasource.unpooled	34 executor.keygen	35 mapping	36 annotations	38 scripting.xmltags
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

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 65% · Adequate · gated by X5 ·

The Good

D1 · .NET / C# Cyclomatic Complexity 8.6 D3 · .NET / C# God Classes 8.4 D4 · .NET / C# Code Duplication 9.7 D17 · .NET / C# Explicit Debt 9.9 IC1 · Repo Incompleteness & stubs 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X20 · Repo Mistyped argument guard 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X26 · Repo Unsynchronised callback handoff 10.0 X27 · Repo Collection changed while being enumerated 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0 X4 · Repo Structured logging 10.0

The Bad

D2 · .NET / C# Cognitive Complexity 5.9 X3 · Repo Exception handling 6.8

The Ugly

X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 88% · Adequate · gated by D26 ·

The Good

D6 · .NET / C# Cohesion (LCOM4) 9.9 D27 · .NET / C# Navigability 9.0 D35 · .NET / C# Change Coupling 10.0 AX10 · Repo Code composition 9.7 AX3 · Repo Project dependency cycles 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 9.9

The Ugly

D26 · .NET / C# Project Cohesion 0.0

At a glance — Maturity · 52% · Adequate · gated by M2 ·

The Good

D15 · .NET / C# Churn × Complexity Hotspots 10.0 D16 · .NET / C# Bus Factor 9.5 D21 · .NET / C# Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 10.0

The Bad

M1 · Repo Documentation (README) 6.0

The Ugly

D19 · .NET / C# Documentation Quality 4.0 M2 · Repo Architecture documentation 0.0

At a glance — Readiness · 64% · Adequate ·

The Good

D9 · .NET / C# Test Distribution 10.0 D10 · .NET / C# Test Quality 9.4 D13 · .NET / C# Secret Scanning 10.0 P1 · Repo CI/CD gates 10.0 P3 · Repo Security & performance tooling 7.0

The Bad

P10 · Repo Library API & versioning 6.0 P4 · Repo Deployment & Rollback 5.0 P6 · Repo Release Hygiene 5.0

At a glance — Security · 86% · Strong ·

The Good

D28 · .NET / C# Secrets (history) 10.0 D44 · .NET / C# Platform End-of-Life 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Bad

D29 · .NET / C# Static Analysis (SAST) 6.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP category	Findings	Severity
A05:2025 — Injection	3	High / Critical

Roadmap

Begin by establishing architectural clarity through concise decision records in a dedicated folder and by fixing the three documentation quality issues, starting with the root README. Enhance the developer experience by adding a quick-start build section to the README and enforce null safety by applying default null-marked annotations across packages while resolving existing suppressions. Finally, improve test reliability by addressing the six empty test findings, prioritizing the batch and caching executor tests.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do this	Helps	Effort	Dimension
Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3).	+8.5 pts	Low	Documentation Quality
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.	+8.9 pts	Medium	Architecture documentation
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.	+5.1 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.5 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).	+3.0 pts	Medium	Nullable reference types
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor.	+0.6 pts	Low	Bus Factor
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.	+0.6 pts	Low	Bus Factor
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.	+1.1 pts	Medium	Deployment & Rollback

File quality

Per-file score 0–10 — a quality signature. Of 81 files carrying findings, judged against the Production bar: 0% slop · 44% mixed · 56% near-clean.

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
src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java	7.0	Mixed	Test Quality: No assertions: createInstanceWithAbstractClass
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/submitted/keygen/Jdbc3KeyGeneratorTest.java	7.0	Mixed	Test Quality: No assertions: shouldErrorUndefineProperty
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/cache/decorators/SoftCache.java	7.1	Mixed	Code Duplication: Duplicated block (18–19 lines × 2)
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/session/Configuration.java	7.2	Mixed	Cognitive Complexity: Configuration.checkGloballyForDiscriminatedNestedResultMaps (cognitive 16)
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/test/java/org/apache/ibatis/binding/BindingTest.java	7.4	Mixed	Test Quality: No assertions: shouldFailWhenSelectingOneBlogWithNonExistentNestedParam
src/test/java/org/apache/ibatis/scripting/LanguageDriverRegistryTest.java	7.4	Mixed	Test Quality: No assertions: registerByInstanceNull
src/test/java/org/apache/ibatis/session/SqlSessionTest.java	7.4	Mixed	Test Quality: No assertions: shouldCommitAnUnUsedSqlSession

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 10

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.

Serious — 182

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.

Minor — 39

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 20

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

Watchdog 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. 49 of 52 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.8 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 52 dimensions across the health lenses

D1D2D3D4D6D9D10D13D15D16D17D19D21D26D27D28D29D35D44AX10AX3AX5AX6IC1M1M2M3M4P1P10P3P4P6X14X15X16X18X19X20X21X22X23X24X25X26X27X28X29X3X30X4X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions

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, 222 of 231 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

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
Watchdog 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
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16cac-ba15-7082-9100-3a0aa41c46aa.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

D8 Code Coverage — not measured this run — Watchdog 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. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog 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 — not measured this run — Watchdog 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. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 32 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D22 Internal API Consistency — not measured this run — Watchdog 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 (pom.xml), 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.
D30 Dependency Vulnerabilities — not measured this run — Watchdog 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
D34 Knowledge Freshness — not measured this run — Watchdog 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: 110 commits in the last 90 days, yet 116 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.
D43 Malicious Dependencies — not measured this run — Watchdog 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. Osv: osv-scanner exited 127 with no findings — dependency CVEs were not measured. 'osv-scanner' exited 127 and produced no findings, and that exit code has no documented repo-side meaning — so this run measured nothing, and nothing here is a statement about the repository.
AX1 Captive dependencies — not measured this run — Watchdog 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/TypeHandlerRegistry.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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

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.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
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").
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
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").
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.
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: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.

The LLM boundary

LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity8.6 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Prevented

11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DefaultParameterHandler.setParameters at 25.

DefaultParameterHandler.setParameters (cyclomatic 25)src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:91

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

+ 6 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 11 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with DefaultParameterHandler.setParameters (cyclomatic 25), 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.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D2 · Cognitive Complexity5.9 / 10Adequate✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 5.9 / 10 · rule-coverage 100% · ceiling Prevented

44 method(s) exceeded the cognitive complexity threshold of 15; the worst was DefaultParameterHandler.setParameters at 108.

DefaultParameterHandler.setParameters (cognitive 108)src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:91

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

+ 39 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Bring the 6 bodies over 30 down to 30 or less in Cognitive Complexity — start with DefaultParameterHandler.setParameters (cognitive 108), 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.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D3 · God Classes8.4 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.4 / 10 · rule-coverage 100% · ceiling Prevented

18 god class(es) detected.

TooManyMethods: Configuration · ×12src/main/java/org/apache/ibatis/session/Configuration.java:103

ClassTooLong: DefaultResultSetHandler · ×3src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:81

FileTooLong: resultset/DefaultResultSetHandler.java · ×3src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java

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).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D4 · Code Duplication9.7 / 10Stronggated by 20 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Verified

20 duplicated block group(s) detected.

Duplicated block (6 lines × 2) · ×4src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:504

Duplicated block (10 lines × 2) · ×2src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1005

Duplicated block (7 lines × 2) · ×2src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:129

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

+ 10 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

Resolve the 4 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SoftCache.java (3), MapperAnnotationBuilder.java. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with DefaultResultSetHandler.java, SoftCache.java. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with CglibProxyFactory.java (2). — One of this dimension's main actionable groups (2 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

1 of 107 classes have LCOM4 above 3.

Low cohesion: BaseBuilder (LCOM4 5)src/main/java/org/apache/ibatis/builder/BaseBuilder.java:35

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).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1918 test methods: 1918 unit, 0 integration, 0 BDD, 0 e2e.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality9.4 / 10Adequategated by 6 critical findings✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.4 / 10 · rule-coverage 100% · ceiling Prevented

10 skipped (10 with a documented reason), 73 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1918 tests.

No assertions (empty test): dummy · ×6src/test/java/org/apache/ibatis/executor/BatchExecutorTest.java:24

No assertions: shouldFailWhenSelectingOneBlogWithNonExistentNestedParam · ×67src/test/java/org/apache/ibatis/binding/BindingTest.java:549

Skipped (documented): shouldRegisterDynamicallyLoadedDriver · ×10src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:46

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).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 9.5 / 10 · rule-coverage 100% · ceiling Documented

7 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 133 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 3 have no attributable history left to measure.

Off-boarding risk: anonymized user #1

Further sole-owners (lower concentration)

✓ On the Gold path — maintain.

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 10 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Prevented

10 deducted task-comment markers across 35307 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.

TodoComment · ×10src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:93

What to do

Resolve the 10 TodoComment finding(s) in Explicit Debt — start with MapperAnnotationBuilder.java (3), CsvTypeHandler.java (2), ResultMappingConstructorResolver.java. — One of this dimension's main actionable groups (10 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D19 · Documentation QualityWeak◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Weak / 10 · rule-coverage 100% · ceiling Documented

The repository's root README gives a strong overview (what MyBatis SQL mapper framework does) and links to build/coverage/QA badges plus Maven Central, SonarCloud, Stack Overflow, Open Hub, and the official docs site. It also briefly mentions test exclusion configuration but cuts before describing installation, usage examples, or contribution guidance.

Documentation: no installation or build instructions · ×3README.md

What to do

Resolve the 3 Documentation finding(s) in Documentation Quality — start with README.md (3). — One of this dimension's main actionable groups (3 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D26 · Project Cohesion0.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 1 build units (Maven) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D27 · Navigability9.0 / 10Strong✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Documented

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.

What to do

Improve Navigability — currently 9.0/10. — 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.

Detailed fixes: d27_recommendation.md.

Do you agree with this assessment?

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

Do you agree with this assessment?

D29 · Static Analysis (SAST)6.0 / 10Adequate✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

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.

REDACTED

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).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

What to do

The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.

Do you agree with this assessment?

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

`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.

Do you agree with this assessment?

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

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.

Do you agree with this assessment?

M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.

Do you agree with this assessment?

M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

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.

Do you agree with this assessment?

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

Do you agree with this assessment?

M4 · Documentation accuracy10.0 / 10Exemplary◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

Do you agree with this assessment?

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

Do you agree with this assessment?

P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

343/415 types (83%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

What to do

Keep implementation types off the public surface (Java: package-private (no modifier), or leave its package out of `module-info` exports) so internals can change without breaking consumers.

Do you agree with this assessment?

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

What to do

Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

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.

Do you agree with this assessment?

P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

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.

Do you agree with this assessment?

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X26 · Unsynchronised callback handoff10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.

Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X3 · Exception handling6.8 / 10Adequate✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

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/datasource/pooled/PooledDataSource.java:357, src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:371, src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:593, …
`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

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

Do you agree with this assessment?

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

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).

Do you agree with this assessment?

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

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	88%	Adequate — gated by D26	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	52%	Adequate — gated by M2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	64%	Adequate	Acceptable, with room to improve.
Security	86%	Strong	Strongest area.

Unscored — 3 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

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

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

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 — 61 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

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.
AC7 A11y enforcement — 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.
D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 32 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — Not scored — this repository's 32 declared JVM dependency coordinate(s) were read from its 1 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 32 of them (HTTP 429 Too Many Requests from https://repo1.maven.org/maven2/ognl/ognl/3.4.17/ognl-3.4.17.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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.
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+ projects each declaring an entity of their own. 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 — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Scanner failed to run — not a clean result
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
D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).
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.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D43 Malicious Dependencies — Scanner failed to run — not a clean result
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 — no coverage report found on disk — produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 pom.xml, 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 applicable: allocation awareness is rated where code engineers for it — at least 400 production lines that ship benchmarks or already use allocation-aware idioms (8 or more). This repository's Java code has 40,009 production line(s), 0 such use(s) and no benchmarks, so there is no allocation work to rate. The card is reward-only: its absence costs nothing.
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
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
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
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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 10 finding(s)

D10 · Test Quality · No assertions (empty test) · ×6

No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/BatchExecutorTest.java:24 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingBatchExecutorTest.java:24 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingReuseExecutorTest.java:24 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/CachingSimpleExecutorTest.java:24 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): dummy src/test/java/org/apache/ibatis/executor/ReuseExecutorTest.java:26 — Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): shouldInstantiatePropertyValue src/test/java/org/apache/ibatis/reflection/wrapper/BeanWrapperUnitTest.java:203 — Test method has an empty body — it asserts nothing and exercises no code.

D11 · Test Reliability · Test declared unreliable · ×1

Test declared unreliable: shouldParseFastOnJdk7u6 src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:101 — This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Because it randomly fails on Github CI. It could be useful during development.". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

Serious — 182 finding(s)

D10 · Test Quality · No assertions · ×67

No assertions: shouldFailWhenSelectingOneBlogWithNonExistentNestedParam src/test/java/org/apache/ibatis/binding/BindingTest.java:549 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: verifyErrorMessageFromInsertAfterSelectKey src/test/java/org/apache/ibatis/binding/BindingTest.java:170 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: verifyErrorMessageFromSelectKey src/test/java/org/apache/ibatis/binding/BindingTest.java:152 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: parseIsTwice src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:272 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: propertiesSpecifyResourceAndUrlAtSameTime src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:321 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: registerJavaTypeInitializingTypeHandler src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:157 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: unknownJavaTypeOnTypeHandler src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:303 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: unknownSettings src/test/java/org/apache/ibatis/builder/XmlConfigBuilderTest.java:285 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createInstanceWithAbstractClass src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:133 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resolveClassWithNotFound src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:142 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resolveJdbcTypeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:103 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resolveParameterModeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:123 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resolveResultSetTypeWithUndefinedValue src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:113 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: resolveTypeHandlerNoAssignable src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:161 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: setCurrentNamespaceValueIsNull src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:172 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: useCacheRefNamespaceIsNull src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:180 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: useCacheRefNamespaceIsUndefined src/test/java/org/apache/ibatis/builder/XmlMapperBuilderTest.java:188 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldKeepGenericTypes src/test/java/org/apache/ibatis/executor/loader/SerializableProxyTest.java:45 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: notSpecifyTimeout src/test/java/org/apache/ibatis/executor/statement/BaseStatementHandlerTest.java:61 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: changingDelimiterShouldNotCauseRunnerFail src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:150 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: commentAfterStatementDelimiterShouldNotCauseRunnerFail src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:116 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: initializingFailure src/test/java/org/apache/ibatis/mapping/CacheBuilderTest.java:41 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: shouldIgnoreBestMatchSetterIfGetterIsAmbiguous src/test/java/org/apache/ibatis/reflection/ReflectorTest.java:368 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: registerByInstanceNull src/test/java/org/apache/ibatis/scripting/LanguageDriverRegistryTest.java:90 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: registerByTypeDoesNotCreateNewInstance src/test/java/org/apache/ibatis/scripting/LanguageDriverRegistryTest.java:65 — This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
+ 42 more in this group — see findings.md.

D3 · God Classes · TooManyMethods · ×12

TooManyMethods: Configuration src/main/java/org/apache/ibatis/session/Configuration.java:103 — TooManyMethods — 143 methods. The bar is 30 methods; this is 113 over it, 4.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DefaultResultSetHandler src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:81 — TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PooledDataSource src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:43 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SqlSessionManager src/main/java/org/apache/ibatis/session/SqlSessionManager.java:35 — TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AbstractSQL src/main/java/org/apache/ibatis/jdbc/AbstractSQL.java:32 — TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XNode src/main/java/org/apache/ibatis/parsing/XNode.java:33 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: XPathParser REDACTED:47 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DefaultSqlSession src/main/java/org/apache/ibatis/session/defaults/DefaultSqlSession.java:46 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: UnpooledDataSource src/main/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSource.java:39 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Reflector src/main/java/org/apache/ibatis/reflection/Reflector.java:54 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TypeHandlerRegistry src/main/java/org/apache/ibatis/type/TypeHandlerRegistry.java:61 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MapperAnnotationBuilder src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:104 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D17 · Explicit Debt · TodoComment · ×10

TodoComment src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:93 — // todo: AutoMapping works during runtime, we cannot resolve constructors yet — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:293 — // TODO add AutoMappingBehaviour — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:306 — // TODO add AutoMappingBehaviour — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:410 — // TODO gcode issue #577
TodoComment src/main/java/org/apache/ibatis/executor/result/DefaultMapResultHandler.java:52 — // TODO is that assignment always true? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:594 — // TODO is that OK? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:36 — // TODO Rename to 'configuration' after removing the 'configuration' property(deprecated property) on parent class — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/test/java/org/apache/ibatis/executor/BaseExecutorTest.java:340 — // TODO see issue #464. Fail is OK.
TodoComment src/test/java/org/apache/ibatis/submitted/typebasedtypehandlerresolution/CsvTypeHandler.java:76 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/test/java/org/apache/ibatis/submitted/typebasedtypehandlerresolution/CsvTypeHandler.java:82 — // TODO Auto-generated method stub — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

X3 · Exception handling · Swallowed exception (empty catch) · ×8

Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:357 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:371 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:593 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:312 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/io/DefaultVFS.java:168 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:172 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/jdbc/ScriptRunner.java:202 — 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.
Swallowed exception (empty catch) src/main/java/org/apache/ibatis/logging/LogFactory.java:100 — 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.

D4 · Code Duplication · Duplicated block (6 lines × 2) · ×4

Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:504 — src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:504-509 | src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:581-586 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:580` calls `add` and `src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:503` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:40 — src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:40-45 | src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java:40-45 — before extracting anything, compare `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java` and `src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:94 — src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:94-99 | src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java:93-98 — before extracting anything, compare `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java` and `src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:113 — src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:113-118 | src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java:112-117 — before extracting anything, compare `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java` and `src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D3 · God Classes · ClassTooLong · ×3

ClassTooLong: DefaultResultSetHandler src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:81 — ClassTooLong — 1034 significant lines (blank, comment-only and punctuation-only lines excluded), 73 methods. The bar is 400 significant lines; this is 634 over it, 2.59× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Configuration src/main/java/org/apache/ibatis/session/Configuration.java:103 — ClassTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), 143 methods. The bar is 400 significant lines; this is 151 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MapperAnnotationBuilder src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:104 — ClassTooLong — 470 significant lines (blank, comment-only and punctuation-only lines excluded), 34 methods. The bar is 400 significant lines; this is 70 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

D3 · God Classes · FileTooLong · ×3

FileTooLong: resultset/DefaultResultSetHandler.java src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java — FileTooLong — 1089 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: DefaultResultSetHandler (81-1662). The bar is 500 significant lines; this is 589 over it, 2.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: session/Configuration.java src/main/java/org/apache/ibatis/session/Configuration.java — FileTooLong — 632 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: Configuration (103-1200). The bar is 500 significant lines; this is 132 over it, 1.26× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: annotation/MapperAnnotationBuilder.java src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java — FileTooLong — 551 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: MapperAnnotationBuilder (104-773). The bar is 500 significant lines; this is 51 over it, 1.10× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

D4 · Code Duplication · Duplicated block (10 lines × 2) · ×2

Duplicated block (10 lines × 2) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1005 — src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1005-1014 | src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1026-1035 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1005` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:102 — src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:102-111 | src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java:101-110 — before extracting anything, compare `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java` and `src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.

D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2

Duplicated block (7 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:129 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:129-135 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:126-132 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:190 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:190-196 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:187-193 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×2

Swallowed exception (caught, then discarded) src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:150 — `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.
Swallowed exception (caught, then discarded) src/main/java/org/apache/ibatis/type/UnknownTypeHandler.java:158 — `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.

D1 · Cyclomatic Complexity · DefaultParameterHandler.setParameters (cyclomatic 25) · ×1

DefaultParameterHandler.setParameters (cyclomatic 25) src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:91 — DefaultParameterHandler.setParameters has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DefaultVFS.list (cyclomatic 23) · ×1

DefaultVFS.list (cyclomatic 23) src/main/java/org/apache/ibatis/io/DefaultVFS.java:58 — DefaultVFS.list has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · PooledDataSource.popConnection (cyclomatic 22) · ×1

PooledDataSource.popConnection (cyclomatic 22) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:435 — PooledDataSource.popConnection has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MapperAnnotationBuilder.getReturnType (cyclomatic 21) · ×1

MapperAnnotationBuilder.getReturnType (cyclomatic 21) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:444 — MapperAnnotationBuilder.getReturnType has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CacheBuilder.setCacheProperties (cyclomatic 21) · ×1

CacheBuilder.setCacheProperties (cyclomatic 21) src/main/java/org/apache/ibatis/mapping/CacheBuilder.java:142 — CacheBuilder.setCacheProperties has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MapperAnnotationBuilder.parseStatement (cyclomatic 18) · ×1

MapperAnnotationBuilder.parseStatement (cyclomatic 18) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:332 — MapperAnnotationBuilder.parseStatement has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · ProviderSqlSource.<init> (cyclomatic 17) · ×1

ProviderSqlSource.<init> (cyclomatic 17) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:100 — ProviderSqlSource.<init> has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DefaultResultSetHandler.handleRowValuesForNestedResultMap (cyclomatic 17) · ×1

DefaultResultSetHandler.handleRowValuesForNestedResultMap (cyclomatic 17) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1146 — DefaultResultSetHandler.handleRowValuesForNestedResultMap has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · MapperMethod.execute (cyclomatic 16) · ×1

MapperMethod.execute (cyclomatic 16) src/main/java/org/apache/ibatis/binding/MapperMethod.java:57 — MapperMethod.execute has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · DefaultVFS.findJarForResource (cyclomatic 16) · ×1

DefaultVFS.findJarForResource (cyclomatic 16) src/main/java/org/apache/ibatis/io/DefaultVFS.java:234 — DefaultVFS.findJarForResource has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · Builder.build (cyclomatic 16) · ×1

Builder.build (cyclomatic 16) src/main/java/org/apache/ibatis/mapping/ResultMap.java:89 — Builder.build has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D2 · Cognitive Complexity · DefaultParameterHandler.setParameters (cognitive 108) · ×1

DefaultParameterHandler.setParameters (cognitive 108) src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java:91 — DefaultParameterHandler.setParameters has cognitive complexity 108 (threshold 15). Drivers by points: if/else 23 (88 pts), error handling 2 (12 pts), ternaries 1 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 79). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · PooledDataSource.popConnection (cognitive 70) · ×1

PooledDataSource.popConnection (cognitive 70) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:435 — PooledDataSource.popConnection has cognitive complexity 70 (threshold 15). Drivers by points: if/else 21 (60 pts), error handling 2 (9 pts), loops 1 (nesting depth added 46). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · DefaultVFS.list (cognitive 64) · ×1

DefaultVFS.list (cognitive 64) src/main/java/org/apache/ibatis/io/DefaultVFS.java:58 — DefaultVFS.list has cognitive complexity 64 (threshold 15). Drivers by points: if/else 18 (49 pts), loops 3 (8 pts), error handling 3 (7 pts) (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · MapperAnnotationBuilder.getReturnType (cognitive 37) · ×1

MapperAnnotationBuilder.getReturnType (cognitive 37) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:444 — MapperAnnotationBuilder.getReturnType has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (33 pts), boolean chains 4 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · DefaultResultSetHandler.createAutomaticMappings (cognitive 32) · ×1

DefaultResultSetHandler.createAutomaticMappings (cognitive 32) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:625 — DefaultResultSetHandler.createAutomaticMappings has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (23 pts), ternaries 1 (4 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ParamNameResolver.<init> (cognitive 32) · ×1

ParamNameResolver.<init> (cognitive 32) src/main/java/org/apache/ibatis/reflection/ParamNameResolver.java:70 — ParamNameResolver.<init> has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (29 pts), loops 2 (3 pts) (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · MapperAnnotationBuilder.parseStatement (cognitive 30) · ×1

MapperAnnotationBuilder.parseStatement (cognitive 30) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:332 — MapperAnnotationBuilder.parseStatement has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), ternaries 5 (11 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.handleOutputParameters (cognitive 29) · ×1

DefaultResultSetHandler.handleOutputParameters (cognitive 29) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:153 — DefaultResultSetHandler.handleOutputParameters has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (26 pts), boolean chains 2, loops 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · TypeHandlerRegistry.getSmartHandler (cognitive 29) · ×1

TypeHandlerRegistry.getSmartHandler (cognitive 29) src/main/java/org/apache/ibatis/type/TypeHandlerRegistry.java:286 — TypeHandlerRegistry.getSmartHandler has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (21 pts), ternaries 1 (4 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · ResultMappingConstructorResolver.filterBasedOnType (cognitive 28) · ×1

ResultMappingConstructorResolver.filterBasedOnType (cognitive 28) src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:191 — ResultMappingConstructorResolver.filterBasedOnType has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (21 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.applyNestedPendingConstructorCreations (cognitive 28) · ×1

DefaultResultSetHandler.applyNestedPendingConstructorCreations (cognitive 28) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1274 — DefaultResultSetHandler.applyNestedPendingConstructorCreations has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (22 pts), error handling 1 (2 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.applyNestedResultMappings (cognitive 28) · ×1

DefaultResultSetHandler.applyNestedResultMappings (cognitive 28) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1401 — DefaultResultSetHandler.applyNestedResultMappings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), error handling 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 17). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · CacheBuilder.setCacheProperties (cognitive 28) · ×1

CacheBuilder.setCacheProperties (cognitive 28) src/main/java/org/apache/ibatis/mapping/CacheBuilder.java:142 — CacheBuilder.setCacheProperties has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 7, error handling 1 (2 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · XMLStatementBuilder.parseStatementNode (cognitive 27) · ×1

XMLStatementBuilder.parseStatementNode (cognitive 27) src/main/java/org/apache/ibatis/builder/xml/XMLStatementBuilder.java:71 — XMLStatementBuilder.parseStatementNode has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ProviderSqlSource.<init> (cognitive 26) · ×1

ProviderSqlSource.<init> (cognitive 26) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:100 — ProviderSqlSource.<init> has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (4 pts), loops 2 (3 pts), boolean chains 2, error handling 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.handleRowValuesForNestedResultMap (cognitive 26) · ×1

DefaultResultSetHandler.handleRowValuesForNestedResultMap (cognitive 26) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1146 — DefaultResultSetHandler.handleRowValuesForNestedResultMap has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ProviderSqlSource.createSqlSource (cognitive 25) · ×1

ProviderSqlSource.createSqlSource (cognitive 25) src/main/java/org/apache/ibatis/builder/annotation/ProviderSqlSource.java:169 — ProviderSqlSource.createSqlSource has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 6 (9 pts), error handling 2, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Builder.build (cognitive 25) · ×1

Builder.build (cognitive 25) src/main/java/org/apache/ibatis/mapping/ResultMap.java:89 — Builder.build has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · GenericTokenParser.parse (cognitive 25) · ×1

GenericTokenParser.parse (cognitive 25) src/main/java/org/apache/ibatis/parsing/GenericTokenParser.java:33 — GenericTokenParser.parse has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · BaseExecutor.createCacheKey (cognitive 23) · ×1

BaseExecutor.createCacheKey (cognitive 23) src/main/java/org/apache/ibatis/executor/BaseExecutor.java:199 — BaseExecutor.createCacheKey has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.applyPropertyMappings (cognitive 22) · ×1

DefaultResultSetHandler.applyPropertyMappings (cognitive 22) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:545 — DefaultResultSetHandler.applyPropertyMappings has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PreparedStatementLogger.invoke (cognitive 22) · ×1

PreparedStatementLogger.invoke (cognitive 22) src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:44 — PreparedStatementLogger.invoke has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 2 (5 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.createParameterizedResultObject (cognitive 21) · ×1

DefaultResultSetHandler.createParameterizedResultObject (cognitive 21) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:796 — DefaultResultSetHandler.createParameterizedResultObject has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.linkNestedPendingCreations (cognitive 21) · ×1

DefaultResultSetHandler.linkNestedPendingCreations (cognitive 21) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1205 — DefaultResultSetHandler.linkNestedPendingCreations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeParameterResolver.scanSuperTypes (cognitive 21) · ×1

TypeParameterResolver.scanSuperTypes (cognitive 21) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java:189 — TypeParameterResolver.scanSuperTypes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 1 (5 pts), loops 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D2 · Cognitive Complexity · PooledDataSource.pushConnection (cognitive 20) · ×1

PooledDataSource.pushConnection (cognitive 20) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:391 — PooledDataSource.pushConnection has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (19 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.applyArgNameBasedConstructorAutoMapping (cognitive 20) · ×1

DefaultResultSetHandler.applyArgNameBasedConstructorAutoMapping (cognitive 20) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:932 — DefaultResultSetHandler.applyArgNameBasedConstructorAutoMapping has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.createRowKeyForMappedProperties (cognitive 20) · ×1

DefaultResultSetHandler.createRowKeyForMappedProperties (cognitive 20) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1535 — DefaultResultSetHandler.createRowKeyForMappedProperties has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (17 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultVFS.findJarForResource (cognitive 20) · ×1

DefaultVFS.findJarForResource (cognitive 20) src/main/java/org/apache/ibatis/io/DefaultVFS.java:234 — DefaultVFS.findJarForResource has cognitive complexity 20 (threshold 15). Drivers by points: if/else 12 (16 pts), error handling 2 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · Reflector.resolveGetterConflicts (cognitive 20) · ×1

Reflector.resolveGetterConflicts (cognitive 20) src/main/java/org/apache/ibatis/reflection/Reflector.java:115 — Reflector.resolveGetterConflicts has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · PooledDataSource.pingConnection (cognitive 19) · ×1

PooledDataSource.pingConnection (cognitive 19) src/main/java/org/apache/ibatis/datasource/pooled/PooledDataSource.java:561 — PooledDataSource.pingConnection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 3 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · TypeParameterResolver.resolveTypeVar (cognitive 19) · ×1

TypeParameterResolver.resolveTypeVar (cognitive 19) src/main/java/org/apache/ibatis/reflection/TypeParameterResolver.java:144 — TypeParameterResolver.resolveTypeVar has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ParameterMappingTokenHandler.buildParameterMapping (cognitive 18) · ×1

ParameterMappingTokenHandler.buildParameterMapping (cognitive 18) src/main/java/org/apache/ibatis/builder/ParameterMappingTokenHandler.java:85 — ParameterMappingTokenHandler.buildParameterMapping has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 2, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · ParameterMappingTokenHandler.figureOutJavaType (cognitive 18) · ×1

ParameterMappingTokenHandler.figureOutJavaType (cognitive 18) src/main/java/org/apache/ibatis/builder/ParameterMappingTokenHandler.java:140 — ParameterMappingTokenHandler.figureOutJavaType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SelectKeyGenerator.processGeneratedKeys (cognitive 18) · ×1

SelectKeyGenerator.processGeneratedKeys (cognitive 18) src/main/java/org/apache/ibatis/executor/keygen/SelectKeyGenerator.java:58 — SelectKeyGenerator.processGeneratedKeys has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · EnhancedResultObjectProxyImpl.intercept (cognitive 18) · ×1

EnhancedResultObjectProxyImpl.intercept (cognitive 18) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:138 — EnhancedResultObjectProxyImpl.intercept has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · EnhancedResultObjectProxyImpl.invoke (cognitive 18) · ×1

EnhancedResultObjectProxyImpl.invoke (cognitive 18) src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:135 — EnhancedResultObjectProxyImpl.invoke has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, error handling 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · DefaultResultSetHandler.getRowValue (cognitive 18) · ×1

DefaultResultSetHandler.getRowValue (cognitive 18) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:493 — DefaultResultSetHandler.getRowValue has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 6, ternaries 1 (3 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · SqlRunner.insert (cognitive 18) · ×1

SqlRunner.insert (cognitive 18) src/main/java/org/apache/ibatis/jdbc/SqlRunner.java:112 — SqlRunner.insert has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 2 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · MapperAnnotationBuilder.parse (cognitive 17) · ×1

MapperAnnotationBuilder.parse (cognitive 17) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:122 — MapperAnnotationBuilder.parse has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · XMLIncludeTransformer.applyIncludes (cognitive 17) · ×1

XMLIncludeTransformer.applyIncludes (cognitive 17) src/main/java/org/apache/ibatis/builder/xml/XMLIncludeTransformer.java:61 — XMLIncludeTransformer.applyIncludes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 3 (7 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ConstructorMetaInfo.getArgNames (cognitive 17) · ×1

ConstructorMetaInfo.getArgNames (cognitive 17) src/main/java/org/apache/ibatis/builder/ResultMappingConstructorResolver.java:324 — ConstructorMetaInfo.getArgNames has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ResultExtractor.extractObjectFromList (cognitive 16) · ×1

ResultExtractor.extractObjectFromList (cognitive 16) src/main/java/org/apache/ibatis/executor/ResultExtractor.java:37 — ResultExtractor.extractObjectFromList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, loops 1 (3 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D2 · Cognitive Complexity · Configuration.checkGloballyForDiscriminatedNestedResultMaps (cognitive 16) · ×1

Configuration.checkGloballyForDiscriminatedNestedResultMaps (cognitive 16) src/main/java/org/apache/ibatis/session/Configuration.java:1078 — Configuration.checkGloballyForDiscriminatedNestedResultMaps has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.

D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×1

Duplicated block (18–19 lines × 2) src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:73 — src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:73-91 | src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java:73-90 — before extracting anything, compare `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java` and `src/main/java/org/apache/ibatis/cache/decorators/WeakCache.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/cache/decorators/SoftCache.java:73` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.

D4 · Code Duplication · Duplicated block (16 lines × 2) · ×1

Duplicated block (16 lines × 2) src/main/java/org/apache/ibatis/session/SqlSessionFactoryBuilder.java:48 — src/main/java/org/apache/ibatis/session/SqlSessionFactoryBuilder.java:48-63 | src/main/java/org/apache/ibatis/session/SqlSessionFactoryBuilder.java:78-93 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.

D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1

Duplicated block (13–15 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:82 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:82-94 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:77-91 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:95` calls `isEmpty`, `create` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:92` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (12 lines × 2) · ×1

Duplicated block (12 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158-169 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:155-166 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (11 lines × 2) · ×1

Duplicated block (11 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:139 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:139-149 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:136-146 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (9–10 lines × 2) · ×1

Duplicated block (9–10 lines × 2) src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:637 — src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:637-646 | src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:1564-1572 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:637` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.

D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×1

Duplicated block (8–9 lines × 2) src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:463 — src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:463-470 | src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:479-487 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:463` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.

D4 · Code Duplication · Duplicated block (5–6 lines × 3) · ×1

Duplicated block (5–6 lines × 3) src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:55 — src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:55-60 | src/main/java/org/apache/ibatis/logging/jdbc/StatementLogger.java:53-58 | src/main/java/org/apache/ibatis/logging/jdbc/StatementLogger.java:60-64 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/logging/jdbc/PreparedStatementLogger.java:55` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (79 lines × 2) · ×1

Duplicated block (79 lines × 2) src/main/java/org/apache/ibatis/jdbc/SelectBuilder.java:32 — src/main/java/org/apache/ibatis/jdbc/SelectBuilder.java:32-110 | src/main/java/org/apache/ibatis/jdbc/SqlBuilder.java:32-130 — before extracting anything, compare `src/main/java/org/apache/ibatis/jdbc/SelectBuilder.java` and `src/main/java/org/apache/ibatis/jdbc/SqlBuilder.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1

Duplicated block (5 lines × 2) src/main/java/org/apache/ibatis/executor/BaseExecutor.java:135 — src/main/java/org/apache/ibatis/executor/BaseExecutor.java:135-139 | src/main/java/org/apache/ibatis/executor/CachingExecutor.java:87-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/org/apache/ibatis/executor/BaseExecutor.java:141` calls `SuppressWarnings` and `src/main/java/org/apache/ibatis/executor/CachingExecutor.java:93` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.

D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1

Duplicated block (9 lines × 2) src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:117 — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:117-125 | src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java:114-122 — before extracting anything, compare `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java` and `src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 61 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:117` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.

D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1

Duplicated block (5 lines × 3) src/main/java/org/apache/ibatis/logging/jdbc/ConnectionLogger.java:78 — src/main/java/org/apache/ibatis/logging/jdbc/ConnectionLogger.java:78-82 | src/main/java/org/apache/ibatis/logging/jdbc/ResultSetLogger.java:132-136 | src/main/java/org/apache/ibatis/logging/jdbc/StatementLogger.java:82-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: BaseBuilder (LCOM4 5) src/main/java/org/apache/ibatis/builder/BaseBuilder.java:35 — BaseBuilder's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

P12 · CI test-gate honesty · Coverage collected but not gated · ×1

Coverage collected but not gated — CI collects a coverage report but no step enforces a minimum — coverage could halve and CI stays green. Add a step that fails the build when coverage drops below a floor (your coverage tool's minimum-threshold flag, or a coverage-gate action) so the number guards something. What was searched, so you can tell an absence from a miss: this repository's CI files AND its coverage configuration — the well-known coverage and test-runner config files, read at the repository root and inside workspace package directories two levels down, so a floor declared beside the tests rather than in the pipeline is credited — matched against the threshold settings this check knows by name. A floor set in your coverage service's web UI rather than in a committed file, or under a setting whose name is not one of those, is not seen here.

Minor — 29 finding(s)

IC1 · Incompleteness & stubs · Disabled test · ×13

Disabled test src/test/java/org/apache/ibatis/builder/xsd/XmlConfigBuilderTest.java:61 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/builder/xsd/XmlMapperBuilderTest.java:30 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:44 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:52 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:101 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/collection_in_constructor/CollectionInConstructorTest.java:135 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:68 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:79 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/initialized_collection_property/AuthorDAOTest.java:56 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/lazyload_proxyfactory_comparison/JavassistLazyTest.java:20 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:131 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:151 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test src/test/java/org/apache/ibatis/submitted/timestamp_with_timezone/TimestampWithTimezoneTypeHandlerTest.java:78 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.

X10 · Duplicated predicate · Duplicated predicate · ×4

Duplicated predicate src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java:464 — `actualTypeArguments != null && actualTypeArguments.length == 1` appears character-identically in 2 files — src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java, src/main/java/org/apache/ibatis/reflection/MetaClass.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java:158 — `aggressive || lazyLoadTriggerMethods.contains(methodName)` appears character-identically in 2 files — src/main/java/org/apache/ibatis/executor/loader/cglib/CglibProxyFactory.java, src/main/java/org/apache/ibatis/executor/loader/javassist/JavassistProxyFactory.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/main/java/org/apache/ibatis/builder/xml/XMLStatementBuilder.java:126 — `configuration.isUseGeneratedKeys() && SqlCommandType.INSERT.equals(sqlCommandType)` appears character-identically in 2 files — src/main/java/org/apache/ibatis/builder/xml/XMLStatementBuilder.java, src/main/java/org/apache/ibatis/mapping/MappedStatement.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java:159 — `parameterMapping.getMode() == ParameterMode.OUT || parameterMapping.getMode() == ParameterMode.INOUT` appears character-identically in 2 files — src/main/java/org/apache/ibatis/executor/resultset/DefaultResultSetHandler.java, src/main/java/org/apache/ibatis/executor/statement/CallableStatementHandler.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.

D19 · Documentation Quality · Documentation · ×3

Documentation: no installation or build instructions README.md — The README states nothing about how to install MyBatis (Maven dependency, Gradle plugin, or download) and no setup steps for a new project. Add an Install section covering Maven/Gradle dependency lines and any required configuration.
Documentation: no usage examples README.md — There are no runnable examples showing how to configure MyBatis with XML or annotations, nor a 'how to run it' example. Add a Usage section with an annotated Hello World that shows both XML and annotation configuration.
Documentation: no contributor guidance README.md — The README links only to CONTRIBUTING.md but does not explain what the repository is for or how to get started contributing. Add a short Contributing section explaining the scope of work and any required PR/CI steps.

AX6 · Interface segregation · Fat interface · ×1

Fat interface: SqlSession (30 abstract methods) src/main/java/org/apache/ibatis/session/SqlSession.java:32 — `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.

D16 · Bus Factor · Off-boarding risk · ×1

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 4 significant file(s) lose their only recent owner: src/main/java/org/apache/ibatis/scripting/defaults/DefaultParameterHandler.java, src/main/java/org/apache/ibatis/builder/ParameterMappingTokenHandler.java, src/main/java/org/apache/ibatis/builder/BaseBuilder.java, src/main/java/org/apache/ibatis/io/SerialFilterChecker.java. Pair on, review, or document these before any departure.

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (7 single-owned of 133 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 133 of the 393 production source files in this repository met that bar). They are anonymized user #2 (2 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/main/java/org/apache/ibatis/builder/annotation/MapperAnnotationBuilder.java, src/main/java/org/apache/ibatis/annotations/NamedResultMap.java, src/main/java/org/apache/ibatis/io/Resources.java.

D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1

Projects may be oversized for their cohesion — 1 of 1 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `(repository root)` (35307 LoC, 359 module-visible types across 52 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.

M2 · Architecture documentation · No ADRs · ×1

No ADRs — 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.

M2 · Architecture documentation · No architecture diagram/doc · ×1

No architecture diagram/doc — 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.

P10 · Library API & versioning · Large public API surface · ×1

Large public API surface — 343/415 types (83%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.

P6 · Release Hygiene · No changelog · ×1

No changelog — 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.)

X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1

Java packages are not null-marked everywhere — 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`.

Minor — 10 finding(s)

D10 · Test Quality · Skipped (documented) · ×10

Skipped (documented): shouldRegisterDynamicallyLoadedDriver src/test/java/org/apache/ibatis/datasource/unpooled/UnpooledDataSourceTest.java:46 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldRunScriptsBySendingFullScriptAtOnce src/test/java/org/apache/ibatis/jdbc/ScriptRunnerTest.java:53 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldParseFastOnJdk7u6 src/test/java/org/apache/ibatis/parsing/GenericTokenParserTest.java:103 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): testPartiallyImmutableObject src/test/java/org/apache/ibatis/submitted/collection_in_constructor/CollectionInConstructorTest.java:137 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldGetAllUsers_Annotated src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:69 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldGetFirstFourUsers_Annotated src/test/java/org/apache/ibatis/submitted/duplicate_statements/DuplicateStatementsTest.java:80 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldNotOverwriteCollectionOnNestedQuery src/test/java/org/apache/ibatis/submitted/initialized_collection_property/AuthorDAOTest.java:58 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): annotatedUpdateTable2WithGeneratedKey src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:132 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): annotatedUpdateTable2WithGeneratedKeyXml src/test/java/org/apache/ibatis/submitted/selectkey/SelectKeyTest.java:152 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled
Skipped (documented): shouldInsertOffsetTime src/test/java/org/apache/ibatis/submitted/timestamp_with_timezone/TimestampWithTimezoneTypeHandlerTest.java:80 — Skipped with a documented reason — a deferral, not lazy debt: switched off by @Disabled

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-57b72bbe7a16401392c63c47f642310d/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/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-57b72bbe7a16401392c63c47f642310d/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	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 .	0	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	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release).	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

Run 01a16cac-ba15-7082-9100-3a0aa41c46aa · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture: which parts of the code depend on which

At a glance — Code Health · 65% · Adequate · gated by X5 ·

At a glance — Architecture · 88% · Adequate · gated by D26 ·

At a glance — Maturity · 52% · Adequate · gated by M2 ·

At a glance — Readiness · 64% · Adequate ·

At a glance — Security · 86% · Strong ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts