Executive summary
maxcom/lorsource falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 41 out of 100 and is rated Weak, and four of its 48 critical findings are security problems.
Code Health, at 32, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 3 points. Adding type checking would lift Code Health itself, worth about 5 points. Raising Code Health to 70 would lift the score to about 49.
Three pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One password or key is open to anyone who can read the repository. Pinning each tool to an exact version and replacing the exposed password or key would close both risks. The 20 labels or groups of fields with no name need connecting to their fields or naming.
The product code is 32,668 lines, about €41,000 to rebuild.
If Code Health rose from 32 to 70, the lowest score rated Strong, the score would rise from 41 to about 49.
New since the last survey: 8 findings
- Cyclomatic Complexity · (anonymous) (cyclomatic 67) src/main/webapp/js/add-form.js
- Cognitive Complexity · SearchController.search (cognitive 17) src/main/scala/ru/org/linux/search/SearchController.scala
- Cohesion (LCOM4) · Low cohesion: CommentDao (LCOM4 5) src/main/scala/ru/org/linux/comment/CommentDao.scala
- Churn × Complexity Hotspots · Hotspot: src/main/scala/ru/org/linux/admin/DelIPController.scala src/main/scala/ru/org/linux/admin/DelIPController.scala
- Large Files · src/main/webapp/js/add-form.js: 631 lines of code src/main/webapp/js/add-form.js
- Dead Code · Dead file (~748 LoC) src/main/webapp/js/add-form.js
- Documentation (README) · README may be stale
- Exception handling · Swallowed exception (empty catch) src/main/webapp/js/add-form.js
Fixed since the last survey: 10 findings
- Cyclomatic Complexity · (anonymous) (cyclomatic 60) src/main/webapp/js/add-form.js
- Churn × Complexity Hotspots · Hotspot: src/main/scala/ru/org/linux/user/WhoisController.scala src/main/scala/ru/org/linux/user/WhoisController.scala
- Churn × Complexity Hotspots · Hotspot: src/main/java/ru/org/linux/util/bbcode/tags/UrlWithParamTag.java src/main/java/ru/org/linux/util/bbcode/tags/UrlWithParamTag.java
- Static Analysis (SAST) · Medium: crlf-injection-logs src/main/java/ru/org/linux/csrf/CSRFProtectionService.java
- Large Files · src/main/webapp/js/add-form.js: 579 lines of code src/main/webapp/js/add-form.js
- Dead Code · Dead file (~694 LoC) src/main/webapp/js/add-form.js
- Forms & labels · <input> without a programmatic label src/main/webapp/WEB-INF/jsp/whois.jsp
- Forms & labels · <select> without a programmatic label src/main/webapp/WEB-INF/jsp/whois.jsp
- Forms & labels · <select> without a programmatic label src/main/webapp/WEB-INF/jsp/whois.jsp
- Forms & labels · <input> without a programmatic label src/main/webapp/js/add-form.js
Rebuild cost: about €41,000 · Estimate
| Cost to rebuild | €14,000 to €68,000, for 226 to 717 hours of work, about 0.3 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. 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: 32,668 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 org.springframework.scala.transaction.support | 2 ru.org.linux.adv | 3 ru.org.linux.section | 4 ru.org.linux.spring | 5 ru.org.linux.topic.TopicListController | 6 ru.org.linux.tracker | 7 ru.org.linux.reaction | 8 ru.org.linux.scalikejdbc | 9 ru.org.linux.site | 10 ru.org.linux.util.bbcode.tags | 11 ru.org.linux.msgbase | 12 ru.org.linux.markup | 13 ru.org.linux.user | 14 ru.org.linux.admin | 15 ru.org.linux.email | 16 ru.org.linux.group | 17 ru.org.linux.poll | 18 ru.org.linux.realtime | 19 ru.org.linux.util.markdown | 20 ru.org.linux.exception | 21 ru.org.linux.rights | 22 ru.org.linux.tag | 23 ru.org.linux.tag.TagService | 24 ru.org.linux.topic.AddTopicController | 25 ru.org.linux.warning | 26 ru.org.linux.boxlets | 27 ru.org.linux.comment | 28 ru.org.linux.site.tags | 29 ru.org.linux.comment.DeleteService | 30 ru.org.linux.edithistory | 31 ru.org.linux.topic | 32 ru.org.linux.auth | 33 ru.org.linux.search | 34 ru.org.linux.util | 35 ru.org.linux.gallery | 36 ru.org.linux.util.formatter | 37 ru.org.linux | 38 ru.org.linux.edithistory.EditHistoryService | 39 ru.org.linux.util.bbcode.nodes | 40 ru.org.linux.util.bbcode |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 org.springframework.scala.transaction.support | ||||||||||||||||||||||||||||||||||||||||
| 2 ru.org.linux.adv | ||||||||||||||||||||||||||||||||||||||||
| 3 ru.org.linux.section | ||||||||||||||||||||||||||||||||||||||||
| 4 ru.org.linux.spring | ||||||||||||||||||||||||||||||||||||||||
| 5 ru.org.linux.topic.TopicListController | ||||||||||||||||||||||||||||||||||||||||
| 6 ru.org.linux.tracker | ||||||||||||||||||||||||||||||||||||||||
| 7 ru.org.linux.reaction | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 8 ru.org.linux.scalikejdbc | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 ru.org.linux.site | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 10 ru.org.linux.util.bbcode.tags | 12 | 12 | ||||||||||||||||||||||||||||||||||||||
| 11 ru.org.linux.msgbase | 3 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 12 ru.org.linux.markup | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 ru.org.linux.user | 2 | 1 | 1 | 4 | 1 | 4 | 1 | 2 | 3 | 1 | ||||||||||||||||||||||||||||||
| 14 ru.org.linux.admin | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 ru.org.linux.email | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 ru.org.linux.group | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 ru.org.linux.poll | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 ru.org.linux.realtime | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 ru.org.linux.util.markdown | 2 | |||||||||||||||||||||||||||||||||||||||
| 20 ru.org.linux.exception | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 ru.org.linux.rights | 2 | 3 | 4 | 5 | 8 | |||||||||||||||||||||||||||||||||||
| 22 ru.org.linux.tag | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 23 ru.org.linux.tag.TagService | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 ru.org.linux.topic.AddTopicController | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 ru.org.linux.warning | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 26 ru.org.linux.boxlets | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 ru.org.linux.comment | 2 | 2 | 2 | 9 | 1 | 2 | 4 | 2 | ||||||||||||||||||||||||||||||||
| 28 ru.org.linux.site.tags | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 ru.org.linux.comment.DeleteService | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 ru.org.linux.edithistory | 2 | 2 | 2 | 1 | 1 | 2 | 2 | |||||||||||||||||||||||||||||||||
| 31 ru.org.linux.topic | 7 | 1 | 2 | 1 | 1 | 2 | 1 | 7 | 8 | 5 | 1 | 5 | 2 | 1 | 5 | 5 | ||||||||||||||||||||||||
| 32 ru.org.linux.auth | 14 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 33 ru.org.linux.search | 2 | 4 | 1 | |||||||||||||||||||||||||||||||||||||
| 34 ru.org.linux.util | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 ru.org.linux.gallery | 2 | 1 | 1 | 1 | 1 | 4 | 2 | |||||||||||||||||||||||||||||||||
| 36 ru.org.linux.util.formatter | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 ru.org.linux | 1 | 1 | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 38 ru.org.linux.edithistory.EditHistoryService | 2 | 1 | 1 | 1 | 4 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 39 ru.org.linux.util.bbcode.nodes | 1 | 2 | 1 | 1 | 8 | |||||||||||||||||||||||||||||||||||
| 40 ru.org.linux.util.bbcode | 2 | 1 | 1 | 5 |
7→13 ru.org.linux.reaction uses ru.org.linux.user part of a loop✕
- Connections
- 3 pairs of types, where a type in ru.org.linux.reaction uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.reaction.PreparedReaction→ru.org.linux.user.Userru.org.linux.reaction.PreparedReactionView→ru.org.linux.user.Userru.org.linux.reaction.ReactionListItem→ru.org.linux.user.User
- Direction
- ru.org.linux.reaction uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.reaction, while a change to ru.org.linux.reaction can't break ru.org.linux.user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→27 ru.org.linux.reaction uses ru.org.linux.comment part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.reaction uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.reaction.ReactionController→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.reaction uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.reaction, while a change to ru.org.linux.reaction can't break ru.org.linux.comment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→31 ru.org.linux.reaction uses ru.org.linux.topic part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.reaction uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.reaction.ReactionController→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.reaction uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.reaction, while a change to ru.org.linux.reaction can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→32 ru.org.linux.reaction uses ru.org.linux.auth part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.reaction uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.reaction.ReactionController→ru.org.linux.auth.AuthorizedSession
- Direction
- ru.org.linux.reaction uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.reaction, while a change to ru.org.linux.reaction can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→1 ru.org.linux.scalikejdbc uses org.springframework.scala.transaction.support✕
- Connections
- 1 pair of types, where a type in ru.org.linux.scalikejdbc uses a type in org.springframework.scala.transaction.support.
- The types involved
ru.org.linux.scalikejdbc.SpringDB→org.springframework.scala.transaction.support.TransactionManagement
- Direction
- ru.org.linux.scalikejdbc uses org.springframework.scala.transaction.support, so a change to org.springframework.scala.transaction.support can break ru.org.linux.scalikejdbc, while a change to ru.org.linux.scalikejdbc can't break org.springframework.scala.transaction.support.
- Position
- Below the diagonal: ru.org.linux.scalikejdbc uses a module listed above it, which is the healthy direction.
9→6 ru.org.linux.site uses ru.org.linux.tracker✕
- Connections
- 1 pair of types, where a type in ru.org.linux.site uses a type in ru.org.linux.tracker.
- The types involved
ru.org.linux.site.DefaultProfile→ru.org.linux.tracker.TrackerFilterEnum
- Direction
- ru.org.linux.site uses ru.org.linux.tracker, so a change to ru.org.linux.tracker can break ru.org.linux.site, while a change to ru.org.linux.site can't break ru.org.linux.tracker.
- Position
- Below the diagonal: ru.org.linux.site uses a module listed above it, which is the healthy direction.
9→13 ru.org.linux.site uses ru.org.linux.user part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.site uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.site.BadInputException→ru.org.linux.user.UserErrorExceptionru.org.linux.site.Template→ru.org.linux.user.Profile
- Direction
- ru.org.linux.site uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.site, while a change to ru.org.linux.site can't break ru.org.linux.user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→31 ru.org.linux.site uses ru.org.linux.topic part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.site uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.site.MessageNotFoundException→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.site uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.site, while a change to ru.org.linux.site can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→39 ru.org.linux.util.bbcode.tags uses ru.org.linux.util.bbcode.nodes part of a loop✕
- Connections
- 12 pairs of types, where a type in ru.org.linux.util.bbcode.tags uses a type in ru.org.linux.util.bbcode.nodes.
- The types involved
ru.org.linux.util.bbcode.tags.CodeTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.CutTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.HtmlEquivTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.InlineTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.LiTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.ListTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.MemberTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.QuoteTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.SoftBrTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.Tag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.UrlTag→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.tags.UrlWithParamTag→ru.org.linux.util.bbcode.nodes.Node
- Direction
- ru.org.linux.util.bbcode.tags uses ru.org.linux.util.bbcode.nodes, so a change to ru.org.linux.util.bbcode.nodes can break ru.org.linux.util.bbcode.tags, while a change to ru.org.linux.util.bbcode.tags can't break ru.org.linux.util.bbcode.nodes.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→40 ru.org.linux.util.bbcode.tags uses ru.org.linux.util.bbcode part of a loop✕
- Connections
- 12 pairs of types, where a type in ru.org.linux.util.bbcode.tags uses a type in ru.org.linux.util.bbcode.
- The types involved
ru.org.linux.util.bbcode.tags.CodeTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.CutTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.HtmlEquivTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.InlineTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.LiTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.ListTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.MemberTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.QuoteTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.SoftBrTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.Tag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.UrlTag→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.tags.UrlWithParamTag→ru.org.linux.util.bbcode.ParserParameters
- Direction
- ru.org.linux.util.bbcode.tags uses ru.org.linux.util.bbcode, so a change to ru.org.linux.util.bbcode can break ru.org.linux.util.bbcode.tags, while a change to ru.org.linux.util.bbcode.tags can't break ru.org.linux.util.bbcode.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→8 ru.org.linux.msgbase uses ru.org.linux.scalikejdbc✕
- Connections
- 3 pairs of types, where a type in ru.org.linux.msgbase uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.msgbase.DeleteInfoDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.msgbase.MsgbaseDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.msgbase.UserAgentDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.msgbase uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.msgbase, while a change to ru.org.linux.msgbase can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.msgbase uses a module listed above it, which is the healthy direction.
11→9 ru.org.linux.msgbase uses ru.org.linux.site✕
- Connections
- 1 pair of types, where a type in ru.org.linux.msgbase uses a type in ru.org.linux.site.
- The types involved
ru.org.linux.msgbase.DeleteInfoDao→ru.org.linux.site.DeleteInfo
- Direction
- ru.org.linux.msgbase uses ru.org.linux.site, so a change to ru.org.linux.site can break ru.org.linux.msgbase, while a change to ru.org.linux.msgbase can't break ru.org.linux.site.
- Position
- Below the diagonal: ru.org.linux.msgbase uses a module listed above it, which is the healthy direction.
11→12 ru.org.linux.msgbase uses ru.org.linux.markup part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.msgbase uses a type in ru.org.linux.markup.
- The types involved
ru.org.linux.msgbase.MessageText→ru.org.linux.markup.MarkupType
- Direction
- ru.org.linux.msgbase uses ru.org.linux.markup, so a change to ru.org.linux.markup can break ru.org.linux.msgbase, while a change to ru.org.linux.msgbase can't break ru.org.linux.markup.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→13 ru.org.linux.msgbase uses ru.org.linux.user part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.msgbase uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.msgbase.DeleteInfoDao→ru.org.linux.user.Userru.org.linux.msgbase.InsertDeleteInfo→ru.org.linux.user.User
- Direction
- ru.org.linux.msgbase uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.msgbase, while a change to ru.org.linux.msgbase can't break ru.org.linux.user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→11 ru.org.linux.markup uses ru.org.linux.msgbase✕
- Connections
- 1 pair of types, where a type in ru.org.linux.markup uses a type in ru.org.linux.msgbase.
- The types involved
ru.org.linux.markup.MessageTextService→ru.org.linux.msgbase.MessageText
- Direction
- ru.org.linux.markup uses ru.org.linux.msgbase, so a change to ru.org.linux.msgbase can break ru.org.linux.markup, while a change to ru.org.linux.markup can't break ru.org.linux.msgbase.
- Position
- Below the diagonal: ru.org.linux.markup uses a module listed above it, which is the healthy direction.
12→13 ru.org.linux.markup uses ru.org.linux.user part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.markup uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.markup.MessageTextService→ru.org.linux.user.User
- Direction
- ru.org.linux.markup uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.markup, while a change to ru.org.linux.markup can't break ru.org.linux.user.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→3 ru.org.linux.user uses ru.org.linux.section✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.user uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.user.PreparedUserEvent→ru.org.linux.section.Sectionru.org.linux.user.PreparedUsersSectionStatEntry→ru.org.linux.section.Section
- Direction
- ru.org.linux.user uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→6 ru.org.linux.user uses ru.org.linux.tracker✕
- Connections
- 1 pair of types, where a type in ru.org.linux.user uses a type in ru.org.linux.tracker.
- The types involved
ru.org.linux.user.ProfileBuilder→ru.org.linux.tracker.TrackerFilterEnum
- Direction
- ru.org.linux.user uses ru.org.linux.tracker, so a change to ru.org.linux.tracker can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.tracker.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→7 ru.org.linux.user uses ru.org.linux.reaction✕
- Connections
- 1 pair of types, where a type in ru.org.linux.user uses a type in ru.org.linux.reaction.
- The types involved
ru.org.linux.user.PreparedUserEvent→ru.org.linux.reaction.ReactionListItem
- Direction
- ru.org.linux.user uses ru.org.linux.reaction, so a change to ru.org.linux.reaction can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.reaction.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→8 ru.org.linux.user uses ru.org.linux.scalikejdbc✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.user uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.user.UserEventDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.user.UserEventService→ru.org.linux.scalikejdbc.Transactionru.org.linux.user.UserLogDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.user.UserTagDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.user uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→11 ru.org.linux.user uses ru.org.linux.msgbase✕
- Connections
- 1 pair of types, where a type in ru.org.linux.user uses a type in ru.org.linux.msgbase.
- The types involved
ru.org.linux.user.UserEventService→ru.org.linux.msgbase.InsertDeleteInfo
- Direction
- ru.org.linux.user uses ru.org.linux.msgbase, so a change to ru.org.linux.msgbase can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.msgbase.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→12 ru.org.linux.user uses ru.org.linux.markup✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.user uses a type in ru.org.linux.markup.
- The types involved
ru.org.linux.user.Profile→ru.org.linux.markup.MarkupTyperu.org.linux.user.ProfileBuilder→ru.org.linux.markup.MarkupTyperu.org.linux.user.UserInfo→ru.org.linux.markup.MarkupTyperu.org.linux.user.UserPermissionService→ru.org.linux.markup.MarkupType
- Direction
- ru.org.linux.user uses ru.org.linux.markup, so a change to ru.org.linux.markup can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.markup.
- Position
- Below the diagonal: ru.org.linux.user uses a module listed above it, which is the healthy direction.
13→16 ru.org.linux.user uses ru.org.linux.group part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.user uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.user.PreparedUserEvent→ru.org.linux.group.Group
- Direction
- ru.org.linux.user uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.group.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→27 ru.org.linux.user uses ru.org.linux.comment part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.user uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.user.UserEventDao→ru.org.linux.comment.Commentru.org.linux.user.UserEventService→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.user uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.comment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→31 ru.org.linux.user uses ru.org.linux.topic part of a loop✕
- Connections
- 3 pairs of types, where a type in ru.org.linux.user uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.user.MemoriesDao→ru.org.linux.topic.Topicru.org.linux.user.UserEventDao→ru.org.linux.topic.Topicru.org.linux.user.UserEventService→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.user uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
13→32 ru.org.linux.user uses ru.org.linux.auth part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.user uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.user.DeregisterController→ru.org.linux.auth.AuthorizedSession
- Direction
- ru.org.linux.user uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.user, while a change to ru.org.linux.user can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→13 ru.org.linux.admin uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.admin uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.admin.PreparedEmailDomainBlock→ru.org.linux.user.User
- Direction
- ru.org.linux.admin uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.admin, while a change to ru.org.linux.admin can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.admin uses a module listed above it, which is the healthy direction.
15→13 ru.org.linux.email uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.email uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.email.EmailService→ru.org.linux.user.User
- Direction
- ru.org.linux.email uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.email, while a change to ru.org.linux.email can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.email uses a module listed above it, which is the healthy direction.
16→3 ru.org.linux.group uses ru.org.linux.section✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.group uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.group.GroupDao→ru.org.linux.section.Sectionru.org.linux.group.GroupService→ru.org.linux.section.Section
- Direction
- ru.org.linux.group uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.group, while a change to ru.org.linux.group can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.group uses a module listed above it, which is the healthy direction.
16→13 ru.org.linux.group uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.group uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.group.PreparedTopicsListItem→ru.org.linux.user.User
- Direction
- ru.org.linux.group uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.group, while a change to ru.org.linux.group can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.group uses a module listed above it, which is the healthy direction.
17→8 ru.org.linux.poll uses ru.org.linux.scalikejdbc✕
- Connections
- 1 pair of types, where a type in ru.org.linux.poll uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.poll.PollDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.poll uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.poll, while a change to ru.org.linux.poll can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.poll uses a module listed above it, which is the healthy direction.
17→9 ru.org.linux.poll uses ru.org.linux.site✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.poll uses a type in ru.org.linux.site.
- The types involved
ru.org.linux.poll.BadVoteException→ru.org.linux.site.ScriptErrorExceptionru.org.linux.poll.PollNotFoundException→ru.org.linux.site.ScriptErrorException
- Direction
- ru.org.linux.poll uses ru.org.linux.site, so a change to ru.org.linux.site can break ru.org.linux.poll, while a change to ru.org.linux.poll can't break ru.org.linux.site.
- Position
- Below the diagonal: ru.org.linux.poll uses a module listed above it, which is the healthy direction.
17→13 ru.org.linux.poll uses ru.org.linux.user✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.poll uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.poll.PollDao→ru.org.linux.user.Userru.org.linux.poll.PollPrepareService→ru.org.linux.user.User
- Direction
- ru.org.linux.poll uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.poll, while a change to ru.org.linux.poll can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.poll uses a module listed above it, which is the healthy direction.
17→31 ru.org.linux.poll uses ru.org.linux.topic part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.poll uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.poll.PollPrepareService→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.poll uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.poll, while a change to ru.org.linux.poll can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→13 ru.org.linux.realtime uses ru.org.linux.user✕
- Connections
- 3 pairs of types, where a type in ru.org.linux.realtime uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.realtime.RealtimeConfigurationBeans→ru.org.linux.user.IgnoreListDaoru.org.linux.realtime.RealtimeEventHub→ru.org.linux.user.IgnoreListDaoru.org.linux.realtime.RealtimeSessionActor→ru.org.linux.user.IgnoreListDao
- Direction
- ru.org.linux.realtime uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.realtime, while a change to ru.org.linux.realtime can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.realtime uses a module listed above it, which is the healthy direction.
19→13 ru.org.linux.util.markdown uses ru.org.linux.user✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.util.markdown uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.util.markdown.FlexmarkMarkdownFormatter→ru.org.linux.user.Userru.org.linux.util.markdown.MarkdownFormatter→ru.org.linux.user.User
- Direction
- ru.org.linux.util.markdown uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.util.markdown, while a change to ru.org.linux.util.markdown can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.util.markdown uses a module listed above it, which is the healthy direction.
20→4 ru.org.linux.exception uses ru.org.linux.spring✕
- Connections
- 1 pair of types, where a type in ru.org.linux.exception uses a type in ru.org.linux.spring.
- The types involved
ru.org.linux.exception.ExceptionHandlingConfiguration→ru.org.linux.spring.SiteConfig
- Direction
- ru.org.linux.exception uses ru.org.linux.spring, so a change to ru.org.linux.spring can break ru.org.linux.exception, while a change to ru.org.linux.exception can't break ru.org.linux.spring.
- Position
- Below the diagonal: ru.org.linux.exception uses a module listed above it, which is the healthy direction.
20→15 ru.org.linux.exception uses ru.org.linux.email✕
- Connections
- 1 pair of types, where a type in ru.org.linux.exception uses a type in ru.org.linux.email.
- The types involved
ru.org.linux.exception.ExceptionResolver→ru.org.linux.email.EmailService
- Direction
- ru.org.linux.exception uses ru.org.linux.email, so a change to ru.org.linux.email can break ru.org.linux.exception, while a change to ru.org.linux.exception can't break ru.org.linux.email.
- Position
- Below the diagonal: ru.org.linux.exception uses a module listed above it, which is the healthy direction.
21→3 ru.org.linux.rights uses ru.org.linux.section✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.rights uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.rights.AddTopicChecker→ru.org.linux.section.Sectionru.org.linux.rights.PostScoreChecker→ru.org.linux.section.Section
- Direction
- ru.org.linux.rights uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.rights, while a change to ru.org.linux.rights can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.rights uses a module listed above it, which is the healthy direction.
21→13 ru.org.linux.rights uses ru.org.linux.user✕
- Connections
- 3 pairs of types, where a type in ru.org.linux.rights uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.rights.AddCommentChecker→ru.org.linux.user.Userru.org.linux.rights.PostScoreChecker→ru.org.linux.user.Userru.org.linux.rights.SlowModeChecker→ru.org.linux.user.User
- Direction
- ru.org.linux.rights uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.rights, while a change to ru.org.linux.rights can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.rights uses a module listed above it, which is the healthy direction.
21→16 ru.org.linux.rights uses ru.org.linux.group✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.rights uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.rights.AddCommentChecker→ru.org.linux.group.Groupru.org.linux.rights.AddTopicChecker→ru.org.linux.group.Groupru.org.linux.rights.PostScoreChecker→ru.org.linux.group.Groupru.org.linux.rights.TopicPublishChecker→ru.org.linux.group.Group
- Direction
- ru.org.linux.rights uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.rights, while a change to ru.org.linux.rights can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.rights uses a module listed above it, which is the healthy direction.
21→31 ru.org.linux.rights uses ru.org.linux.topic part of a loop✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.rights uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.rights.AddCommentChecker→ru.org.linux.topic.Topicru.org.linux.rights.EditTopicChecker→ru.org.linux.topic.PreparedTopicru.org.linux.rights.EditTopicChecker→ru.org.linux.topic.Topicru.org.linux.rights.PostScoreChecker→ru.org.linux.topic.Topicru.org.linux.rights.VoteChecker→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.rights uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.rights, while a change to ru.org.linux.rights can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→32 ru.org.linux.rights uses ru.org.linux.auth part of a loop✕
- Connections
- 8 pairs of types, where a type in ru.org.linux.rights uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.rights.AddCommentChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.AddTopicChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.EditProfileChecker→ru.org.linux.auth.AuthorizedSessionru.org.linux.rights.EditTopicChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.FrozenUserChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.IpBlockChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.TopicPublishChecker→ru.org.linux.auth.AnySessionru.org.linux.rights.VoteChecker→ru.org.linux.auth.AnySession
- Direction
- ru.org.linux.rights uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.rights, while a change to ru.org.linux.rights can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→3 ru.org.linux.tag uses ru.org.linux.section✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.tag.TagService→ru.org.linux.section.Section
- Direction
- ru.org.linux.tag uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.tag, while a change to ru.org.linux.tag can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.tag uses a module listed above it, which is the healthy direction.
22→5 ru.org.linux.tag uses ru.org.linux.topic.TopicListController✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag uses a type in ru.org.linux.topic.TopicListController.
- The types involved
ru.org.linux.tag.TagService→ru.org.linux.topic.TopicListController.ForumFilter
- Direction
- ru.org.linux.tag uses ru.org.linux.topic.TopicListController, so a change to ru.org.linux.topic.TopicListController can break ru.org.linux.tag, while a change to ru.org.linux.tag can't break ru.org.linux.topic.TopicListController.
- Position
- Below the diagonal: ru.org.linux.tag uses a module listed above it, which is the healthy direction.
22→8 ru.org.linux.tag uses ru.org.linux.scalikejdbc✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.tag uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.tag.TagDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.tag.TagService→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.tag uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.tag, while a change to ru.org.linux.tag can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.tag uses a module listed above it, which is the healthy direction.
22→16 ru.org.linux.tag uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.tag.TagService→ru.org.linux.group.Group
- Direction
- ru.org.linux.tag uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.tag, while a change to ru.org.linux.tag can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.tag uses a module listed above it, which is the healthy direction.
23→3 ru.org.linux.tag.TagService uses ru.org.linux.section✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag.TagService uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.tag.TagService.ActiveTopTags→ru.org.linux.section.Section
- Direction
- ru.org.linux.tag.TagService uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.tag.TagService, while a change to ru.org.linux.tag.TagService can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.tag.TagService uses a module listed above it, which is the healthy direction.
23→5 ru.org.linux.tag.TagService uses ru.org.linux.topic.TopicListController✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag.TagService uses a type in ru.org.linux.topic.TopicListController.
- The types involved
ru.org.linux.tag.TagService.ActiveTopTags→ru.org.linux.topic.TopicListController.ForumFilter
- Direction
- ru.org.linux.tag.TagService uses ru.org.linux.topic.TopicListController, so a change to ru.org.linux.topic.TopicListController can break ru.org.linux.tag.TagService, while a change to ru.org.linux.tag.TagService can't break ru.org.linux.topic.TopicListController.
- Position
- Below the diagonal: ru.org.linux.tag.TagService uses a module listed above it, which is the healthy direction.
23→16 ru.org.linux.tag.TagService uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.tag.TagService uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.tag.TagService.ActiveTopTags→ru.org.linux.group.Group
- Direction
- ru.org.linux.tag.TagService uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.tag.TagService, while a change to ru.org.linux.tag.TagService can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.tag.TagService uses a module listed above it, which is the healthy direction.
24→3 ru.org.linux.topic.AddTopicController uses ru.org.linux.section✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic.AddTopicController uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.topic.AddTopicController.SectionChoice→ru.org.linux.section.Section
- Direction
- ru.org.linux.topic.AddTopicController uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.topic.AddTopicController, while a change to ru.org.linux.topic.AddTopicController can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.topic.AddTopicController uses a module listed above it, which is the healthy direction.
24→16 ru.org.linux.topic.AddTopicController uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic.AddTopicController uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.topic.AddTopicController.GroupChoice→ru.org.linux.group.Group
- Direction
- ru.org.linux.topic.AddTopicController uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.topic.AddTopicController, while a change to ru.org.linux.topic.AddTopicController can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.topic.AddTopicController uses a module listed above it, which is the healthy direction.
25→8 ru.org.linux.warning uses ru.org.linux.scalikejdbc✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.warning.WarningDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.warning uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.warning uses a module listed above it, which is the healthy direction.
25→13 ru.org.linux.warning uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.warning.PreparedWarning→ru.org.linux.user.User
- Direction
- ru.org.linux.warning uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.warning uses a module listed above it, which is the healthy direction.
25→16 ru.org.linux.warning uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.warning.WarningController→ru.org.linux.group.Group
- Direction
- ru.org.linux.warning uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.warning uses a module listed above it, which is the healthy direction.
25→27 ru.org.linux.warning uses ru.org.linux.comment part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.warning.PostWarningRequest→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.warning uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.comment.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→31 ru.org.linux.warning uses ru.org.linux.topic part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.warning.PostWarningRequest→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.warning uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→32 ru.org.linux.warning uses ru.org.linux.auth part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.warning uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.warning.WarningController→ru.org.linux.auth.AuthorizedSession
- Direction
- ru.org.linux.warning uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.warning, while a change to ru.org.linux.warning can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→22 ru.org.linux.boxlets uses ru.org.linux.tag✕
- Connections
- 1 pair of types, where a type in ru.org.linux.boxlets uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.boxlets.TagCloudBoxlet→ru.org.linux.tag.TagCloudDao
- Direction
- ru.org.linux.boxlets uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.boxlets, while a change to ru.org.linux.boxlets can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.boxlets uses a module listed above it, which is the healthy direction.
27→7 ru.org.linux.comment uses ru.org.linux.reaction✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.reaction.
- The types involved
ru.org.linux.comment.Comment→ru.org.linux.reaction.Reactionsru.org.linux.comment.PreparedComment→ru.org.linux.reaction.PreparedReactions
- Direction
- ru.org.linux.comment uses ru.org.linux.reaction, so a change to ru.org.linux.reaction can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.reaction.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→8 ru.org.linux.comment uses ru.org.linux.scalikejdbc✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.comment.CommentDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.comment.DeleteService→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.comment uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→11 ru.org.linux.comment uses ru.org.linux.msgbase✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.msgbase.
- The types involved
ru.org.linux.comment.CommentPrepareService→ru.org.linux.msgbase.MessageTextru.org.linux.comment.DeleteService→ru.org.linux.msgbase.InsertDeleteInfo
- Direction
- ru.org.linux.comment uses ru.org.linux.msgbase, so a change to ru.org.linux.msgbase can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.msgbase.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→13 ru.org.linux.comment uses ru.org.linux.user✕
- Connections
- 9 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.comment.CommentDao→ru.org.linux.user.Userru.org.linux.comment.CommentPrepareService→ru.org.linux.user.Userru.org.linux.comment.CommentReadService→ru.org.linux.user.Userru.org.linux.comment.CommentRequest→ru.org.linux.user.Userru.org.linux.comment.DeleteService→ru.org.linux.user.Userru.org.linux.comment.PreparedComment→ru.org.linux.user.Userru.org.linux.comment.PreparedComment→ru.org.linux.user.Userpicru.org.linux.comment.PreparedCommentsListItem→ru.org.linux.user.Userru.org.linux.comment.PreparedRSSComment→ru.org.linux.user.User
- Direction
- ru.org.linux.comment uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→16 ru.org.linux.comment uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.comment.CommentPrepareService→ru.org.linux.group.Group
- Direction
- ru.org.linux.comment uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→25 ru.org.linux.comment uses ru.org.linux.warning✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.warning.
- The types involved
ru.org.linux.comment.CommentPrepareService→ru.org.linux.warning.Warningru.org.linux.comment.PreparedComment→ru.org.linux.warning.PreparedWarning
- Direction
- ru.org.linux.comment uses ru.org.linux.warning, so a change to ru.org.linux.warning can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.warning.
- Position
- Below the diagonal: ru.org.linux.comment uses a module listed above it, which is the healthy direction.
27→31 ru.org.linux.comment uses ru.org.linux.topic part of a loop✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.comment.CommentPrepareService→ru.org.linux.topic.Topicru.org.linux.comment.CommentReadService→ru.org.linux.topic.Topicru.org.linux.comment.CommentRequest→ru.org.linux.topic.Topicru.org.linux.comment.DeleteService→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.comment uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→32 ru.org.linux.comment uses ru.org.linux.auth part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.comment uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.comment.CommentPrepareService→ru.org.linux.auth.AnySessionru.org.linux.comment.DeleteService→ru.org.linux.auth.AuthorizedSession
- Direction
- ru.org.linux.comment uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.comment, while a change to ru.org.linux.comment can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→13 ru.org.linux.site.tags uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.site.tags uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.site.tags.TagUserpic→ru.org.linux.user.Userpic
- Direction
- ru.org.linux.site.tags uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.site.tags, while a change to ru.org.linux.site.tags can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.site.tags uses a module listed above it, which is the healthy direction.
28→22 ru.org.linux.site.tags uses ru.org.linux.tag✕
- Connections
- 1 pair of types, where a type in ru.org.linux.site.tags uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.site.tags.TagsTag→ru.org.linux.tag.TagRef
- Direction
- ru.org.linux.site.tags uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.site.tags, while a change to ru.org.linux.site.tags can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.site.tags uses a module listed above it, which is the healthy direction.
29→27 ru.org.linux.comment.DeleteService uses ru.org.linux.comment✕
- Connections
- 1 pair of types, where a type in ru.org.linux.comment.DeleteService uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.comment.DeleteService.CommentAndDepth→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.comment.DeleteService uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.comment.DeleteService, while a change to ru.org.linux.comment.DeleteService can't break ru.org.linux.comment.
- Position
- Below the diagonal: ru.org.linux.comment.DeleteService uses a module listed above it, which is the healthy direction.
30→8 ru.org.linux.edithistory uses ru.org.linux.scalikejdbc✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.edithistory.EditHistoryDao→ru.org.linux.scalikejdbc.Transactionru.org.linux.edithistory.EditHistoryService→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.edithistory uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.edithistory uses a module listed above it, which is the healthy direction.
30→13 ru.org.linux.edithistory uses ru.org.linux.user✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.edithistory.EditHistoryService→ru.org.linux.user.Userru.org.linux.edithistory.PreparedEditHistory→ru.org.linux.user.User
- Direction
- ru.org.linux.edithistory uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.edithistory uses a module listed above it, which is the healthy direction.
30→17 ru.org.linux.edithistory uses ru.org.linux.poll✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.poll.
- The types involved
ru.org.linux.edithistory.EditHistoryRecord→ru.org.linux.poll.Pollru.org.linux.edithistory.PreparedEditHistory→ru.org.linux.poll.Poll
- Direction
- ru.org.linux.edithistory uses ru.org.linux.poll, so a change to ru.org.linux.poll can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.poll.
- Position
- Below the diagonal: ru.org.linux.edithistory uses a module listed above it, which is the healthy direction.
30→22 ru.org.linux.edithistory uses ru.org.linux.tag✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.edithistory.PreparedEditHistory→ru.org.linux.tag.TagRef
- Direction
- ru.org.linux.edithistory uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.edithistory uses a module listed above it, which is the healthy direction.
30→27 ru.org.linux.edithistory uses ru.org.linux.comment✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.edithistory.EditHistoryService→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.edithistory uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.comment.
- Position
- Below the diagonal: ru.org.linux.edithistory uses a module listed above it, which is the healthy direction.
30→31 ru.org.linux.edithistory uses ru.org.linux.topic part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.edithistory.EditHistoryService→ru.org.linux.topic.Topicru.org.linux.edithistory.PreparedEditHistory→ru.org.linux.topic.PreparedImage
- Direction
- ru.org.linux.edithistory uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.topic.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→35 ru.org.linux.edithistory uses ru.org.linux.gallery part of a loop✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory uses a type in ru.org.linux.gallery.
- The types involved
ru.org.linux.edithistory.EditHistoryService→ru.org.linux.gallery.Imageru.org.linux.edithistory.PreparedEditHistory→ru.org.linux.gallery.Image
- Direction
- ru.org.linux.edithistory uses ru.org.linux.gallery, so a change to ru.org.linux.gallery can break ru.org.linux.edithistory, while a change to ru.org.linux.edithistory can't break ru.org.linux.gallery.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→3 ru.org.linux.topic uses ru.org.linux.section✕
- Connections
- 7 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.topic.AddTopicController→ru.org.linux.section.Sectionru.org.linux.topic.ArchiveDao→ru.org.linux.section.Sectionru.org.linux.topic.ArchiveStats→ru.org.linux.section.Sectionru.org.linux.topic.PreparedTopic→ru.org.linux.section.Sectionru.org.linux.topic.TagTopicListController→ru.org.linux.section.Sectionru.org.linux.topic.TopicListController→ru.org.linux.section.Sectionru.org.linux.topic.TopicService→ru.org.linux.section.Section
- Direction
- ru.org.linux.topic uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→5 ru.org.linux.topic uses ru.org.linux.topic.TopicListController✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.topic.TopicListController.
- The types involved
ru.org.linux.topic.TopicListForm→ru.org.linux.topic.TopicListController.ForumFilter
- Direction
- ru.org.linux.topic uses ru.org.linux.topic.TopicListController, so a change to ru.org.linux.topic.TopicListController can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.topic.TopicListController.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→7 ru.org.linux.topic uses ru.org.linux.reaction✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.reaction.
- The types involved
ru.org.linux.topic.PreparedTopic→ru.org.linux.reaction.PreparedReactionsru.org.linux.topic.Topic→ru.org.linux.reaction.Reactions
- Direction
- ru.org.linux.topic uses ru.org.linux.reaction, so a change to ru.org.linux.reaction can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.reaction.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→8 ru.org.linux.topic uses ru.org.linux.scalikejdbc✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.topic.TopicTagDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.topic uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→9 ru.org.linux.topic uses ru.org.linux.site✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.site.
- The types involved
ru.org.linux.topic.PreparedTopic→ru.org.linux.site.DeleteInfo
- Direction
- ru.org.linux.topic uses ru.org.linux.site, so a change to ru.org.linux.site can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.site.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→11 ru.org.linux.topic uses ru.org.linux.msgbase✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.msgbase.
- The types involved
ru.org.linux.topic.EditTopicController→ru.org.linux.msgbase.MessageTextru.org.linux.topic.TopicPrepareService→ru.org.linux.msgbase.MessageText
- Direction
- ru.org.linux.topic uses ru.org.linux.msgbase, so a change to ru.org.linux.msgbase can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.msgbase.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→12 ru.org.linux.topic uses ru.org.linux.markup✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.markup.
- The types involved
ru.org.linux.topic.PreparedTopic→ru.org.linux.markup.MarkupType
- Direction
- ru.org.linux.topic uses ru.org.linux.markup, so a change to ru.org.linux.markup can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.markup.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→13 ru.org.linux.topic uses ru.org.linux.user✕
- Connections
- 7 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.topic.AddTopicRequest→ru.org.linux.user.Userru.org.linux.topic.EditTopicRequest→ru.org.linux.user.Userru.org.linux.topic.PreparedGalleryItem→ru.org.linux.user.Userru.org.linux.topic.PreparedTopic→ru.org.linux.user.Remarkru.org.linux.topic.PreparedTopic→ru.org.linux.user.Userru.org.linux.topic.TopicListDao→ru.org.linux.user.Userru.org.linux.topic.TopicMenu→ru.org.linux.user.Userpic
- Direction
- ru.org.linux.topic uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→16 ru.org.linux.topic uses ru.org.linux.group✕
- Connections
- 8 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.topic.AddTopicController→ru.org.linux.group.Groupru.org.linux.topic.AddTopicRequest→ru.org.linux.group.Groupru.org.linux.topic.ArchiveDao→ru.org.linux.group.Groupru.org.linux.topic.ArchiveStats→ru.org.linux.group.Groupru.org.linux.topic.PreparedTopic→ru.org.linux.group.Groupru.org.linux.topic.TopicListController→ru.org.linux.group.Groupru.org.linux.topic.TopicPrepareService→ru.org.linux.group.PreparedTopicsListItemru.org.linux.topic.TopicPrepareService→ru.org.linux.group.TopicsListItem
- Direction
- ru.org.linux.topic uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→17 ru.org.linux.topic uses ru.org.linux.poll✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.poll.
- The types involved
ru.org.linux.topic.AddTopicController→ru.org.linux.poll.Pollru.org.linux.topic.EditTopicController→ru.org.linux.poll.Pollru.org.linux.topic.PreparedTopic→ru.org.linux.poll.PreparedPollru.org.linux.topic.TopicPrepareService→ru.org.linux.poll.Pollru.org.linux.topic.TopicPrepareService→ru.org.linux.poll.PreparedPoll
- Direction
- ru.org.linux.topic uses ru.org.linux.poll, so a change to ru.org.linux.poll can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.poll.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→21 ru.org.linux.topic uses ru.org.linux.rights✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.rights.
- The types involved
ru.org.linux.topic.EditTopicController→ru.org.linux.rights.Permission
- Direction
- ru.org.linux.topic uses ru.org.linux.rights, so a change to ru.org.linux.rights can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.rights.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→22 ru.org.linux.topic uses ru.org.linux.tag✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.topic.PreparedTopic→ru.org.linux.tag.TagRefru.org.linux.topic.SectionRssFeedView→ru.org.linux.tag.TagRefru.org.linux.topic.TopicPrepareService→ru.org.linux.tag.TagRefru.org.linux.topic.TopicTagDao→ru.org.linux.tag.TagInforu.org.linux.topic.TopicTagService→ru.org.linux.tag.TagRef
- Direction
- ru.org.linux.topic uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→25 ru.org.linux.topic uses ru.org.linux.warning✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.warning.
- The types involved
ru.org.linux.topic.PreparedTopic→ru.org.linux.warning.PreparedWarningru.org.linux.topic.TopicPrepareService→ru.org.linux.warning.Warning
- Direction
- ru.org.linux.topic uses ru.org.linux.warning, so a change to ru.org.linux.warning can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.warning.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→30 ru.org.linux.topic uses ru.org.linux.edithistory✕
- Connections
- 1 pair of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.edithistory.
- The types involved
ru.org.linux.topic.TopicPrepareService→ru.org.linux.edithistory.EditInfoSummary
- Direction
- ru.org.linux.topic uses ru.org.linux.edithistory, so a change to ru.org.linux.edithistory can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.edithistory.
- Position
- Below the diagonal: ru.org.linux.topic uses a module listed above it, which is the healthy direction.
31→32 ru.org.linux.topic uses ru.org.linux.auth part of a loop✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.topic.DeleteTopicController→ru.org.linux.auth.AuthorizedSessionru.org.linux.topic.EditTopicController→ru.org.linux.auth.AuthorizedSessionru.org.linux.topic.TopicController→ru.org.linux.auth.AnySessionru.org.linux.topic.TopicPrepareService→ru.org.linux.auth.AnySessionru.org.linux.topic.UserTopicListController→ru.org.linux.auth.AnySession
- Direction
- ru.org.linux.topic uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.auth.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
31→35 ru.org.linux.topic uses ru.org.linux.gallery part of a loop✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.topic uses a type in ru.org.linux.gallery.
- The types involved
ru.org.linux.topic.EditTopicController→ru.org.linux.gallery.UploadedImagePreviewru.org.linux.topic.PreparedGalleryItem→ru.org.linux.gallery.GalleryItemru.org.linux.topic.PreparedImage→ru.org.linux.gallery.Imageru.org.linux.topic.TopicPrepareService→ru.org.linux.gallery.Imageru.org.linux.topic.TopicPrepareService→ru.org.linux.gallery.UploadedImagePreview
- Direction
- ru.org.linux.topic uses ru.org.linux.gallery, so a change to ru.org.linux.gallery can break ru.org.linux.topic, while a change to ru.org.linux.topic can't break ru.org.linux.gallery.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→13 ru.org.linux.auth uses ru.org.linux.user✕
- Connections
- 14 pairs of types, where a type in ru.org.linux.auth uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.auth.AccessViolationException→ru.org.linux.user.UserErrorExceptionru.org.linux.auth.AnySession→ru.org.linux.user.Profileru.org.linux.auth.AnySession→ru.org.linux.user.Userru.org.linux.auth.AuthUtil→ru.org.linux.user.Profileru.org.linux.auth.AuthUtil→ru.org.linux.user.Userru.org.linux.auth.AuthUtil→ru.org.linux.user.UserServiceru.org.linux.auth.AuthorizedSession→ru.org.linux.user.Profileru.org.linux.auth.AuthorizedSession→ru.org.linux.user.Userru.org.linux.auth.GenerationBasedTokenRememberMeServices→ru.org.linux.user.UserDaoru.org.linux.auth.NonAuthorizedSession→ru.org.linux.user.Profileru.org.linux.auth.NonAuthorizedSession→ru.org.linux.user.Userru.org.linux.auth.UserDetailsImpl→ru.org.linux.user.Profileru.org.linux.auth.UserDetailsImpl→ru.org.linux.user.Userru.org.linux.auth.UserDetailsServiceImpl→ru.org.linux.user.User
- Direction
- ru.org.linux.auth uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.auth, while a change to ru.org.linux.auth can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.auth uses a module listed above it, which is the healthy direction.
32→31 ru.org.linux.auth uses ru.org.linux.topic✕
- Connections
- 1 pair of types, where a type in ru.org.linux.auth uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.auth.GalleryPermissionInterceptor→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.auth uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.auth, while a change to ru.org.linux.auth can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.auth uses a module listed above it, which is the healthy direction.
32→35 ru.org.linux.auth uses ru.org.linux.gallery part of a loop✕
- Connections
- 1 pair of types, where a type in ru.org.linux.auth uses a type in ru.org.linux.gallery.
- The types involved
ru.org.linux.auth.GalleryPermissionInterceptor→ru.org.linux.gallery.Image
- Direction
- ru.org.linux.auth uses ru.org.linux.gallery, so a change to ru.org.linux.gallery can break ru.org.linux.auth, while a change to ru.org.linux.auth can't break ru.org.linux.gallery.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
33→13 ru.org.linux.search uses ru.org.linux.user✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.search uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.search.SearchItem→ru.org.linux.user.Userru.org.linux.search.SearchServiceRequest→ru.org.linux.user.User
- Direction
- ru.org.linux.search uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.search, while a change to ru.org.linux.search can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.search uses a module listed above it, which is the healthy direction.
33→22 ru.org.linux.search uses ru.org.linux.tag✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.search uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.search.MoreLikeThisService→ru.org.linux.tag.TagRefru.org.linux.search.SearchItem→ru.org.linux.tag.TagRefru.org.linux.search.SearchService→ru.org.linux.tag.TagRefru.org.linux.search.SearchServiceResponse→ru.org.linux.tag.TagRef
- Direction
- ru.org.linux.search uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.search, while a change to ru.org.linux.search can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.search uses a module listed above it, which is the healthy direction.
33→31 ru.org.linux.search uses ru.org.linux.topic✕
- Connections
- 1 pair of types, where a type in ru.org.linux.search uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.search.MoreLikeThisService→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.search uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.search, while a change to ru.org.linux.search can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.search uses a module listed above it, which is the healthy direction.
34→16 ru.org.linux.util uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.util.LorURL→ru.org.linux.group.GroupService
- Direction
- ru.org.linux.util uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.util, while a change to ru.org.linux.util can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.util uses a module listed above it, which is the healthy direction.
34→31 ru.org.linux.util uses ru.org.linux.topic✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.util.LorURL→ru.org.linux.topic.TopicDao
- Direction
- ru.org.linux.util uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.util, while a change to ru.org.linux.util can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.util uses a module listed above it, which is the healthy direction.
35→3 ru.org.linux.gallery uses ru.org.linux.section✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.section.
- The types involved
ru.org.linux.gallery.ImageDao→ru.org.linux.section.Sectionru.org.linux.gallery.ImageDao→ru.org.linux.section.SectionService
- Direction
- ru.org.linux.gallery uses ru.org.linux.section, so a change to ru.org.linux.section can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.section.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→8 ru.org.linux.gallery uses ru.org.linux.scalikejdbc✕
- Connections
- 1 pair of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.scalikejdbc.
- The types involved
ru.org.linux.gallery.ImageDao→ru.org.linux.scalikejdbc.Transaction
- Direction
- ru.org.linux.gallery uses ru.org.linux.scalikejdbc, so a change to ru.org.linux.scalikejdbc can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.scalikejdbc.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→9 ru.org.linux.gallery uses ru.org.linux.site✕
- Connections
- 1 pair of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.site.
- The types involved
ru.org.linux.gallery.ImageNotFoundException→ru.org.linux.site.ScriptErrorException
- Direction
- ru.org.linux.gallery uses ru.org.linux.site, so a change to ru.org.linux.site can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.site.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→13 ru.org.linux.gallery uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.gallery.ImageService→ru.org.linux.user.User
- Direction
- ru.org.linux.gallery uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→26 ru.org.linux.gallery uses ru.org.linux.boxlets✕
- Connections
- 1 pair of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.boxlets.
- The types involved
ru.org.linux.gallery.GalleryBoxlet→ru.org.linux.boxlets.AbstractBoxlet
- Direction
- ru.org.linux.gallery uses ru.org.linux.boxlets, so a change to ru.org.linux.boxlets can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.boxlets.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→31 ru.org.linux.gallery uses ru.org.linux.topic✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.gallery.DeleteImageController→ru.org.linux.topic.PreparedTopicru.org.linux.gallery.ImageService→ru.org.linux.topic.PreparedGalleryItemru.org.linux.gallery.ImageService→ru.org.linux.topic.PreparedImageru.org.linux.gallery.ImageService→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.gallery uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
35→32 ru.org.linux.gallery uses ru.org.linux.auth✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.gallery uses a type in ru.org.linux.auth.
- The types involved
ru.org.linux.gallery.DeleteImageController→ru.org.linux.auth.AuthorizedSessionru.org.linux.gallery.ImageService→ru.org.linux.auth.AuthorizedSession
- Direction
- ru.org.linux.gallery uses ru.org.linux.auth, so a change to ru.org.linux.auth can break ru.org.linux.gallery, while a change to ru.org.linux.gallery can't break ru.org.linux.auth.
- Position
- Below the diagonal: ru.org.linux.gallery uses a module listed above it, which is the healthy direction.
36→4 ru.org.linux.util.formatter uses ru.org.linux.spring✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.spring.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.spring.SiteConfig
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.spring, so a change to ru.org.linux.spring can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.spring.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
36→13 ru.org.linux.util.formatter uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.user.User
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
36→16 ru.org.linux.util.formatter uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.group.GroupService
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
36→27 ru.org.linux.util.formatter uses ru.org.linux.comment✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.comment.CommentDao
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.comment.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
36→31 ru.org.linux.util.formatter uses ru.org.linux.topic✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.topic.TopicDao
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
36→34 ru.org.linux.util.formatter uses ru.org.linux.util✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.formatter uses a type in ru.org.linux.util.
- The types involved
ru.org.linux.util.formatter.ToHtmlFormatter→ru.org.linux.util.LorURL
- Direction
- ru.org.linux.util.formatter uses ru.org.linux.util, so a change to ru.org.linux.util can break ru.org.linux.util.formatter, while a change to ru.org.linux.util.formatter can't break ru.org.linux.util.
- Position
- Below the diagonal: ru.org.linux.util.formatter uses a module listed above it, which is the healthy direction.
37→2 ru.org.linux uses ru.org.linux.adv✕
- Connections
- 1 pair of types, where a type in ru.org.linux uses a type in ru.org.linux.adv.
- The types involved
ru.org.linux.ImagesResourcesConfiguration→ru.org.linux.adv.AdvCounterDao
- Direction
- ru.org.linux uses ru.org.linux.adv, so a change to ru.org.linux.adv can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.adv.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
37→4 ru.org.linux uses ru.org.linux.spring✕
- Connections
- 1 pair of types, where a type in ru.org.linux uses a type in ru.org.linux.spring.
- The types involved
ru.org.linux.HttpClientConfiguration→ru.org.linux.spring.SiteConfig
- Direction
- ru.org.linux uses ru.org.linux.spring, so a change to ru.org.linux.spring can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.spring.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
37→13 ru.org.linux uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.ImagesResourcesConfiguration→ru.org.linux.user.UserService
- Direction
- ru.org.linux uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
37→16 ru.org.linux uses ru.org.linux.group✕
- Connections
- 1 pair of types, where a type in ru.org.linux uses a type in ru.org.linux.group.
- The types involved
ru.org.linux.ImagesResourcesConfiguration→ru.org.linux.group.GroupService
- Direction
- ru.org.linux uses ru.org.linux.group, so a change to ru.org.linux.group can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.group.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
37→31 ru.org.linux uses ru.org.linux.topic✕
- Connections
- 2 pairs of types, where a type in ru.org.linux uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.ImagesResourcesConfiguration→ru.org.linux.topic.TopicPermissionServiceru.org.linux.ImagesResourcesConfiguration→ru.org.linux.topic.TopicService
- Direction
- ru.org.linux uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
37→35 ru.org.linux uses ru.org.linux.gallery✕
- Connections
- 1 pair of types, where a type in ru.org.linux uses a type in ru.org.linux.gallery.
- The types involved
ru.org.linux.ImagesResourcesConfiguration→ru.org.linux.gallery.ImageDao
- Direction
- ru.org.linux uses ru.org.linux.gallery, so a change to ru.org.linux.gallery can break ru.org.linux, while a change to ru.org.linux can't break ru.org.linux.gallery.
- Position
- Below the diagonal: ru.org.linux uses a module listed above it, which is the healthy direction.
38→12 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.markup✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.markup.
- The types involved
ru.org.linux.edithistory.EditHistoryService.CommentEditHistoryState→ru.org.linux.markup.MarkupTyperu.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.markup.MarkupType
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.markup, so a change to ru.org.linux.markup can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.markup.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→17 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.poll✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.poll.
- The types involved
ru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.poll.Poll
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.poll, so a change to ru.org.linux.poll can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.poll.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→22 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.tag✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.tag.
- The types involved
ru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.tag.TagRef
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.tag, so a change to ru.org.linux.tag can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.tag.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→27 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.comment✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.comment.
- The types involved
ru.org.linux.edithistory.EditHistoryService.CommentEditHistoryState→ru.org.linux.comment.Comment
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.comment, so a change to ru.org.linux.comment can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.comment.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→30 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.edithistory✕
- Connections
- 4 pairs of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.edithistory.
- The types involved
ru.org.linux.edithistory.EditHistoryService.CommentEditHistoryState→ru.org.linux.edithistory.EditHistoryRecordru.org.linux.edithistory.EditHistoryService.CommentEditHistoryState→ru.org.linux.edithistory.PreparedEditHistoryru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.edithistory.EditHistoryRecordru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.edithistory.PreparedEditHistory
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.edithistory, so a change to ru.org.linux.edithistory can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.edithistory.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→31 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.topic✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.topic.
- The types involved
ru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.topic.Topic
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.topic, so a change to ru.org.linux.topic can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.topic.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
38→35 ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.gallery✕
- Connections
- 1 pair of types, where a type in ru.org.linux.edithistory.EditHistoryService uses a type in ru.org.linux.gallery.
- The types involved
ru.org.linux.edithistory.EditHistoryService.TopicEditHistoryState→ru.org.linux.gallery.Image
- Direction
- ru.org.linux.edithistory.EditHistoryService uses ru.org.linux.gallery, so a change to ru.org.linux.gallery can break ru.org.linux.edithistory.EditHistoryService, while a change to ru.org.linux.edithistory.EditHistoryService can't break ru.org.linux.gallery.
- Position
- Below the diagonal: ru.org.linux.edithistory.EditHistoryService uses a module listed above it, which is the healthy direction.
39→10 ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.bbcode.tags✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.bbcode.nodes uses a type in ru.org.linux.util.bbcode.tags.
- The types involved
ru.org.linux.util.bbcode.nodes.TagNode→ru.org.linux.util.bbcode.tags.Tag
- Direction
- ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.bbcode.tags, so a change to ru.org.linux.util.bbcode.tags can break ru.org.linux.util.bbcode.nodes, while a change to ru.org.linux.util.bbcode.nodes can't break ru.org.linux.util.bbcode.tags.
- Position
- Below the diagonal: ru.org.linux.util.bbcode.nodes uses a module listed above it, which is the healthy direction.
39→13 ru.org.linux.util.bbcode.nodes uses ru.org.linux.user✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.util.bbcode.nodes uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.user.Userru.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.user.UserService
- Direction
- ru.org.linux.util.bbcode.nodes uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.util.bbcode.nodes, while a change to ru.org.linux.util.bbcode.nodes can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.util.bbcode.nodes uses a module listed above it, which is the healthy direction.
39→34 ru.org.linux.util.bbcode.nodes uses ru.org.linux.util✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.bbcode.nodes uses a type in ru.org.linux.util.
- The types involved
ru.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.util.LorURI
- Direction
- ru.org.linux.util.bbcode.nodes uses ru.org.linux.util, so a change to ru.org.linux.util can break ru.org.linux.util.bbcode.nodes, while a change to ru.org.linux.util.bbcode.nodes can't break ru.org.linux.util.
- Position
- Below the diagonal: ru.org.linux.util.bbcode.nodes uses a module listed above it, which is the healthy direction.
39→36 ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.formatter✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.bbcode.nodes uses a type in ru.org.linux.util.formatter.
- The types involved
ru.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.util.formatter.ToHtmlFormatter
- Direction
- ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.formatter, so a change to ru.org.linux.util.formatter can break ru.org.linux.util.bbcode.nodes, while a change to ru.org.linux.util.bbcode.nodes can't break ru.org.linux.util.formatter.
- Position
- Below the diagonal: ru.org.linux.util.bbcode.nodes uses a module listed above it, which is the healthy direction.
39→40 ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.bbcode part of a loop✕
- Connections
- 8 pairs of types, where a type in ru.org.linux.util.bbcode.nodes uses a type in ru.org.linux.util.bbcode.
- The types involved
ru.org.linux.util.bbcode.nodes.Node→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.util.bbcode.CutTyperu.org.linux.util.bbcode.nodes.RootNode→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.nodes.TagNode→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.nodes.TextCodeNode→ru.org.linux.util.bbcode.ParserAutomatonStateru.org.linux.util.bbcode.nodes.TextCodeNode→ru.org.linux.util.bbcode.ParserParametersru.org.linux.util.bbcode.nodes.TextNode→ru.org.linux.util.bbcode.ParserAutomatonStateru.org.linux.util.bbcode.nodes.TextNode→ru.org.linux.util.bbcode.ParserParameters
- Direction
- ru.org.linux.util.bbcode.nodes uses ru.org.linux.util.bbcode, so a change to ru.org.linux.util.bbcode can break ru.org.linux.util.bbcode.nodes, while a change to ru.org.linux.util.bbcode.nodes can't break ru.org.linux.util.bbcode.
- 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.
40→10 ru.org.linux.util.bbcode uses ru.org.linux.util.bbcode.tags✕
- Connections
- 2 pairs of types, where a type in ru.org.linux.util.bbcode uses a type in ru.org.linux.util.bbcode.tags.
- The types involved
ru.org.linux.util.bbcode.DefaultParserParameters→ru.org.linux.util.bbcode.tags.Tagru.org.linux.util.bbcode.ParserParameters→ru.org.linux.util.bbcode.tags.Tag
- Direction
- ru.org.linux.util.bbcode uses ru.org.linux.util.bbcode.tags, so a change to ru.org.linux.util.bbcode.tags can break ru.org.linux.util.bbcode, while a change to ru.org.linux.util.bbcode can't break ru.org.linux.util.bbcode.tags.
- Position
- Below the diagonal: ru.org.linux.util.bbcode uses a module listed above it, which is the healthy direction.
40→13 ru.org.linux.util.bbcode uses ru.org.linux.user✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.bbcode uses a type in ru.org.linux.user.
- The types involved
ru.org.linux.util.bbcode.LorCodeService→ru.org.linux.user.User
- Direction
- ru.org.linux.util.bbcode uses ru.org.linux.user, so a change to ru.org.linux.user can break ru.org.linux.util.bbcode, while a change to ru.org.linux.util.bbcode can't break ru.org.linux.user.
- Position
- Below the diagonal: ru.org.linux.util.bbcode uses a module listed above it, which is the healthy direction.
40→36 ru.org.linux.util.bbcode uses ru.org.linux.util.formatter✕
- Connections
- 1 pair of types, where a type in ru.org.linux.util.bbcode uses a type in ru.org.linux.util.formatter.
- The types involved
ru.org.linux.util.bbcode.ParserAutomatonState→ru.org.linux.util.formatter.RuTypoChanger
- Direction
- ru.org.linux.util.bbcode uses ru.org.linux.util.formatter, so a change to ru.org.linux.util.formatter can break ru.org.linux.util.bbcode, while a change to ru.org.linux.util.bbcode can't break ru.org.linux.util.formatter.
- Position
- Below the diagonal: ru.org.linux.util.bbcode uses a module listed above it, which is the healthy direction.
40→39 ru.org.linux.util.bbcode uses ru.org.linux.util.bbcode.nodes✕
- Connections
- 5 pairs of types, where a type in ru.org.linux.util.bbcode uses a type in ru.org.linux.util.bbcode.nodes.
- The types involved
ru.org.linux.util.bbcode.NodeUtils→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.Parser→ru.org.linux.util.bbcode.nodes.Noderu.org.linux.util.bbcode.Parser→ru.org.linux.util.bbcode.nodes.RootNoderu.org.linux.util.bbcode.Parser→ru.org.linux.util.bbcode.nodes.TextNoderu.org.linux.util.bbcode.ParserAutomatonState→ru.org.linux.util.bbcode.nodes.RootNode
- Direction
- ru.org.linux.util.bbcode uses ru.org.linux.util.bbcode.nodes, so a change to ru.org.linux.util.bbcode.nodes can break ru.org.linux.util.bbcode, while a change to ru.org.linux.util.bbcode can't break ru.org.linux.util.bbcode.nodes.
- Position
- Below the diagonal: ru.org.linux.util.bbcode uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 8 | High / Critical |
| A02:2025 — Security Misconfiguration | 6 | Medium |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A01:2025 — Broken Access Control | 2 | Medium |
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value; Bring the 46 bodies over 15 down to 15 or less in Cognitive Complexity — start with LorURL.findURLIds (cognitive 57), EditTopicController.edit (cognitive 54), TopicPermissionService.checkView (cognitive 44).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.6 pts | Low | ADR Quality |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +4.7 pts | Medium | Type Safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +4.7 pts | Medium | Dead Code |
| Bring the 46 bodies over 15 down to 15 or less in Cognitive Complexity — start with LorURL.findURLIds (cognitive 57), EditTopicController.edit (cognitive 54), TopicPermissionService.checkView (cognitive 44). | +3.9 pts | High | Cognitive Complexity |
| On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it. | +3.5 pts | Medium | Nullable reference types |
| Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +2.5 pts | Medium | Security & performance tooling |
| Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery. | +2.5 pts | Medium | DR & Backup |
| Interpolated log message defeats structured logging | +2.2 pts | Medium | Structured logging |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.2 | Slop | Static Analysis (SAST): High: REDACTED |
| src/main/scala/ru/org/linux/topic/TopicListDao.scala | 6.3 | Mixed | Cyclomatic Complexity: TopicListDao.makeConditions (cyclomatic 24) |
| src/main/scala/ru/org/linux/comment/CommentDao.scala | 6.3 | Mixed | Code Duplication: Duplicated block (50–55 lines × 2) |
| src/main/scala/ru/org/linux/util/markdown/LorLinkExtension.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/ru/org/linux/edithistory/EditHistoryService.scala | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 6.9 | Mixed | Data Compliance (PII/GDPR): Medium: REDACTED |
| src/main/scala/ru/org/linux/user/RegisterController.scala | 7.0 | Mixed | Cognitive Complexity: RegisterController.doRegister (cognitive 16) |
| src/main/scala/ru/org/linux/user/UserDao.scala | 7.0 | Mixed | God Classes: TooManyMethods: UserDao |
| src/main/scala/ru/org/linux/user/UserService.scala | 7.0 | Mixed | God Classes: TooManyMethods: UserService |
| src/main/webapp/js/add-form.js | 7.1 | Mixed | Cyclomatic Complexity: (anonymous) (cyclomatic 67) |
| src/main/java/ru/org/linux/util/bbcode/Parser.java | 7.2 | Mixed | Cyclomatic Complexity: Parser.pushTextNode (cyclomatic 17) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| src/main/scala/ru/org/linux/markup/MessageTextService.scala | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/java/ru/org/linux/util/bbcode/DefaultParserParameters.java | 7.3 | Mixed | Explicit Debt: TodoComment |
| src/main/scala/ru/org/linux/topic/EditTopicController.scala | 7.4 | Mixed | Cyclomatic Complexity: EditTopicController.edit (cyclomatic 40) |
| src/main/scala/ru/org/linux/topic/TopicPermissionService.scala | 7.4 | Mixed | Cyclomatic Complexity: TopicPermissionService.checkView (cyclomatic 19) |
| src/main/scala/ru/org/linux/topic/UserTopicListController.scala | 7.4 | Mixed | Code Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens) |
| src/main/webapp/js/jquery.hotkeys.js | 7.8 | Mixed | Cyclomatic Complexity: jquery.hotkeys.keyHandler (cyclomatic 39) |
| src/main/scala/ru/org/linux/topic/TopicController.scala | 7.8 | Mixed | Cyclomatic Complexity: TopicController.getMessage (cyclomatic 26) |
| src/main/scala/ru/org/linux/user/WhoisController.scala | 7.8 | Mixed | Cyclomatic Complexity: WhoisController.getInfoNew (cyclomatic 26) |
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 75 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 75 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, 248 of 260 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.scala) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 72 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- 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 (102 contributor(s) across 10099 commit(s) sampled, automation and bot accounts excluded). One of them holds 87% of the history; the other 101 hold 0.1% 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- D27 Navigability — 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D32 Data Compliance (PII/GDPR) — 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. `src/main/scala/ru/org/linux/SpringSecurityConfiguration.scala`, `src/main/scala/ru/org/linux/adv/AdvCounterDao.scala`, `src/main/scala/ru/org/linux/auth/IpBlockDao.scala`, `src/main/scala/ru/org/linux/auth/LoginAttemptCache.scala`, `src/main/scala/ru/org/linux/auth/LoginController.scala`, … (+51 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AC2 Forms & labels — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
- AX1 Captive dependencies — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository also uses Spring (Scala), whose singleton and shorter-lived bindings can capture one another the same way, but this check does not read them yet. That is a gap in this analyzer's language reach — not a finding that those bindings are free of it.
- AXR1 Runtime accessibility — 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. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 1 — a container did not start, exited, or never became healthy) — app Built Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown; runtime evidence skipped.
- 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. 'scalikejdbc' is imported (src/main/scala/ru/org/linux/warning/WarningDao.scala:21), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 'scalikejdbc' is imported (src/main/scala/ru/org/linux/warning/WarningDao.scala:21), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- 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. 'scalikejdbc' is imported (src/main/scala/ru/org/linux/warning/WarningDao.scala:21), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- P8 Schema migrations — 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- 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.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
21 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was (anonymous) at 67.
What to do
- Bring the 5 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with (anonymous) (cyclomatic 67), EditTopicController.edit (cyclomatic 40), jquery.hotkeys.keyHandler (cyclomatic 39). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
46 method(s) exceeded the cognitive complexity threshold of 15; the worst was LorURL.findURLIds at 57.
What to do
- Bring the 46 bodies over 15 down to 15 or less in Cognitive Complexity — start with LorURL.findURLIds (cognitive 57), EditTopicController.edit (cognitive 54), TopicPermissionService.checkView (cognitive 44). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 46 together lifts Cognitive Complexity from 6.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with UserDao.scala, UserService.scala, TopicDao.scala. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with add-form.js. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
15 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AddCommentController.scala, UserEventPrepareService.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DateFormats.scala, EditProfileRequestValidator.scala. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with UserTopicListController.scala. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
9 of 33 classes have LCOM4 above 3.
What to do
- Resolve the 9 Low cohesion finding(s) in Cohesion (LCOM4) — start with UserDao.scala, SiteConfig.scala, UserService.scala. — One of this dimension's main actionable groups (9 warning-level).
- Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D9 · Test Distribution
792 test methods: 506 unit, 286 integration, 0 BDD, 0 e2e. The Scala suite contributes 792 test case(s) across 113 file(s) in a test source set declaring at least one — every `test("…")`, `it("…")`, `property("…")` and `"…" in {…}` registration and every JUnit `@Test`, which is how munit, ScalaTest, utest, ZIO Test and specs2 declare a case; a case registered under a computed name is not counted, so this is a floor. Its tier split is INFERRED from paths and file names, except sbt's src/it source set, which the build declares.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main/scala/ru/org/linux/topic/EditTopicController.scala (7×40=280); src/main/scala/ru/org/linux/topic/AddTopicController.scala (6×18=108); src/main/scala/ru/org/linux/user/EditProfileController.scala (3×17=51)
What to do
- Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with EditTopicController.scala, AddTopicController.scala, EditProfileController.scala. — One of this dimension's main actionable groups (4 warning-level).
D17 · Explicit Debt
6 deducted task-comment markers across 32668 LoC (0.0/KLoC) → score 10.0. 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 6 TodoComment finding(s) in Explicit Debt — start with MessageTextService.scala (2), DefaultParserParameters.java (2), LorLinkExtension.scala. — One of this dimension's main actionable groups (6 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
8 finding(s): 0 critical, 3 high, 5 medium, 0 low. 2 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 46 file(s) — `mvnw` (line 86, line 124, line 134, …), `src/main/scala/ru/org/linux/adv/AdvCounterDao.scala`, `src/main/scala/ru/org/linux/auth/IpBlockDao.scala`, `src/main/scala/ru/org/linux/auth/LoginController.scala`, `src/main/scala/ru/org/linux/comment/CommentDao.scala`, … (+41 more) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 2 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 (2 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D31 · IaC & Container Security
6 finding(s): 0 critical, 0 high, 0 medium, 6 low.
D32 · Data Compliance (PII/GDPR)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 56 file(s) — `src/main/scala/ru/org/linux/SpringSecurityConfiguration.scala`, `src/main/scala/ru/org/linux/adv/AdvCounterDao.scala`, `src/main/scala/ru/org/linux/auth/IpBlockDao.scala`, `src/main/scala/ru/org/linux/auth/LoginAttemptCache.scala`, `src/main/scala/ru/org/linux/auth/LoginController.scala`, … (+51 more) — so the PII/GDPR sweep did not cover them at all.
What to do
- Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
16 of 200 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/java/ru/org/linux/util/bbcode/tags/CodeTag.java. Counted over 200 of the 350 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 72 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
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×3) — src/main/webapp/WEB-INF/jsp/edit.jsp:143, src/main/webapp/WEB-INF/jsp/white2/head-main.jsp:26, src/main/webapp/WEB-INF/jsp/zomg_ponies/head-main.jsp:28
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×20) — src/main/webapp/WEB-INF/jsp/add.jsp:104, src/main/webapp/WEB-INF/jsp/add.jsp:108, src/main/webapp/WEB-INF/jsp/add.jsp:178, …
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×17) — src/main/webapp/WEB-INF/jsp/addphoto.jsp:52, src/main/webapp/WEB-INF/jsp/delete.jsp:54, src/main/webapp/WEB-INF/jsp/delete_comment.jsp:51, …
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. — src/main/webapp/WEB-INF/jsp/tango/head-main.jsp:35
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — src/main/webapp/WEB-INF/jsp/user-topics.jsp:61, src/main/webapp/WEB-INF/jsp/view-news-archive.jsp:76
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). (×9) — src/main/webapp/WEB-INF/jsp/black/head-main.jsp:27, src/main/webapp/WEB-INF/jsp/black/head.jsp:23, src/main/webapp/WEB-INF/jsp/edit-settings.jsp:55, …
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — src/main/webapp/WEB-INF/jsp/head.jsp:1
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — src/main/webapp/WEB-INF/jsp/head.jsp:1
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×15) — src/main/webapp/WEB-INF/jsp/add.jsp:185, src/main/webapp/WEB-INF/jsp/comment-message.jsp:34, src/main/webapp/WEB-INF/jsp/edit.jsp:184, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.markup-tabs__panel[data-panel="editor"] textarea:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/main/webapp/sass/_form.scss:284
- `#bd .nav li a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×3) — src/main/webapp/sass/zomg_ponies/_style.scss:651, src/main/webapp/sass/waltz/_style.scss:411, src/main/webapp/sass/tango/_style.scss:484
- `.spinner` moves (`animation: spinner 2s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/main/webapp/sass/_base.scss:861
- `.comment-form-inline` moves (`transition: max-height 0.3s ease, opacity 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/main/webapp/sass/_form.scss:194
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AC7 · A11y enforcement
- No accessibility enforcement found — no automated accessibility check runs over the HTML your app renders. Assert the accessibility invariants over that HTML in the test suite you already have (parse the output and assert, or drive a browser), and gate that test in CI so a regression blocks the merge. What was searched, so you can tell an absence from a miss: the 95 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
- Enforce accessibility in the test suite you already have: assert the accessibility invariants over the HTML your app renders — parse the rendered output in an existing test, or drive a real browser from one — and gate that test in CI so a regression blocks the merge.
AX1 · Captive dependencies
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX2 · Stateful singletons
- `SearchQueueListener` is one shared instance (@Component: every request runs on it, concurrently, on the server's thread pool) but writes its own state outside any lock (mappingsSet; e.g. `mappingsSet` in `createIndex` at line 73). Two requests that interleave lose an update, and a mutable collection written concurrently can corrupt. — src/main/scala/ru/org/linux/search/SearchQueueListener.scala:24
What to do
- Scala: keep controllers and singletons stateless — per-request data in locals, shared data in a store — or hold the state in a thread-safe type (TrieMap, AtomicInteger/AtomicReference, a cats-effect Ref) or update it under `synchronized { }`; a flag that is only ever overwritten can be a `@volatile var`.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
- 335 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Review the README against recent changes; refresh the parts that drifted.
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
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add scalafix or scapegoat (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 1707 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:3
What to do
- Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
What to do
- Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
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.
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 16 plain JS — the untyped files are src/main/webapp/js/add-form.js, src/main/webapp/js/lor/ads.js, src/main/webapp/js/lor/disabled-btn.js, src/main/webapp/js/lor/forms.js, src/main/webapp/js/lor/images.js, src/main/webapp/js/lor/memories.js (+10 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- src/main/webapp/js/lor/memories.js:133 · src/main/webapp/js/lor/memories.js:173 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/webapp/js/lor/memories.js:133
- src/main/webapp/js/tagsAutocomplete.js:32 · src/main/webapp/js/tagsAutocomplete.js:67 — the two spans are one implementation copied and then locally edited — 92 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/webapp/js/tagsAutocomplete.js:32
- src/main/webapp/js/lor/memories.js:16 · src/main/webapp/js/lor/memories.js:111 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/main/webapp/js/lor/memories.js:16
- src/main/webapp/js/add-form.js:426 · src/main/webapp/js/add-form.js:456 — the two spans are one implementation copied and then locally edited — 87 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/main/webapp/js/add-form.js:426
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- (anonymous) has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/main/webapp/js/lor/timezone.js:27
- moveAndShowForm has cyclomatic complexity 15 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/main/webapp/js/add-form.js:548
- initPreviewTabs has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/main/webapp/js/add-form.js:81
R3 · Large Files
- src/main/webapp/js/add-form.js has 631 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/main/webapp/js/add-form.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R7 · Dead Code
- Unreachable from the 1 application, 0 tooling and 0 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 0 tooling, 0 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×15) — src/main/webapp/js/add-form.js, src/main/webapp/js/lor/memories.js, src/main/webapp/js/lor_view_diff_history.js, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
- `Files.newDirectoryStream(…)` opens something that has to be given back — a file descriptor, a socket, a directory handle — and its only use reads `.asScala` through it and drops it, so this expression both creates the value and is the last place that can release it, and does not. Every call leaks one more open handle until the collector happens to reach it: `Too many open files` under load, and on Windows a file that cannot be replaced or deleted while it is held. Open it with `scala.util.Using.resource(Files.newDirectoryStream(…)) { r => … }`, which releases it on every path including a throw, or hold it and call `.close()` in a `finally`. — src/main/scala/ru/org/linux/gallery/ImageService.scala:209
What to do
- Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
X19 · Unrestored process-global state
X20 · Mistyped argument guard
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `data.html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — src/main/webapp/js/add-form.js:207
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X26 · Unsynchronised callback handoff
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — src/main/webapp/js/add-form.js:338
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/java/ru/org/linux/util/StringUtil.java:111
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `info` at line 55 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/ru/org/linux/search/SearchQueueSender.java:55
- `info` at line 61 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.info("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — src/main/java/ru/org/linux/search/SearchQueueSender.java:61
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- No build over this repository's 302 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
What to do
- On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 32% | Weak — gated by R1, R7, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40% | Weak — gated by P3, P5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 87% | Strong | Solid. |
| Accessibility | 43% | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'scalikejdbc' (src/main/scala/ru/org/linux/warning/WarningDao.scala:21) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'scalikejdbc' (src/main/scala/ru/org/linux/warning/WarningDao.scala:21) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'scalikejdbc' (src/main/scala/ru/org/linux/warning/WarningDao.scala:21) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
Not included — 50 check(s) not relevant to this codebase
- 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
- 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
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 1 — a container did not start, exited, or never became healthy) — app Built Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error setting rlimits for ready process: error setting rlimit type 8: operation not permitted: unknown; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- 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.
- D10 Test Quality — ~15193 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — no .scala test runner
- D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 72 dependency(ies) and leaving 0 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D14 License Compliance — Not scored — this repository's 72 declared JVM dependency coordinate(s) were read from its 1 Maven/Gradle manifest(s), but Maven Central could not be asked for the licence of 66 of them (HTTP 429 Too Many Requests from http://172.31.7.1:8790/maven/org/scala-lang/scala3-library_${scala.suffix}/3.9.0/scala3-library_${scala.suffix}-3.9.0.pom), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Java, JavaScript, Scala not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java, .scala source were not judged.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Maven build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 108 value object(s); 3 domain event(s); its domain events are published by services or handlers — no domain entity raises one
- 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
- M4 Documentation accuracy — Not applicable: the 2 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- 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 — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: src/main/scala/ru/org/linux/warning/WarningController.scala:44 (@Controller))
- P8 Schema migrations — Liquibase is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (`addSbtPlugin("org.scoverage" % "sbt-scoverage" % "<version>")` in `project/plugins.sbt`, then `sbt clean coverage test coverageReport`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — the JS/TS workspace (16 production file(s)) has no JavaScript/TypeScript test, but it is 5.49% of this repository's production source and the other 94.51% carries 15,193 line(s) of test code this pass cannot read — an incidental frontend's reachability is not the repository's test posture, so it is not scored as one
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- 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.
- X2 Cancellation propagation — no C# was loaded; this repository's Scala and Java were read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter; a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 48 finding(s)
- <label> that labels no control src/main/webapp/WEB-INF/jsp/add.jsp:104
- <label> that labels no control src/main/webapp/WEB-INF/jsp/add.jsp:108
- <label> that labels no control src/main/webapp/WEB-INF/jsp/add.jsp:178
- <label> that labels no control src/main/webapp/WEB-INF/jsp/deregister.jsp:45
- <label> that labels no control src/main/webapp/WEB-INF/jsp/deregister.jsp:48
- <label> that labels no control src/main/webapp/WEB-INF/jsp/edit.jsp:83
- <label> that labels no control src/main/webapp/WEB-INF/jsp/edit.jsp:87
- <label> that labels no control src/main/webapp/WEB-INF/jsp/edit.jsp:90
- <label> that labels no control src/main/webapp/WEB-INF/jsp/edit.jsp:164
- <label> that labels no control src/main/webapp/WEB-INF/jsp/group-new.jsp:267
- <label> that labels no control src/main/webapp/WEB-INF/jsp/group.jsp:236
- <label> that labels no control src/main/webapp/WEB-INF/jsp/groupmod.jsp:56
- <label> that labels no control src/main/webapp/WEB-INF/jsp/login-form.jsp:33
- <label> that labels no control src/main/webapp/WEB-INF/jsp/login-form.jsp:34
- <label> that labels no control src/main/webapp/WEB-INF/jsp/search.jsp:59
- <label> that labels no control src/main/webapp/WEB-INF/jsp/search.jsp:66
- <label> that labels no control src/main/webapp/WEB-INF/jsp/search.jsp:74
- <label> that labels no control src/main/webapp/WEB-INF/jsp/search.jsp:75
- <label> that labels no control src/main/webapp/WEB-INF/jsp/search.jsp:84
- <label> that labels no control src/main/webapp/WEB-INF/jsp/tags-delete.jsp:47
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/delete.jsp:54
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/delete_comment.jsp:51
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:46
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:58
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:222
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:230
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:301
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/search-reindex.jsp:26
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/user-topics.jsp:66
- <select> without a programmatic label src/main/webapp/WEB-INF/jsp/view-news-archive.jsp:81
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/addphoto.jsp:52
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:45
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:221
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/sameip.jsp:300
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/search.jsp:61
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/user-topics.jsp:61
- <input> without a programmatic label src/main/webapp/WEB-INF/jsp/view-news-archive.jsp:76
- <img> without a text alternative src/main/webapp/WEB-INF/jsp/edit.jsp:143
- <img> without a text alternative src/main/webapp/WEB-INF/jsp/white2/head-main.jsp:26
- <img> without a text alternative src/main/webapp/WEB-INF/jsp/zomg_ponies/head-main.jsp:28
- <textarea> without a programmatic label src/main/webapp/WEB-INF/jsp/edit-remark.jsp:35
- <textarea> without a programmatic label src/main/webapp/WEB-INF/jsp/groupmod.jsp:64
- REDACTED
- REDACTED
- Link with no accessible name src/main/webapp/WEB-INF/jsp/tango/head-main.jsp:35
- Document without a <title> src/main/webapp/WEB-INF/jsp/head.jsp:1
- REDACTED
- REDACTED
Serious — 172 finding(s)
- Anchor without href src/main/webapp/WEB-INF/jsp/add.jsp:185
- Anchor without href src/main/webapp/WEB-INF/jsp/comment-message.jsp:34
- Anchor without href src/main/webapp/WEB-INF/jsp/edit.jsp:184
- Anchor without href src/main/webapp/WEB-INF/jsp/group-new.jsp:120
- Anchor without href src/main/webapp/WEB-INF/jsp/index.jsp:113
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-page.jsp:159
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-page.jsp:202
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-page.jsp:251
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-page.jsp:289
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-page.jsp:330
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-topics-forum-new.jsp:54
- Anchor without href src/main/webapp/WEB-INF/jsp/tag-topics.jsp:53
- Anchor without href src/main/webapp/WEB-INF/jsp/view-all.jsp:69
- Anchor without href src/main/webapp/WEB-INF/jsp/view-news-archive.jsp:69
- Anchor without href src/main/webapp/WEB-INF/jsp/view-news.jsp:92
- Data table has no header cells src/main/webapp/WEB-INF/jsp/black/head-main.jsp:27
- Data table has no header cells src/main/webapp/WEB-INF/jsp/black/head.jsp:23
- Data table has no header cells src/main/webapp/WEB-INF/jsp/edit-settings.jsp:55
- Data table has no header cells src/main/webapp/WEB-INF/jsp/show-replies.jsp:107
- Data table has no header cells src/main/webapp/WEB-INF/jsp/tag-topics.jsp:112
- Data table has no header cells src/main/webapp/WEB-INF/jsp/user-reactions.jsp:70
- Data table has no header cells src/main/webapp/WEB-INF/jsp/user-topics.jsp:92
- Data table has no header cells src/main/webapp/WEB-INF/jsp/view-news.jsp:133
- Data table has no header cells src/main/webapp/WEB-INF/jsp/whois.jsp:666
- Low cohesion: UserDao (LCOM4 23) src/main/scala/ru/org/linux/user/UserDao.scala:97
- Low cohesion: SiteConfig (LCOM4 10) src/main/scala/ru/org/linux/spring/SiteConfig.scala:26
- Low cohesion: UserService (LCOM4 7) src/main/scala/ru/org/linux/user/UserService.scala:61
- Low cohesion: ImagesResourcesConfiguration (LCOM4 5) src/main/scala/ru/org/linux/ImagesResourcesConfiguration.scala:33
- Low cohesion: CommentDao (LCOM4 5) src/main/scala/ru/org/linux/comment/CommentDao.scala:35
- Low cohesion: ImageService (LCOM4 5) src/main/scala/ru/org/linux/gallery/ImageService.scala:39
- Low cohesion: TagService (LCOM4 5) src/main/scala/ru/org/linux/tag/TagService.scala:46
- Low cohesion: TopicListDao (LCOM4 5) src/main/scala/ru/org/linux/topic/TopicListDao.scala:140
- Low cohesion: RegisterController (LCOM4 4) src/main/scala/ru/org/linux/user/RegisterController.scala:43
- TodoComment src/main/scala/ru/org/linux/util/markdown/LorLinkExtension.scala:34
- TodoComment src/main/scala/ru/org/linux/markup/MessageTextService.scala:66
- TodoComment src/main/scala/ru/org/linux/markup/MessageTextService.scala:122
- TodoComment src/main/scala/ru/org/linux/edithistory/EditHistoryService.scala:374
- TodoComment src/main/java/ru/org/linux/util/bbcode/DefaultParserParameters.java:111
- TodoComment src/main/java/ru/org/linux/util/bbcode/DefaultParserParameters.java:115
- Focus outline removed in CSS without a :focus replacement src/main/webapp/sass/_form.scss:284
- Focus outline removed in CSS without a :focus replacement src/main/webapp/sass/zomg_ponies/_style.scss:651
- Focus outline removed in CSS without a :focus replacement src/main/webapp/sass/waltz/_style.scss:411
- Focus outline removed in CSS without a :focus replacement src/main/webapp/sass/tango/_style.scss:484
- Hotspot: src/main/scala/ru/org/linux/topic/EditTopicController.scala src/main/scala/ru/org/linux/topic/EditTopicController.scala:237
- Hotspot: src/main/scala/ru/org/linux/topic/AddTopicController.scala src/main/scala/ru/org/linux/topic/AddTopicController.scala:184
- Hotspot: src/main/scala/ru/org/linux/user/EditProfileController.scala src/main/scala/ru/org/linux/user/EditProfileController.scala:101
- Hotspot: src/main/scala/ru/org/linux/admin/DelIPController.scala src/main/scala/ru/org/linux/admin/DelIPController.scala:46
- TooManyMethods: UserDao src/main/scala/ru/org/linux/user/UserDao.scala:97
- TooManyMethods: UserService src/main/scala/ru/org/linux/user/UserService.scala:61
- TooManyMethods: TopicDao src/main/scala/ru/org/linux/topic/TopicDao.scala:45
- Animation without a prefers-reduced-motion guard src/main/webapp/sass/_base.scss:861
- Animation without a prefers-reduced-motion guard src/main/webapp/sass/_form.scss:194
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/main/scala/ru/org/linux/comment/AddCommentController.scala:94
- Duplicated block (9 lines × 2) src/main/scala/ru/org/linux/user/UserEventPrepareService.scala:82
- Duplicated block (7 lines × 2) src/main/scala/ru/org/linux/site/DateFormats.scala:62
- Duplicated block (7 lines × 2) src/main/scala/ru/org/linux/user/EditProfileRequestValidator.scala:47
- Dead file (~34 LoC) src/main/webapp/js/lor/disabled-btn.js
- Dead file (~34 LoC) src/main/webapp/js/lor/theme.js
- Page without a main landmark src/main/webapp/WEB-INF/jsp/head.jsp:1
- Accessibility enforcement below the top rung
- Stateful singleton: SearchQueueListener src/main/scala/ru/org/linux/search/SearchQueueListener.scala:24
- (anonymous) (cyclomatic 67) src/main/webapp/js/add-form.js:252
- EditTopicController.edit (cyclomatic 40) src/main/scala/ru/org/linux/topic/EditTopicController.scala:237
- jquery.hotkeys.keyHandler (cyclomatic 39) src/main/webapp/js/jquery.hotkeys.js:34
- initPreviewTabs (cyclomatic 33) src/main/webapp/js/add-form.js:81
- TopicController.getMessage (cyclomatic 26) src/main/scala/ru/org/linux/topic/TopicController.scala:161
- WhoisController.getInfoNew (cyclomatic 26) src/main/scala/ru/org/linux/user/WhoisController.scala:52
- (anonymous) (cyclomatic 25) src/main/webapp/js/lor/notifications.js:16
- TopicListDao.makeConditions (cyclomatic 24) src/main/scala/ru/org/linux/topic/TopicListDao.scala:31
- LorURL.findURLIds (cyclomatic 24) src/main/java/ru/org/linux/util/LorURL.java:51
- timezone.fixTimezone (cyclomatic 22) src/main/webapp/js/lor/timezone.js:16
- TopicPermissionService.checkView (cyclomatic 19) src/main/scala/ru/org/linux/topic/TopicPermissionService.scala:73
- AddTopicController.doAdd (cyclomatic 18) src/main/scala/ru/org/linux/topic/AddTopicController.scala:184
- RegisterRequestValidator.validate (cyclomatic 18) src/main/scala/ru/org/linux/user/RegisterRequestValidator.scala:53
- ToLorCodeTexFormatter.quote (cyclomatic 18) src/main/java/ru/org/linux/util/formatter/ToLorCodeTexFormatter.java:36
- DelIPController.delIp (cyclomatic 17) src/main/scala/ru/org/linux/admin/DelIPController.scala:46
- EditProfileController.edit (cyclomatic 17) src/main/scala/ru/org/linux/user/EditProfileController.scala:101
- Parser.pushTextNode (cyclomatic 17) src/main/java/ru/org/linux/util/bbcode/Parser.java:241
- DeleteCommentController.deleteComments (cyclomatic 16) src/main/scala/ru/org/linux/comment/DeleteCommentController.scala:83
- PostScoreChecker.postScoreCheckerChain (cyclomatic 16) src/main/scala/ru/org/linux/rights/PostScoreChecker.scala:13
- LorURL.findURLIds (cognitive 57) src/main/java/ru/org/linux/util/LorURL.java:51
- EditTopicController.edit (cognitive 54) src/main/scala/ru/org/linux/topic/EditTopicController.scala:237
- TopicPermissionService.checkView (cognitive 44) src/main/scala/ru/org/linux/topic/TopicPermissionService.scala:73
- ToLorCodeTexFormatter.quote (cognitive 38) src/main/java/ru/org/linux/util/formatter/ToLorCodeTexFormatter.java:36
- Parser.pushTextNode (cognitive 37) src/main/java/ru/org/linux/util/bbcode/Parser.java:241
- timezone.fixTimezone (cognitive 37) src/main/webapp/js/lor/timezone.js:16
- initPreviewTabs (cognitive 37) src/main/webapp/js/add-form.js:81
- TopicController.getMessage (cognitive 34) src/main/scala/ru/org/linux/topic/TopicController.scala:161
- (anonymous)::(anonymous)::moveAndShowForm (cognitive 34) src/main/webapp/js/add-form.js:548
- QuoteTag.renderNodeXhtml (cognitive 30) src/main/java/ru/org/linux/util/bbcode/tags/QuoteTag.java:87
- LoginController.loginProcess (cognitive 28) src/main/scala/ru/org/linux/auth/LoginController.scala:63
- LorLinkRenderer.renderLorUrl (cognitive 28) src/main/scala/ru/org/linux/util/markdown/LorLinkExtension.scala:70
- DeleteCommentController.deleteComments (cognitive 27) src/main/scala/ru/org/linux/comment/DeleteCommentController.scala:83
- EditProfileController.edit (cognitive 27) src/main/scala/ru/org/linux/user/EditProfileController.scala:101
- WhoisController.getInfoNew (cognitive 27) src/main/scala/ru/org/linux/user/WhoisController.scala:52
- UrlWithParamTag.renderNodeXhtml (cognitive 27) src/main/java/ru/org/linux/util/bbcode/tags/UrlWithParamTag.java:72
- TopicListDao.makeConditions (cognitive 26) src/main/scala/ru/org/linux/topic/TopicListDao.scala:31
- CommentPrepareService.prepareComment (cognitive 25) src/main/scala/ru/org/linux/comment/CommentPrepareService.scala:40
- TopicEditHistoryState.build (cognitive 24) src/main/scala/ru/org/linux/edithistory/EditHistoryService.scala:107
- ImageInfo.getJpgInfo (cognitive 23) src/main/java/ru/org/linux/util/image/ImageInfo.java:125
- (anonymous) (cognitive 22) src/main/webapp/js/lor/notifications.js:16
- SameIPController.sameIP (cognitive 20) src/main/scala/ru/org/linux/admin/SameIPController.scala:59
- AddTopicController.doAdd (cognitive 20) src/main/scala/ru/org/linux/topic/AddTopicController.scala:184
- TagTopicListController.tagFeed (cognitive 20) src/main/scala/ru/org/linux/topic/TagTopicListController.scala:73
- TopicPermissionService.checkCommentEditableNow (cognitive 19) src/main/scala/ru/org/linux/topic/TopicPermissionService.scala:178
- TopicPrepareService.prepareTopic (cognitive 19) src/main/scala/ru/org/linux/topic/TopicPrepareService.scala:80
- LostPasswordController.sendPassword (cognitive 19) src/main/scala/ru/org/linux/user/LostPasswordController.scala:47
- RegisterRequestValidator.validate (cognitive 19) src/main/scala/ru/org/linux/user/RegisterRequestValidator.scala:53
- WarningController.post (cognitive 19) src/main/scala/ru/org/linux/warning/WarningController.scala:96
- UserReactionsController.reactions (cognitive 18) src/main/scala/ru/org/linux/reaction/UserReactionsController.scala:29
- TagController.deleteTagSubmitHandler (cognitive 18) src/main/scala/ru/org/linux/tag/TagController.scala:212
- TagPageController.tagPage (cognitive 18) src/main/scala/ru/org/linux/tag/TagPageController.scala:60
- Parser.pushTagNode (cognitive 18) src/main/java/ru/org/linux/util/bbcode/Parser.java:336
- RuTypoChanger.format (cognitive 18) src/main/java/ru/org/linux/util/formatter/RuTypoChanger.java:137
- jquery.hotkeys.keyHandler (cognitive 18) src/main/webapp/js/jquery.hotkeys.js:34
- memories.tag_memories_form_setup (cognitive 18) src/main/webapp/js/lor/memories.js:111
- UserpicPermissionInterceptor.preHandle (cognitive 17) src/main/scala/ru/org/linux/auth/UserpicPermissionInterceptor.scala:26
- SearchController.search (cognitive 17) src/main/scala/ru/org/linux/search/SearchController.scala:58
- EditTopicController.checkModified (cognitive 16) src/main/scala/ru/org/linux/topic/EditTopicController.scala:200
- RegisterController.doRegister (cognitive 16) src/main/scala/ru/org/linux/user/RegisterController.scala:76
- UserEventController.processClickNotifications (cognitive 16) src/main/scala/ru/org/linux/user/UserEventController.scala:83
- CutTag.renderNodeXhtml (cognitive 16) src/main/java/ru/org/linux/util/bbcode/tags/CutTag.java:73
- Parser.firstParagraphBreak (cognitive 16) src/main/java/ru/org/linux/util/bbcode/Parser.java:182
- REDACTED
- FunctionTooLong: add-form.initPreviewTabs src/main/webapp/js/add-form.js:81
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/scala/ru/org/linux/topic/UserTopicListController.scala:41
- Duplicated block (58 lines × 2) src/main/scala/ru/org/linux/topic/TopicDao.scala:145
- Duplicated block (50–55 lines × 2) src/main/scala/ru/org/linux/comment/CommentDao.scala:326
- Duplicated block (15–16 lines × 2) src/main/scala/ru/org/linux/reaction/ReactionDao.scala:66
- Duplicated block (14–15 lines × 2) src/main/scala/ru/org/linux/topic/UserTopicListController.scala:63
- Duplicated block (11 lines × 2) src/main/scala/ru/org/linux/user/EditProfileRequestValidator.scala:57
- Duplicated block (10 lines × 2) src/main/scala/ru/org/linux/comment/CommentDao.scala:363
- Duplicated block (7–8 lines × 2) src/main/scala/ru/org/linux/comment/AddCommentController.scala:126
- Duplicated block (8 lines × 2) src/main/scala/ru/org/linux/topic/TopicModificationController.scala:125
- Duplicated block (7 lines × 4) src/main/scala/ru/org/linux/topic/UserTopicListController.scala:44
- Duplicated block (5 lines × 2) src/main/scala/ru/org/linux/admin/DelIPController.scala:72
- Duplicated block (15 lines × 2) src/main/java/ru/org/linux/util/image/ImageUtil.java:51
- README may be stale
- No DR/backup evidence
- Type Safety
- Duplicated block (28 lines × 2 locations) src/main/webapp/js/lor/memories.js:133
- Duplicated block with local edits (26 matched lines × 2 locations) src/main/webapp/js/tagsAutocomplete.js:32
- Duplicated block (20 lines × 2 locations) src/main/webapp/js/lor/memories.js:16
- Duplicated block with local edits (17 matched lines × 2 locations) src/main/webapp/js/add-form.js:426
- Complex function (anonymous) (cyclomatic 19, cognitive 24) src/main/webapp/js/lor/timezone.js:27
- Complex function moveAndShowForm (cyclomatic 15, cognitive 34) src/main/webapp/js/add-form.js:548
- Complex function initPreviewTabs (cyclomatic 12, cognitive 11) src/main/webapp/js/add-form.js:81
- src/main/webapp/js/add-form.js: 631 lines of code src/main/webapp/js/add-form.js:1
- Dead file (~748 LoC) src/main/webapp/js/add-form.js
- Dead file (~216 LoC) src/main/webapp/js/lor/memories.js
- Dead file (~152 LoC) src/main/webapp/js/lor_view_diff_history.js
- Dead file (~118 LoC) src/main/webapp/js/realtime.js
- Dead file (~106 LoC) src/main/webapp/js/lor/reactions.js
- Dead file (~98 LoC) src/main/webapp/js/tagsAutocomplete.js
- Dead file (~80 LoC) src/main/webapp/js/lor/navigation.js
- Dead file (~76 LoC) src/main/webapp/js/lor/timezone.js
- Dead file (~69 LoC) src/main/webapp/js/lor/ads.js
- Dead file (~51 LoC) src/main/webapp/js/lor/forms.js
- Dead file (~38 LoC) src/main/webapp/js/lor/images.js
- Dead file (~35 LoC) src/main/webapp/js/lor/spoilers.js
- Dead file (~26 LoC) src/main/webapp/js/pattern.js
- Disposable created and abandoned in the function that made it src/main/scala/ru/org/linux/gallery/ImageService.scala:209
- Untrusted text written into markup unescaped src/main/webapp/js/add-form.js:207
- Swallowed exception (empty catch) src/main/webapp/js/add-form.js:338
- Swallowed exception (caught, then discarded) src/main/java/ru/org/linux/util/StringUtil.java:111
Minor — 40 finding(s)
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/CodeTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/formatter/RuTypoChanger.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/nodes/RootNode.java:1
- Orphaned file src/main/java/ru/org/linux/util/image/ImageUtil.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/Tag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/CutTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/MemberTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/HtmlEquivTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/nodes/TextNode.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/nodes/TagNode.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/ListTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/NodeUtils.java:1
- Orphaned file src/main/java/ru/org/linux/spring/AbstractRomeView.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/SoftBrTag.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/nodes/TextCodeNode.java:1
- Orphaned file src/main/java/ru/org/linux/util/bbcode/tags/LiTag.java:1
- Duplicated predicate src/main/java/ru/org/linux/util/bbcode/NodeUtils.java:72
- Duplicated predicate src/main/scala/ru/org/linux/user/EditProfileRequestValidator.scala:53
- Duplicated predicate src/main/scala/ru/org/linux/spring/MainPageController.scala:80
- Duplicated predicate src/main/scala/ru/org/linux/topic/TopicDao.scala:168
- Duplicated predicate src/main/scala/ru/org/linux/user/EditProfileRequestValidator.scala:47
- Duplicated predicate src/main/scala/ru/org/linux/user/RegisterController.scala:260
- Duplicated predicate src/main/scala/ru/org/linux/auth/AuthUtil.scala:251
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Interpolated log message defeats structured logging src/main/java/ru/org/linux/search/SearchQueueSender.java:55
- Interpolated log message defeats structured logging src/main/java/ru/org/linux/search/SearchQueueSender.java:61
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No SAST REDACTED:3
- No changelog
- Scala's null is not held to the type system everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2877425956c447cca2359d70c5b342d7/history.json --exit-code 0 --source . | 10 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2877425956c447cca2359d70c5b342d7/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 . | 8 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 6 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep --config /opt/semgrep-rules/gdpr.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 . | 2 | artifacts/raw/semgrep-gdpr.json |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |