Executive summary
SpaiR/imgui-java falls short of our standard for production because its Git mining dimensions are rated Critical, and 43 files are no longer known to anyone active in the project. It scores 55.4 out of 100, which alone would earn Adequate, but it is rated Weak: a rating can't sit more than one step above its weakest group.
Maturity, at 47.2, is the weakest lens and counts most in the score. The best first step is having someone learn and document the 43 files no active contributor knows, worth about 9.0 points. Recording design decisions comes next, worth about 6.7 points. Raising Maturity to 70 would lift the score to about 62.8.
Seventeen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks. The two inner parts of the code that depend on an outer part need turning around so they point inward.
The product code is 77,988 lines, about €79,000 to rebuild.
If Maturity rose from 47.2 to 70, the lowest score rated Strong, the score would rise from 55.4 to about 62.8.
Rebuild cost: about €79,000 · Estimate
| Cost to rebuild | €26,000 to €130,000, for 440 to 1,395 hours of work, about 0.5 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 55. 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: 77,988 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 assertion | 2 binding | 3 binding.annotation | 4 extension.imguifiledialog.callback | 5 extension.imguifiledialog.flag | 6 extension.imguiknobs.flag | 7 extension.imguizmo.flag | 8 extension.imnodes.flag | 9 extension.implot.flag | 10 extension.nodeditor.flag | 11 extension.texteditor.flag | 12 flag | 13 internal.flag | 14 lwjgl3.glfw | 15 type | 16 callback | 17 extension.imguiknobs | 18 extension.memedit | 19 internal | 20 imgui | 21 extension.imguifiledialog | 22 extension.imguizmo | 23 extension.imnodes | 24 extension.implot | 25 extension.nodeditor | 26 extension.texteditor | 27 gl3 | 28 glfw | 29 sdl3 | 30 app |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 assertion | ||||||||||||||||||||||||||||||
| 2 binding | ||||||||||||||||||||||||||||||
| 3 binding.annotation | ||||||||||||||||||||||||||||||
| 4 extension.imguifiledialog.callback | ||||||||||||||||||||||||||||||
| 5 extension.imguifiledialog.flag | ||||||||||||||||||||||||||||||
| 6 extension.imguiknobs.flag | ||||||||||||||||||||||||||||||
| 7 extension.imguizmo.flag | ||||||||||||||||||||||||||||||
| 8 extension.imnodes.flag | ||||||||||||||||||||||||||||||
| 9 extension.implot.flag | ||||||||||||||||||||||||||||||
| 10 extension.nodeditor.flag | ||||||||||||||||||||||||||||||
| 11 extension.texteditor.flag | ||||||||||||||||||||||||||||||
| 12 flag | ||||||||||||||||||||||||||||||
| 13 internal.flag | ||||||||||||||||||||||||||||||
| 14 lwjgl3.glfw | ||||||||||||||||||||||||||||||
| 15 type | ||||||||||||||||||||||||||||||
| 16 callback | 9 | |||||||||||||||||||||||||||||
| 17 extension.imguiknobs | 2 | |||||||||||||||||||||||||||||
| 18 extension.memedit | 2 | |||||||||||||||||||||||||||||
| 19 internal | 3 | 3 | 10 | |||||||||||||||||||||||||||
| 20 imgui | 2 | 19 | 7 | 11 | 4 | |||||||||||||||||||||||||
| 21 extension.imguifiledialog | 1 | 1 | ||||||||||||||||||||||||||||
| 22 extension.imguizmo | 1 | 2 | ||||||||||||||||||||||||||||
| 23 extension.imnodes | 4 | 2 | 1 | 2 | ||||||||||||||||||||||||||
| 24 extension.implot | 4 | 3 | 1 | 8 | ||||||||||||||||||||||||||
| 25 extension.nodeditor | 3 | 1 | 5 | |||||||||||||||||||||||||||
| 26 extension.texteditor | 2 | 2 | 1 | 1 | ||||||||||||||||||||||||||
| 27 gl3 | 1 | 3 | ||||||||||||||||||||||||||||
| 28 glfw | 18 | 21 | ||||||||||||||||||||||||||||
| 29 sdl3 | 4 | 2 | ||||||||||||||||||||||||||||
| 30 app | 1 | 1 | 4 |
16→20 callback uses imgui part of a loop✕
- Connections
- 9 pairs of types, where a type in callback uses a type in imgui.
- The types involved
imgui.callback.ImPlatformFuncViewport→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportFloat→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportImVec2→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportImVec2→imgui.ImVec2imgui.callback.ImPlatformFuncViewportString→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportSuppBoolean→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportSuppFloat→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportSuppImVec2→imgui.ImGuiViewportimgui.callback.ImPlatformFuncViewportSuppImVec2→imgui.ImVec2
- Direction
- callback uses imgui, so a change to imgui can break callback, while a change to callback can't break imgui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→15 extension.imguiknobs uses type✕
- Connections
- 2 pairs of types, where a type in extension.imguiknobs uses a type in type.
- The types involved
imgui.extension.imguiknobs.ImGuiKnobs→imgui.type.ImFloatimgui.extension.imguiknobs.ImGuiKnobs→imgui.type.ImInt
- Direction
- extension.imguiknobs uses type, so a change to type can break extension.imguiknobs, while a change to extension.imguiknobs can't break type.
- Position
- Below the diagonal: extension.imguiknobs uses a module listed above it, which is the healthy direction.
18→2 extension.memedit uses binding✕
- Connections
- 2 pairs of types, where a type in extension.memedit uses a type in binding.
- The types involved
imgui.extension.memedit.MemoryEditor→imgui.binding.ImGuiStructDestroyableimgui.extension.memedit.MemoryEditorSizes→imgui.binding.ImGuiStructDestroyable
- Direction
- extension.memedit uses binding, so a change to binding can break extension.memedit, while a change to extension.memedit can't break binding.
- Position
- Below the diagonal: extension.memedit uses a module listed above it, which is the healthy direction.
19→2 internal uses binding✕
- Connections
- 3 pairs of types, where a type in internal uses a type in binding.
- The types involved
imgui.internal.ImGuiContext→imgui.binding.ImGuiStructimgui.internal.ImGuiDockNode→imgui.binding.ImGuiStructimgui.internal.ImGuiWindow→imgui.binding.ImGuiStruct
- Direction
- internal uses binding, so a change to binding can break internal, while a change to internal can't break binding.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
19→15 internal uses type✕
- Connections
- 3 pairs of types, where a type in internal uses a type in type.
- The types involved
imgui.internal.ImGui→imgui.type.ImBooleanimgui.internal.ImGui→imgui.type.ImFloatimgui.internal.ImGui→imgui.type.ImInt
- Direction
- internal uses type, so a change to type can break internal, while a change to internal can't break type.
- Position
- Below the diagonal: internal uses a module listed above it, which is the healthy direction.
19→20 internal uses imgui part of a loop✕
- Connections
- 10 pairs of types, where a type in internal uses a type in imgui.
- The types involved
imgui.internal.ImGui→imgui.ImDrawListimgui.internal.ImGui→imgui.ImFontimgui.internal.ImGui→imgui.ImGuiimgui.internal.ImGui→imgui.ImGuiPlatformMonitorimgui.internal.ImGui→imgui.ImGuiViewportimgui.internal.ImGui→imgui.ImVec2imgui.internal.ImGui→imgui.ImVec4imgui.internal.ImGuiDockNode→imgui.ImGuiWindowClassimgui.internal.ImGuiDockNode→imgui.ImVec2imgui.internal.ImRect→imgui.ImVec2
- Direction
- internal uses imgui, so a change to imgui can break internal, while a change to internal can't break imgui.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 imgui uses assertion✕
- Connections
- 2 pairs of types, where a type in imgui uses a type in assertion.
- The types involved
imgui.1→imgui.assertion.ImAssertCallbackimgui.ImGui→imgui.assertion.ImAssertCallback
- Direction
- imgui uses assertion, so a change to assertion can break imgui, while a change to imgui can't break assertion.
- Position
- Below the diagonal: imgui uses a module listed above it, which is the healthy direction.
20→2 imgui uses binding✕
- Connections
- 19 pairs of types, where a type in imgui uses a type in binding.
- The types involved
imgui.ImDrawData→imgui.binding.ImGuiStructimgui.ImDrawList→imgui.binding.ImGuiStructimgui.ImFont→imgui.binding.ImGuiStructDestroyableimgui.ImFontAtlas→imgui.binding.ImGuiStructDestroyableimgui.ImFontConfig→imgui.binding.ImGuiStructDestroyableimgui.ImFontGlyph→imgui.binding.ImGuiStructDestroyableimgui.ImGuiIO→imgui.binding.ImGuiStructimgui.ImGuiInputTextCallbackData→imgui.binding.ImGuiStructimgui.ImGuiKeyData→imgui.binding.ImGuiStructDestroyableimgui.ImGuiListClipper→imgui.binding.ImGuiStructDestroyableimgui.ImGuiPlatformIO→imgui.binding.ImGuiStructimgui.ImGuiPlatformMonitor→imgui.binding.ImGuiStructimgui.ImGuiStorage→imgui.binding.ImGuiStructDestroyableimgui.ImGuiStyle→imgui.binding.ImGuiStructDestroyableimgui.ImGuiTableColumnSortSpecs→imgui.binding.ImGuiStructimgui.ImGuiTableSortSpecs→imgui.binding.ImGuiStructimgui.ImGuiTextFilter→imgui.binding.ImGuiStructDestroyableimgui.ImGuiViewport→imgui.binding.ImGuiStructimgui.ImGuiWindowClass→imgui.binding.ImGuiStructDestroyable
- Direction
- imgui uses binding, so a change to binding can break imgui, while a change to imgui can't break binding.
- Position
- Below the diagonal: imgui uses a module listed above it, which is the healthy direction.
20→15 imgui uses type✕
- Connections
- 7 pairs of types, where a type in imgui uses a type in type.
- The types involved
imgui.ImFontAtlas→imgui.type.ImIntimgui.ImGui→imgui.type.ImBooleanimgui.ImGui→imgui.type.ImDoubleimgui.ImGui→imgui.type.ImFloatimgui.ImGui→imgui.type.ImIntimgui.ImGui→imgui.type.ImStringimgui.ImGui→imgui.type.InputData
- Direction
- imgui uses type, so a change to type can break imgui, while a change to imgui can't break type.
- Position
- Below the diagonal: imgui uses a module listed above it, which is the healthy direction.
20→16 imgui uses callback✕
- Connections
- 11 pairs of types, where a type in imgui uses a type in callback.
- The types involved
imgui.ImGui→imgui.callback.ImGuiInputTextCallbackimgui.ImGuiIO→imgui.callback.ImStrConsumerimgui.ImGuiIO→imgui.callback.ImStrSupplierimgui.ImGuiListClipper→imgui.callback.ImListClipperCallbackimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportFloatimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportImVec2imgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportStringimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportSuppBooleanimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportSuppFloatimgui.ImGuiPlatformIO→imgui.callback.ImPlatformFuncViewportSuppImVec2
- Direction
- imgui uses callback, so a change to callback can break imgui, while a change to imgui can't break callback.
- Position
- Below the diagonal: imgui uses a module listed above it, which is the healthy direction.
20→19 imgui uses internal✕
- Connections
- 4 pairs of types, where a type in imgui uses a type in internal.
- The types involved
imgui.ImGui→imgui.internal.ImGuiContextimgui.ImGuiIO→imgui.internal.ImGuiContextimgui.ImGuiInputTextCallbackData→imgui.internal.ImGuiContextimgui.ImGuiListClipper→imgui.internal.ImGuiContext
- Direction
- imgui uses internal, so a change to internal can break imgui, while a change to imgui can't break internal.
- Position
- Below the diagonal: imgui uses a module listed above it, which is the healthy direction.
21→4 extension.imguifiledialog uses extension.imguifiledialog.callback✕
- Connections
- 1 pair of types, where a type in extension.imguifiledialog uses a type in extension.imguifiledialog.callback.
- The types involved
imgui.extension.imguifiledialog.ImGuiFileDialog→imgui.extension.imguifiledialog.callback.ImGuiFileDialogPaneFun
- Direction
- extension.imguifiledialog uses extension.imguifiledialog.callback, so a change to extension.imguifiledialog.callback can break extension.imguifiledialog, while a change to extension.imguifiledialog can't break extension.imguifiledialog.callback.
- Position
- Below the diagonal: extension.imguifiledialog uses a module listed above it, which is the healthy direction.
21→20 extension.imguifiledialog uses imgui✕
- Connections
- 1 pair of types, where a type in extension.imguifiledialog uses a type in imgui.
- The types involved
imgui.extension.imguifiledialog.ImGuiFileDialog→imgui.ImVec2
- Direction
- extension.imguifiledialog uses imgui, so a change to imgui can break extension.imguifiledialog, while a change to extension.imguifiledialog can't break imgui.
- Position
- Below the diagonal: extension.imguifiledialog uses a module listed above it, which is the healthy direction.
22→19 extension.imguizmo uses internal✕
- Connections
- 1 pair of types, where a type in extension.imguizmo uses a type in internal.
- The types involved
imgui.extension.imguizmo.ImGuizmo→imgui.internal.ImGuiContext
- Direction
- extension.imguizmo uses internal, so a change to internal can break extension.imguizmo, while a change to extension.imguizmo can't break internal.
- Position
- Below the diagonal: extension.imguizmo uses a module listed above it, which is the healthy direction.
22→20 extension.imguizmo uses imgui✕
- Connections
- 2 pairs of types, where a type in extension.imguizmo uses a type in imgui.
- The types involved
imgui.extension.imguizmo.ImGuizmo→imgui.ImDrawListimgui.extension.imguizmo.ImGuizmo→imgui.ImVec2
- Direction
- extension.imguizmo uses imgui, so a change to imgui can break extension.imguizmo, while a change to extension.imguizmo can't break imgui.
- Position
- Below the diagonal: extension.imguizmo uses a module listed above it, which is the healthy direction.
23→2 extension.imnodes uses binding✕
- Connections
- 4 pairs of types, where a type in extension.imnodes uses a type in binding.
- The types involved
imgui.extension.imnodes.ImNodesContext→imgui.binding.ImGuiStructimgui.extension.imnodes.ImNodesEditorContext→imgui.binding.ImGuiStructimgui.extension.imnodes.ImNodesIO→imgui.binding.ImGuiStructimgui.extension.imnodes.ImNodesStyle→imgui.binding.ImGuiStruct
- Direction
- extension.imnodes uses binding, so a change to binding can break extension.imnodes, while a change to extension.imnodes can't break binding.
- Position
- Below the diagonal: extension.imnodes uses a module listed above it, which is the healthy direction.
23→15 extension.imnodes uses type✕
- Connections
- 2 pairs of types, where a type in extension.imnodes uses a type in type.
- The types involved
imgui.extension.imnodes.ImNodes→imgui.type.ImBooleanimgui.extension.imnodes.ImNodes→imgui.type.ImInt
- Direction
- extension.imnodes uses type, so a change to type can break extension.imnodes, while a change to extension.imnodes can't break type.
- Position
- Below the diagonal: extension.imnodes uses a module listed above it, which is the healthy direction.
23→19 extension.imnodes uses internal✕
- Connections
- 1 pair of types, where a type in extension.imnodes uses a type in internal.
- The types involved
imgui.extension.imnodes.ImNodes→imgui.internal.ImGuiContext
- Direction
- extension.imnodes uses internal, so a change to internal can break extension.imnodes, while a change to extension.imnodes can't break internal.
- Position
- Below the diagonal: extension.imnodes uses a module listed above it, which is the healthy direction.
23→20 extension.imnodes uses imgui✕
- Connections
- 2 pairs of types, where a type in extension.imnodes uses a type in imgui.
- The types involved
imgui.extension.imnodes.ImNodes→imgui.ImVec2imgui.extension.imnodes.ImNodesStyle→imgui.ImVec2
- Direction
- extension.imnodes uses imgui, so a change to imgui can break extension.imnodes, while a change to extension.imnodes can't break imgui.
- Position
- Below the diagonal: extension.imnodes uses a module listed above it, which is the healthy direction.
24→2 extension.implot uses binding✕
- Connections
- 4 pairs of types, where a type in extension.implot uses a type in binding.
- The types involved
imgui.extension.implot.ImPlotContext→imgui.binding.ImGuiStructimgui.extension.implot.ImPlotInputMap→imgui.binding.ImGuiStructDestroyableimgui.extension.implot.ImPlotSpec→imgui.binding.ImGuiStructDestroyableimgui.extension.implot.ImPlotStyle→imgui.binding.ImGuiStructDestroyable
- Direction
- extension.implot uses binding, so a change to binding can break extension.implot, while a change to extension.implot can't break binding.
- Position
- Below the diagonal: extension.implot uses a module listed above it, which is the healthy direction.
24→15 extension.implot uses type✕
- Connections
- 3 pairs of types, where a type in extension.implot uses a type in type.
- The types involved
imgui.extension.implot.ImPlot→imgui.type.ImBooleanimgui.extension.implot.ImPlot→imgui.type.ImDoubleimgui.extension.implot.ImPlot→imgui.type.ImFloat
- Direction
- extension.implot uses type, so a change to type can break extension.implot, while a change to extension.implot can't break type.
- Position
- Below the diagonal: extension.implot uses a module listed above it, which is the healthy direction.
24→19 extension.implot uses internal✕
- Connections
- 1 pair of types, where a type in extension.implot uses a type in internal.
- The types involved
imgui.extension.implot.ImPlot→imgui.internal.ImGuiContext
- Direction
- extension.implot uses internal, so a change to internal can break extension.implot, while a change to extension.implot can't break internal.
- Position
- Below the diagonal: extension.implot uses a module listed above it, which is the healthy direction.
24→20 extension.implot uses imgui✕
- Connections
- 8 pairs of types, where a type in extension.implot uses a type in imgui.
- The types involved
imgui.extension.implot.ImPlot→imgui.ImDrawListimgui.extension.implot.ImPlot→imgui.ImVec2imgui.extension.implot.ImPlot→imgui.ImVec4imgui.extension.implot.ImPlotPoint→imgui.ImVec2imgui.extension.implot.ImPlotRect→imgui.ImVec2imgui.extension.implot.ImPlotSpec→imgui.ImVec4imgui.extension.implot.ImPlotStyle→imgui.ImVec2imgui.extension.implot.ImPlotStyle→imgui.ImVec4
- Direction
- extension.implot uses imgui, so a change to imgui can break extension.implot, while a change to extension.implot can't break imgui.
- Position
- Below the diagonal: extension.implot uses a module listed above it, which is the healthy direction.
25→2 extension.nodeditor uses binding✕
- Connections
- 3 pairs of types, where a type in extension.nodeditor uses a type in binding.
- The types involved
imgui.extension.nodeditor.NodeEditorConfig→imgui.binding.ImGuiStructDestroyableimgui.extension.nodeditor.NodeEditorContext→imgui.binding.ImGuiStructimgui.extension.nodeditor.NodeEditorStyle→imgui.binding.ImGuiStruct
- Direction
- extension.nodeditor uses binding, so a change to binding can break extension.nodeditor, while a change to extension.nodeditor can't break binding.
- Position
- Below the diagonal: extension.nodeditor uses a module listed above it, which is the healthy direction.
25→15 extension.nodeditor uses type✕
- Connections
- 1 pair of types, where a type in extension.nodeditor uses a type in type.
- The types involved
imgui.extension.nodeditor.NodeEditor→imgui.type.ImLong
- Direction
- extension.nodeditor uses type, so a change to type can break extension.nodeditor, while a change to extension.nodeditor can't break type.
- Position
- Below the diagonal: extension.nodeditor uses a module listed above it, which is the healthy direction.
25→20 extension.nodeditor uses imgui✕
- Connections
- 5 pairs of types, where a type in extension.nodeditor uses a type in imgui.
- The types involved
imgui.extension.nodeditor.NodeEditor→imgui.ImDrawListimgui.extension.nodeditor.NodeEditor→imgui.ImVec2imgui.extension.nodeditor.NodeEditor→imgui.ImVec4imgui.extension.nodeditor.NodeEditorStyle→imgui.ImVec2imgui.extension.nodeditor.NodeEditorStyle→imgui.ImVec4
- Direction
- extension.nodeditor uses imgui, so a change to imgui can break extension.nodeditor, while a change to extension.nodeditor can't break imgui.
- Position
- Below the diagonal: extension.nodeditor uses a module listed above it, which is the healthy direction.
26→2 extension.texteditor uses binding✕
- Connections
- 2 pairs of types, where a type in extension.texteditor uses a type in binding.
- The types involved
imgui.extension.texteditor.TextEditor→imgui.binding.ImGuiStructDestroyableimgui.extension.texteditor.TextEditorLanguage→imgui.binding.ImGuiStruct
- Direction
- extension.texteditor uses binding, so a change to binding can break extension.texteditor, while a change to extension.texteditor can't break binding.
- Position
- Below the diagonal: extension.texteditor uses a module listed above it, which is the healthy direction.
26→11 extension.texteditor uses extension.texteditor.flag✕
- Connections
- 2 pairs of types, where a type in extension.texteditor uses a type in extension.texteditor.flag.
- The types involved
imgui.extension.texteditor.TextEditor→imgui.extension.texteditor.flag.TextEditorColorimgui.extension.texteditor.TextEditor→imgui.extension.texteditor.flag.TextEditorScroll
- Direction
- extension.texteditor uses extension.texteditor.flag, so a change to extension.texteditor.flag can break extension.texteditor, while a change to extension.texteditor can't break extension.texteditor.flag.
- Position
- Below the diagonal: extension.texteditor uses a module listed above it, which is the healthy direction.
26→19 extension.texteditor uses internal✕
- Connections
- 1 pair of types, where a type in extension.texteditor uses a type in internal.
- The types involved
imgui.extension.texteditor.TextEditor→imgui.internal.ImGuiContext
- Direction
- extension.texteditor uses internal, so a change to internal can break extension.texteditor, while a change to extension.texteditor can't break internal.
- Position
- Below the diagonal: extension.texteditor uses a module listed above it, which is the healthy direction.
26→20 extension.texteditor uses imgui✕
- Connections
- 1 pair of types, where a type in extension.texteditor uses a type in imgui.
- The types involved
imgui.extension.texteditor.TextEditor→imgui.ImVec2
- Direction
- extension.texteditor uses imgui, so a change to imgui can break extension.texteditor, while a change to extension.texteditor can't break imgui.
- Position
- Below the diagonal: extension.texteditor uses a module listed above it, which is the healthy direction.
27→16 gl3 uses callback✕
- Connections
- 1 pair of types, where a type in gl3 uses a type in callback.
- The types involved
imgui.gl3.RendererRenderWindowFunction→imgui.callback.ImPlatformFuncViewport
- Direction
- gl3 uses callback, so a change to callback can break gl3, while a change to gl3 can't break callback.
- Position
- Below the diagonal: gl3 uses a module listed above it, which is the healthy direction.
27→20 gl3 uses imgui✕
- Connections
- 3 pairs of types, where a type in gl3 uses a type in imgui.
- The types involved
imgui.gl3.ImGuiImplGl3→imgui.ImDrawDataimgui.gl3.Properties→imgui.ImVec4imgui.gl3.RendererRenderWindowFunction→imgui.ImGuiViewport
- Direction
- gl3 uses imgui, so a change to imgui can break gl3, while a change to gl3 can't break imgui.
- Position
- Below the diagonal: gl3 uses a module listed above it, which is the healthy direction.
28→16 glfw uses callback✕
- Connections
- 18 pairs of types, where a type in glfw uses a type in callback.
- The types involved
imgui.glfw.1→imgui.callback.ImStrSupplierimgui.glfw.2→imgui.callback.ImStrConsumerimgui.glfw.CreateWindowFunction→imgui.callback.ImPlatformFuncViewportimgui.glfw.DestroyWindowFunction→imgui.callback.ImPlatformFuncViewportimgui.glfw.GetWindowFocusFunction→imgui.callback.ImPlatformFuncViewportSuppBooleanimgui.glfw.GetWindowMinimizedFunction→imgui.callback.ImPlatformFuncViewportSuppBooleanimgui.glfw.GetWindowPosFunction→imgui.callback.ImPlatformFuncViewportSuppImVec2imgui.glfw.GetWindowSizeFunction→imgui.callback.ImPlatformFuncViewportSuppImVec2imgui.glfw.ImGuiImplGlfw→imgui.callback.ImStrConsumerimgui.glfw.ImGuiImplGlfw→imgui.callback.ImStrSupplierimgui.glfw.RenderWindowFunction→imgui.callback.ImPlatformFuncViewportimgui.glfw.SetWindowAlphaFunction→imgui.callback.ImPlatformFuncViewportFloatimgui.glfw.SetWindowFocusFunction→imgui.callback.ImPlatformFuncViewportimgui.glfw.SetWindowPosFunction→imgui.callback.ImPlatformFuncViewportImVec2imgui.glfw.SetWindowSizeFunction→imgui.callback.ImPlatformFuncViewportImVec2imgui.glfw.SetWindowTitleFunction→imgui.callback.ImPlatformFuncViewportStringimgui.glfw.ShowWindowFunction→imgui.callback.ImPlatformFuncViewportimgui.glfw.SwapBuffersFunction→imgui.callback.ImPlatformFuncViewport
- Direction
- glfw uses callback, so a change to callback can break glfw, while a change to glfw can't break callback.
- Position
- Below the diagonal: glfw uses a module listed above it, which is the healthy direction.
28→20 glfw uses imgui✕
- Connections
- 21 pairs of types, where a type in glfw uses a type in imgui.
- The types involved
imgui.glfw.CreateWindowFunction→imgui.ImGuiViewportimgui.glfw.Data→imgui.ImVec2imgui.glfw.DestroyWindowFunction→imgui.ImGuiViewportimgui.glfw.GetWindowFocusFunction→imgui.ImGuiViewportimgui.glfw.GetWindowMinimizedFunction→imgui.ImGuiViewportimgui.glfw.GetWindowPosFunction→imgui.ImGuiViewportimgui.glfw.GetWindowPosFunction→imgui.ImVec2imgui.glfw.GetWindowSizeFunction→imgui.ImGuiViewportimgui.glfw.GetWindowSizeFunction→imgui.ImVec2imgui.glfw.ImGuiImplGlfw→imgui.ImVec2imgui.glfw.Properties→imgui.ImVec2imgui.glfw.RenderWindowFunction→imgui.ImGuiViewportimgui.glfw.SetWindowAlphaFunction→imgui.ImGuiViewportimgui.glfw.SetWindowFocusFunction→imgui.ImGuiViewportimgui.glfw.SetWindowPosFunction→imgui.ImGuiViewportimgui.glfw.SetWindowPosFunction→imgui.ImVec2imgui.glfw.SetWindowSizeFunction→imgui.ImGuiViewportimgui.glfw.SetWindowSizeFunction→imgui.ImVec2imgui.glfw.SetWindowTitleFunction→imgui.ImGuiViewportimgui.glfw.ShowWindowFunction→imgui.ImGuiViewportimgui.glfw.SwapBuffersFunction→imgui.ImGuiViewport
- Direction
- glfw uses imgui, so a change to imgui can break glfw, while a change to glfw can't break imgui.
- Position
- Below the diagonal: glfw uses a module listed above it, which is the healthy direction.
29→16 sdl3 uses callback✕
- Connections
- 4 pairs of types, where a type in sdl3 uses a type in callback.
- The types involved
imgui.sdl3.1→imgui.callback.ImStrSupplierimgui.sdl3.2→imgui.callback.ImStrConsumerimgui.sdl3.ImGuiImplSdl3→imgui.callback.ImStrConsumerimgui.sdl3.ImGuiImplSdl3→imgui.callback.ImStrSupplier
- Direction
- sdl3 uses callback, so a change to callback can break sdl3, while a change to sdl3 can't break callback.
- Position
- Below the diagonal: sdl3 uses a module listed above it, which is the healthy direction.
29→20 sdl3 uses imgui✕
- Connections
- 2 pairs of types, where a type in sdl3 uses a type in imgui.
- The types involved
imgui.sdl3.ImGuiImplSdl3→imgui.ImGuiIOimgui.sdl3.ImGuiImplSdlRenderer3→imgui.ImDrawData
- Direction
- sdl3 uses imgui, so a change to imgui can break sdl3, while a change to sdl3 can't break imgui.
- Position
- Below the diagonal: sdl3 uses a module listed above it, which is the healthy direction.
30→27 app uses gl3✕
- Connections
- 1 pair of types, where a type in app uses a type in gl3.
- The types involved
imgui.app.WindowGlfw→imgui.gl3.ImGuiImplGl3
- Direction
- app uses gl3, so a change to gl3 can break app, while a change to app can't break gl3.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
30→28 app uses glfw✕
- Connections
- 1 pair of types, where a type in app uses a type in glfw.
- The types involved
imgui.app.WindowGlfw→imgui.glfw.ImGuiImplGlfw
- Direction
- app uses glfw, so a change to glfw can break app, while a change to app can't break glfw.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
30→29 app uses sdl3✕
- Connections
- 4 pairs of types, where a type in app uses a type in sdl3.
- The types involved
imgui.app.WindowSdl→imgui.sdl3.ImGuiImplSdl3imgui.app.WindowSdl→imgui.sdl3.ImGuiImplSdlGpu3imgui.app.WindowSdlRenderer→imgui.sdl3.ImGuiImplSdl3imgui.app.WindowSdlRenderer→imgui.sdl3.ImGuiImplSdlRenderer3
- Direction
- app uses sdl3, so a change to sdl3 can break app, while a change to app can't break sdl3.
- Position
- Below the diagonal: app uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 4 | Medium |
Roadmap
Top priorities: Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with ImGuiImplSdlGpu3.java, ImGuiIO.java, jni_content.kt; 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; Resolve the 116 Low coverage finding(s) in Code Coverage — start with ImGui.java (2), BindingSourceProcessor.kt, ExcludedSourceProcessor.kt.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with ImGuiImplSdlGpu3.java, ImGuiIO.java, jni_content.kt. | +9.0 pts | Medium | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.7 pts | Medium | Architecture documentation |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ImGui.java, ImPlot.java, ImGuiImplSdl3.java. | +2.7 pts | Low | Knowledge Freshness |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.7 pts | Medium | Security & performance tooling |
| Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle. | +1.3 pts | Low | Project Cohesion |
| Resolve the 116 Low coverage finding(s) in Code Coverage — start with ImGui.java (2), BindingSourceProcessor.kt, ExcludedSourceProcessor.kt. | +4.2 pts | High | Code Coverage |
| Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. | +0.9 pts | Low | Knowledge Freshness |
| Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion). | +1.6 pts | Medium | Dependency direction |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java | 6.0 | Mixed | Explicit Debt: FixmeComment |
| imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/ImGui.java | 6.0 | Mixed | Explicit Debt: FixmeComment |
| imgui-binding/src/main/java/imgui/ImGuiPlatformIO.java | 6.0 | Mixed | Explicit Debt: FixmeComment |
| imgui-binding/src/main/java/imgui/internal/ImGui.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/internal/ImGuiDockNode.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| imgui-app/src/main/java/imgui/app/WindowSdl.java | 6.3 | Mixed | Code Duplication: Duplicated block (12 lines × 2) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| imgui-binding/src/generated/java/imgui/internal/ImGui.java | 6.5 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/ImFontAtlas.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/ImGuiIO.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/ImGuiInputTextCallbackData.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/extension/imnodes/ImNodes.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/extension/implot/ImPlot.java | 6.7 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/generated/java/imgui/extension/imnodes/ImNodes.java | 6.9 | Mixed | Explicit Debt: TodoComment |
| imgui-binding/src/main/java/imgui/ImDrawData.java | 7.0 | Mixed | Code Duplication: Edited copy of a member (14 corresponding lines) |
| imgui-binding/src/main/java/imgui/ImVec2.java | 7.0 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 277 of 326 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.cpp, .java) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.cpp, .java) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D4 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 6 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .java (75,791 lines, 99% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D15 Churn × Complexity Hotspots — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A hotspot is churn × complexity. Churn was measured (641 line(s) across the 90-day window), but no complexity could be computed for .cpp, .java, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (41 contributor(s) across 685 commit(s) sampled, automation and bot accounts excluded). One of them holds 88% of the history; the other 40 hold 0.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (imgui-lwjgl3/build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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").
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D4 · Code Duplication
6 duplicated block group(s) detected. 0.4 % of the production lines (347 of 77,988) are in a reported copy. A further 9 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 2 of the 15 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .java (99% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 3 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with ImVec2.java, ImGuiImplGlfw.java, ImGuiImplSdlGpu3.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (23 corresponding lines) finding(s) in Code Duplication — start with ImGuiImplSdlGpu3.java, ImGuiImplGlfw.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with ImGuiImplGl3.java, ImDrawData.java. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
5 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 3 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 16 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with ImGuiImplGlfw.java. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 0.0% — 116 file(s) below 50%. Measured from the Java/Kotlin suite (repository root, Gradle: the JaCoCo agent on the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 46 line(s) in 1 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 116 Low coverage finding(s) in Code Coverage — start with ImGui.java (2), BindingSourceProcessor.kt, ExcludedSourceProcessor.kt. — One of this dimension's main actionable groups (116 warning-level).
- Resolve the 1 Tests reach code only in some runs finding(s) in Code Coverage — start with ImString.java. — One of this dimension's main actionable groups (1 recommendation-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 37 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 47 artifact(s) resolved, 47 of them gradable against Maven Central, and 38 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 8 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 7 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 4 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
D17 · Explicit Debt
48 deducted task-comment markers across 77988 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 37 TodoComment finding(s) in Explicit Debt — start with ImGui.java (12), ImGuiImplSdl3.java (6), ImGuiDockNode.java (4). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 11 FixmeComment finding(s) in Explicit Debt — start with ImGuiPlatformIO.java (4), ImGuiImplGlfw.java (2), ImGui.java (2). — One of this dimension's main actionable groups (11 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D26 · Project Cohesion
1 of 3 build units (Gradle) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
58 % of calls cross a namespace and 1 % go through an interface, but 69 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 19 high, 1 medium, 0 low. 17 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 74, line 178) — 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.
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).
- No action in Static Analysis (SAST) — all 17 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (17 issue-level, 0 of them charged here).
D34 · Knowledge Freshness
46 of 51 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is imgui-binding/src/main/java/imgui/ImGui.java. Counted over 51 of the 211 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 43 Orphaned file finding(s) in Knowledge Freshness — start with ImGuiImplSdlGpu3.java, ImGuiIO.java, jni_content.kt. — One of this dimension's main actionable groups (43 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with ImGui.java, ImPlot.java, ImGuiImplSdl3.java. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 6 platform declaration(s) and 9 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
- `:imgui-app` is a Application project but references `:imgui-binding`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
- `:imgui-app` is a Application project but references `:imgui-lwjgl3`, a Web project. The clean-architecture rule is that dependencies point INWARD — the domain/application core must not depend on outer layers (infrastructure/web). Invert it: define the abstraction in the inner layer and implement it in the outer one.
What to do
- Keep dependencies pointing inward: domain/application define interfaces, infrastructure/web implement them (Dependency Inversion).
GD1 · Unfinished & placeholder code
- `updateTexture` is a shipped method whose body is empty except for a TODO/FIXME — scaffolding that was never completed. Implement it or remove it. — imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:709
What to do
- Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step (`./gradlew test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
- 5 public types in `imgui.internal` are marked as implementation by their own namespace, folder or name: `ImGui` (imgui-binding/src/main/java/imgui/internal/ImGui.java:18, `internal`), `ImGuiContext` (imgui-binding/src/main/java/imgui/internal/ImGuiContext.java:5, `internal`), `ImGuiDockNode` (imgui-binding/src/main/java/imgui/internal/ImGuiDockNode.java:12, `internal`), `ImGuiWindow` (imgui-binding/src/main/java/imgui/internal/ImGuiWindow.java:8, `internal`), `ImRect` (imgui-binding/src/main/java/imgui/internal/ImRect.java:11, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — imgui-binding/src/main/java/imgui/internal/ImGui.java:18
- 10 public types in `imgui.internal.flag` are marked as implementation by their own namespace, folder or name: `ImGuiAxis` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiAxis.java:7, `internal`), `ImGuiButtonFlags` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiButtonFlags.java:7, `internal`), `ImGuiDataAuthority` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiDataAuthority.java:10, `internal`), `ImGuiDockNodeFlags` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiDockNodeFlags.java:10, `internal`), `ImGuiDockNodeState` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiDockNodeState.java:7, `internal`), `ImGuiFocusRequestFlags` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiFocusRequestFlags.java:7, `internal`), `ImGuiItemFlags` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiItemFlags.java:11, `internal`), `ImGuiItemStatusFlags` (imgui-binding/src/main/java/imgui/internal/flag/ImGuiItemStatusFlags.java:7, `internal`), and 2 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — imgui-binding/src/main/java/imgui/internal/flag/ImGuiAxis.java:7
What to do
- Hide `imgui.internal` (`ImGui`, `ImGuiContext`, `ImGuiDockNode`, `ImGuiWindow`, `ImRect`) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
- Hide `imgui.internal.flag` (`ImGuiAxis`, `ImGuiButtonFlags`, `ImGuiDataAuthority`, `ImGuiDockNodeFlags`, `ImGuiDockNodeState`, `ImGuiFocusRequestFlags`, `ImGuiItemFlags`, `ImGuiItemStatusFlags`, and 2 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `imgui-app`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:9
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gitsubmodule`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Dependabot is configured but does not watch `gitsubmodule` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X13 · Undrained process stream
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X3 · Exception handling
X5 · Nullable reference types
- 0/52 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73.1 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 66.6 | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 47.2 | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 56.0 | Adequate — gated by D8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 73.0 | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 23 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 72 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- AX6 Interface segregation — no public interfaces
- 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .cpp, .java exposed no member bodies
- D15 Churn × Complexity Hotspots — complexity unreadable for .cpp, .java — churn × complexity hotspots could not be measured
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- 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.
- D2 Cognitive Complexity — cognitive complexity not measured — .cpp, .java exposed no member bodies
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (5320 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D3 God Classes — Most of this repository's production source (.cpp, .java) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- 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
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (13 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 116 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 3% of this repository's production lines — java (75,791 lines), cpp (377 lines), c (273 lines), groovy (218 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — 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; a Kotlin request outside a suspend function has no caller's cancellation to honour
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 21 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dependency-rule violation: :imgui-app (Application) → :imgui-binding (Web)
- Dependency-rule violation: :imgui-app (Application) → :imgui-lwjgl3 (Web)
- REDACTED
- REDACTED
Serious — 185 finding(s)
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/BindingSourceProcessor.kt buildSrc/src/main/kotlin/tool/generator/api/BindingSourceProcessor.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/ExcludedSourceProcessor.kt buildSrc/src/main/kotlin/tool/generator/api/ExcludedSourceProcessor.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/ast_content.kt buildSrc/src/main/kotlin/tool/generator/api/ast_content.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/jni_content.kt buildSrc/src/main/kotlin/tool/generator/api/jni_content.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/jvm_content.kt buildSrc/src/main/kotlin/tool/generator/api/jvm_content.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/task/GenerateApi.kt buildSrc/src/main/kotlin/tool/generator/api/task/GenerateApi.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/api/util.kt buildSrc/src/main/kotlin/tool/generator/api/util.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/ast/AstParser.kt buildSrc/src/main/kotlin/tool/generator/ast/AstParser.kt:1
- Low coverage: buildSrc/src/main/kotlin/tool/generator/ast/decl.kt buildSrc/src/main/kotlin/tool/generator/ast/decl.kt:1
- Low coverage: REDACTED REDACTED:1
- Low coverage: example/src/main/java/ExampleCanvasEditor.java example/src/main/java/ExampleCanvasEditor.java:1
- Low coverage: example/src/main/java/ExampleDragAndDrop.java example/src/main/java/ExampleDragAndDrop.java:1
- Low coverage: example/src/main/java/ExampleImGuiColorTextEdit.java example/src/main/java/ExampleImGuiColorTextEdit.java:1
- Low coverage: example/src/main/java/ExampleImGuiMemoryEditor.java example/src/main/java/ExampleImGuiMemoryEditor.java:1
- Low coverage: example/src/main/java/ExampleImGuiNodeEditor.java example/src/main/java/ExampleImGuiNodeEditor.java:1
- Low coverage: example/src/main/java/ExampleImGuizmo.java example/src/main/java/ExampleImGuizmo.java:1
- Low coverage: example/src/main/java/ExampleImNodes.java example/src/main/java/ExampleImNodes.java:1
- Low coverage: example/src/main/java/ExampleImPlot.java example/src/main/java/ExampleImPlot.java:1
- Low coverage: example/src/main/java/ExampleInputTextCallback.java example/src/main/java/ExampleInputTextCallback.java:1
- Low coverage: example/src/main/java/ExampleKnobs.java example/src/main/java/ExampleKnobs.java:1
- Low coverage: example/src/main/java/Extra.java example/src/main/java/Extra.java:1
- Low coverage: example/src/main/java/FontAwesomeIcons.java example/src/main/java/FontAwesomeIcons.java:1
- Low coverage: example/src/main/java/Graph.java example/src/main/java/Graph.java:1
- Low coverage: example/src/main/java/Main.java example/src/main/java/Main.java:1
- Low coverage: example/src/main/java/MainSdl.java example/src/main/java/MainSdl.java:1
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:367
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:376
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:418
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:512
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:668
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:712
- TodoComment imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:710
- TodoComment imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:370
- TodoComment imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java:570
- TodoComment imgui-binding/src/main/java/imgui/ImFontAtlas.java:369
- TodoComment imgui-binding/src/generated/java/imgui/ImFontAtlas.java:770
- TodoComment imgui-binding/src/main/java/imgui/ImGui.java:2718
- TodoComment imgui-binding/src/generated/java/imgui/ImGui.java:12757
- TodoComment imgui-binding/src/main/java/imgui/ImGuiIO.java:820
- TodoComment imgui-binding/src/generated/java/imgui/ImGuiIO.java:3002
- TodoComment imgui-binding/src/main/java/imgui/ImGuiInputTextCallbackData.java:51
- TodoComment imgui-binding/src/generated/java/imgui/ImGuiInputTextCallbackData.java:88
- TodoComment imgui-binding/src/main/java/imgui/internal/ImGui.java:155
- TodoComment imgui-binding/src/generated/java/imgui/internal/ImGui.java:445
- TodoComment imgui-binding/src/main/java/imgui/internal/ImGui.java:162
- TodoComment imgui-binding/src/generated/java/imgui/internal/ImGui.java:457
- TodoComment imgui-binding/src/main/java/imgui/internal/ImGui.java:241
- TodoComment imgui-binding/src/generated/java/imgui/internal/ImGui.java:791
- TodoComment imgui-binding/src/main/java/imgui/internal/ImGui.java:270
- TodoComment imgui-binding/src/generated/java/imgui/internal/ImGui.java:915
- FixmeComment imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:1064
- FixmeComment imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:1107
- FixmeComment imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java:548
- FixmeComment imgui-binding/src/main/java/imgui/ImGui.java:1927
- FixmeComment imgui-binding/src/generated/java/imgui/ImGui.java:10552
- FixmeComment imgui-binding/src/main/java/imgui/ImGuiPlatformIO.java:375
- FixmeComment imgui-binding/src/generated/java/imgui/ImGuiPlatformIO.java:375
- FixmeComment imgui-binding/src/main/java/imgui/ImGuiPlatformIO.java:390
- FixmeComment imgui-binding/src/generated/java/imgui/ImGuiPlatformIO.java:390
- FixmeComment imgui-binding/src/generated/java/imgui/internal/flag/ImGuiButtonFlags.java:105
- FixmeComment imgui-binding/src/generated/java/imgui/flag/ImGuiViewportFlags.java:94
- Edited copy of a member (10 corresponding lines) imgui-binding/src/main/java/imgui/ImVec2.java:74
- Edited copy of a member (10 corresponding lines) imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:1530
- Edited copy of a member (10 corresponding lines) imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:165
- Edited copy of a member (23 corresponding lines) imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:553
- Edited copy of a member (23 corresponding lines) imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:991
- Edited copy of a member (14 corresponding lines) imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java:696
- Edited copy of a member (14 corresponding lines) imgui-binding/src/main/java/imgui/ImDrawData.java:96
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (16 corresponding lines) imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:1379
- Edited copy of a member (15 corresponding lines) imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:1262
- Duplicated block (12 lines × 2) imgui-app/src/main/java/imgui/app/WindowSdl.java:61
- Duplicated block (9 lines × 2) imgui-app/src/main/java/imgui/app/WindowSdl.java:124
- Duplicated block (6–7 lines × 2) imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:348
- Duplicated block (5 lines × 2) imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:677
- Duplicated block (4–13 lines × 6) example/src/main/java/ExampleCanvasEditor.java:31
- Duplicated block (10 lines × 2) example/src/main/java/ExampleImGuiNodeEditor.java:94
- Off the main sequence: :imgui-binding
- Low cohesion: ImGuiImplGlfw (LCOM4 4) imgui-lwjgl3/src/main/java/imgui/glfw/ImGuiImplGlfw.java:278
- Unfinished stub — empty body under a TODO marker imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:709
Minor — 82 finding(s)
- Orphaned file imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdlGpu3.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImGuiIO.java:1
- Orphaned file buildSrc/src/main/kotlin/tool/generator/api/jni_content.kt:1
- Orphaned file buildSrc/src/main/kotlin/tool/generator/api/jvm_content.kt:1
- Orphaned file imgui-binding/src/main/java/imgui/ImGuiPlatformIO.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImFontAtlas.java:1
- Orphaned file REDACTED:1
- Orphaned file imgui-binding/src/main/java/imgui/internal/ImGui.java:1
- Orphaned file imgui-binding/src/main/java/imgui/extension/imnodes/ImNodes.java:1
- Orphaned file imgui-binding/src/main/java/imgui/extension/texteditor/TextEditor.java:1
- Orphaned file imgui-binding/src/main/java/imgui/extension/nodeditor/NodeEditor.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImGuiStyle.java:1
- Orphaned file imgui-binding/src/main/java/imgui/extension/imguifiledialog/ImGuiFileDialog.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImDrawList.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImDrawData.java:1
- Orphaned file buildSrc/src/main/kotlin/tool/generator/api/BindingSourceProcessor.kt:1
- Orphaned file imgui-binding/src/main/java/imgui/extension/imguizmo/ImGuizmo.java:1
- Orphaned file imgui-app/src/main/java/imgui/app/WindowGlfw.java:1
- Orphaned file imgui-binding/src/main/java/imgui/type/ImString.java:1
- Orphaned file imgui-app/src/main/java/imgui/app/WindowSdl.java:1
- Orphaned file imgui-binding/src/main/java/imgui/internal/ImGuiDockNode.java:1
- Orphaned file buildSrc/src/main/kotlin/tool/generator/api/util.kt:1
- Orphaned file imgui-binding/src/main/java/imgui/ImFontConfig.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImGuiViewport.java:1
- Orphaned file imgui-binding/src/main/java/imgui/ImGuiListClipper.java:1
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/implot/ImPlotRange.java:89
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/implot/ImPlotPoint.java:87
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImVec2.java:82
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImVec4.java:88
- Duplicated predicate imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java:159
- Duplicated predicate imgui-binding/src/generated/java/imgui/internal/ImRect.java:70
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/texteditor/TextEditorCursorSelection.java:53
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/implot/ImPlotRect.java:92
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImGui.java:12076
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImFontAtlas.java:563
- Duplicated predicate imgui-lwjgl3/src/main/java/imgui/gl3/ImGuiImplGl3.java:581
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/texteditor/TextEditorCursorPosition.java:47
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImFontGlyphRangesBuilder.java:65
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImGui.java:12073
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImGui.java:12118
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImGui.java:12132
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImGui.java:12001
- Duplicated predicate imgui-binding/src/generated/java/imgui/type/ImString.java:114
- Duplicated predicate imgui-binding/src/generated/java/imgui/ImFontAtlas.java:596
- Duplicated predicate imgui-binding/src/generated/java/imgui/extension/implot/ImPlotRect.java:27
- Duplicated predicate imgui-app/src/main/java/imgui/app/WindowSdl.java:128
- Duplicated predicate buildSrc/src/main/kotlin/tool/generator/api/jni_content.kt:23
- Duplicated predicate buildSrc/src/main/kotlin/tool/generator/api/jni_content.kt:500
- Most significant orphaned file imgui-binding/src/main/java/imgui/ImGui.java:1
- Most significant orphaned file imgui-binding/src/main/java/imgui/extension/implot/ImPlot.java:1
- Most significant orphaned file imgui-lwjgl3/src/main/java/imgui/sdl3/ImGuiImplSdl3.java:1
- Implementation type on the public API imgui-binding/src/main/java/imgui/internal/ImGui.java:18
- Implementation type on the public API imgui-binding/src/main/java/imgui/internal/flag/ImGuiAxis.java:7
- Projects may be oversized for their cohesion imgui-binding/build.gradle:1
- Concentrated knowledge decay
- REDACTED
- REDACTED
- Tests reach code only in some runs: imgui-binding/src/main/java/imgui/type/ImString.java imgui-binding/src/main/java/imgui/type/ImString.java:23
- No ADRs
- Logging is not universal
- No SAST REDACTED:9
- Dependabot does not watch gitsubmodule REDACTED:2
- No changelog
- Java packages are not null-marked everywhere
Minor — 38 finding(s)
- Outdated (compile): org.lwjgl:lwjgl-bom
- Outdated (compile): org.junit.jupiter:junit-jupiter-api
- Outdated (compile): org.junit:junit-bom
- Outdated (compile): org.junit.jupiter:junit-jupiter-engine
- Outdated (compile): org.junit.platform:junit-platform-commons
- Outdated (compile): org.junit.platform:junit-platform-engine
- Outdated (compile): org.junit.platform:junit-platform-launcher
- Outdated (compile): com.puppycrawl.tools:checkstyle
- Outdated (compile): commons-beanutils:commons-beanutils
- Outdated (compile): commons-collections:commons-collections
- Outdated (compile): com.google.guava:guava
- Outdated (compile): org.jspecify:jspecify
- Outdated (compile): com.google.errorprone:error_prone_annotations
- Outdated (compile): com.google.j2objc:j2objc-annotations
- Outdated (compile): org.javassist:javassist
- Outdated (compile): net.sf.saxon:Saxon-HE
- Outdated (compile): org.xmlresolver:xmlresolver
- Outdated (compile): org.apache.httpcomponents.client5:httpclient5
- Outdated (compile): org.apache.httpcomponents.core5:httpcore5
- Outdated (compile): org.apache.httpcomponents.core5:httpcore5-h2
- Outdated (compile): commons-codec:commons-codec
- Outdated (compile): org.checkerframework:checker-qual
- Outdated (compile): org.apache.maven.doxia:doxia-core
- Outdated (compile): org.apache.maven.doxia:doxia-sink-api
- Outdated (compile): org.codehaus.plexus:plexus-container-default
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-e51bcb6b529945f2befe02c8685a6e36/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=485" --report-format json --report-path /tmp/watchdog-gitleaks-e51bcb6b529945f2befe02c8685a6e36/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e51bcb6b529945f2befe02c8685a6e36/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 20 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |