Executive summary
pig-mesh/pig is rated At risk because critical security findings are open, most of them leaked passwords or keys. Its score is held back because it has pages that don't say their language. It scores 52.0 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 43.7, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 6.2 points. Structuring the pages comes next, worth about 3.6 points. Raising Accessibility to 70 would lift the score to about 58.4.
Eighty-nine passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Seventeen settings leave the servers or containers unsafe, and five known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the three security weaknesses in the code. The 14 pages that don't say their language need their language set.
The product code is 41,240 lines, about €41,000 to rebuild.
If Accessibility rose from 43.7 to 70, the lowest score rated Strong, the score would rise from 52.0 to about 58.4.
Rebuild cost: about €41,000 · Estimate
| Cost to rebuild | €13,000 to €68,000, for 225 to 713 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 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 41,240 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 admin.api.entity | 2 codegen.entity | 3 common.core.util | 4 common.excel.head | 5 daemon.quartz.entity | 6 monitor.service.impl | 7 admin.api.vo | 8 codegen.util.vo | 9 common.excel.enhance | 10 common.file.oss | 11 daemon.quartz.service | 12 daemon.quartz.support | 13 admin.api.dto | 14 codegen.service | 15 common.excel.handler | 16 common.file.core | 17 daemon.quartz.util | 18 admin.api.feign | 19 admin.mapper | 20 admin.service | 21 codegen.controller | 22 common.excel.annotation | 23 daemon.quartz.config | 24 daemon.quartz.controller | 25 daemon.quartz.event | 26 daemon.quartz.service.impl | 27 admin.controller | 28 admin.handler | 29 auth.support.core | 30 auth.support.handler | 31 codegen.service.impl | 32 common.excel.aop | 33 common.log.event | 34 common.security.service | 35 admin.service.impl | 36 auth.endpoint | 37 auth.support.filter | 38 common.excel | 39 common.log | 40 auth.config |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 admin.api.entity | ||||||||||||||||||||||||||||||||||||||||
| 2 codegen.entity | ||||||||||||||||||||||||||||||||||||||||
| 3 common.core.util | ||||||||||||||||||||||||||||||||||||||||
| 4 common.excel.head | ||||||||||||||||||||||||||||||||||||||||
| 5 daemon.quartz.entity | ||||||||||||||||||||||||||||||||||||||||
| 6 monitor.service.impl | ||||||||||||||||||||||||||||||||||||||||
| 7 admin.api.vo | 5 | |||||||||||||||||||||||||||||||||||||||
| 8 codegen.util.vo | 2 | |||||||||||||||||||||||||||||||||||||||
| 9 common.excel.enhance | 2 | 2 | ||||||||||||||||||||||||||||||||||||||
| 10 common.file.oss | 2 | |||||||||||||||||||||||||||||||||||||||
| 11 daemon.quartz.service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 daemon.quartz.support | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 admin.api.dto | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 codegen.service | 3 | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 15 common.excel.handler | 4 | 3 | 5 | |||||||||||||||||||||||||||||||||||||
| 16 common.file.core | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 daemon.quartz.util | 8 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 18 admin.api.feign | 4 | 10 | 6 | |||||||||||||||||||||||||||||||||||||
| 19 admin.mapper | 4 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 admin.service | 17 | 16 | 11 | 17 | ||||||||||||||||||||||||||||||||||||
| 21 codegen.controller | 8 | 8 | 3 | 9 | ||||||||||||||||||||||||||||||||||||
| 22 common.excel.annotation | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 daemon.quartz.config | 3 | 1 | 3 | 1 | ||||||||||||||||||||||||||||||||||||
| 24 daemon.quartz.controller | 2 | 3 | 3 | 2 | ||||||||||||||||||||||||||||||||||||
| 25 daemon.quartz.event | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 daemon.quartz.service.impl | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 27 admin.controller | 22 | 21 | 7 | 15 | 1 | 23 | ||||||||||||||||||||||||||||||||||
| 28 admin.handler | 8 | 7 | 6 | 5 | ||||||||||||||||||||||||||||||||||||
| 29 auth.support.core | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 auth.support.handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 codegen.service.impl | 1 | 8 | 1 | 5 | 17 | 1 | ||||||||||||||||||||||||||||||||||
| 32 common.excel.aop | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 common.log.event | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 common.security.service | 1 | 3 | ||||||||||||||||||||||||||||||||||||||
| 35 admin.service.impl | 20 | 16 | 11 | 17 | 3 | 1 | 16 | 35 | 2 | |||||||||||||||||||||||||||||||
| 36 auth.endpoint | 2 | 1 | 2 | |||||||||||||||||||||||||||||||||||||
| 37 auth.support.filter | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 common.excel | 1 | 1 | 3 | 3 | ||||||||||||||||||||||||||||||||||||
| 39 common.log | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 40 auth.config | 2 | 3 |
7→1 admin.api.vo uses admin.api.entity✕
- Connections
- 5 pairs of types, where a type in admin.api.vo uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.api.vo.SysMessageReadVO→com.pig4cloud.pig.admin.api.entity.SysMessageRelationEntitycom.pig4cloud.pig.admin.api.vo.SysMessageVO→com.pig4cloud.pig.admin.api.entity.SysMessageEntitycom.pig4cloud.pig.admin.api.vo.UserVO→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.api.vo.UserVO→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.api.vo.UserVO→com.pig4cloud.pig.admin.api.entity.SysRole
- Direction
- admin.api.vo uses admin.api.entity, so a change to admin.api.entity can break admin.api.vo, while a change to admin.api.vo can't break admin.api.entity.
- Position
- Below the diagonal: admin.api.vo uses a module listed above it, which is the healthy direction.
8→2 codegen.util.vo uses codegen.entity✕
- Connections
- 2 pairs of types, where a type in codegen.util.vo uses a type in codegen.entity.
- The types involved
com.pig4cloud.pig.codegen.util.vo.GroupVO→com.pig4cloud.pig.codegen.entity.GenTemplateEntitycom.pig4cloud.pig.codegen.util.vo.TemplateGroupDTO→com.pig4cloud.pig.codegen.entity.GenGroupEntity
- Direction
- codegen.util.vo uses codegen.entity, so a change to codegen.entity can break codegen.util.vo, while a change to codegen.util.vo can't break codegen.entity.
- Position
- Below the diagonal: codegen.util.vo uses a module listed above it, which is the healthy direction.
9→4 common.excel.enhance uses common.excel.head✕
- Connections
- 2 pairs of types, where a type in common.excel.enhance uses a type in common.excel.head.
- The types involved
com.pig4cloud.pig.common.excel.enhance.DefaultWriterBuilderEnhancer→com.pig4cloud.pig.common.excel.head.HeadGeneratorcom.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancer→com.pig4cloud.pig.common.excel.head.HeadGenerator
- Direction
- common.excel.enhance uses common.excel.head, so a change to common.excel.head can break common.excel.enhance, while a change to common.excel.enhance can't break common.excel.head.
- Position
- Below the diagonal: common.excel.enhance uses a module listed above it, which is the healthy direction.
9→22 common.excel.enhance uses common.excel.annotation part of a loop✕
- Connections
- 2 pairs of types, where a type in common.excel.enhance uses a type in common.excel.annotation.
- The types involved
com.pig4cloud.pig.common.excel.enhance.DefaultWriterBuilderEnhancer→com.pig4cloud.pig.common.excel.annotation.ResponseExcelcom.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancer→com.pig4cloud.pig.common.excel.annotation.ResponseExcel
- Direction
- common.excel.enhance uses common.excel.annotation, so a change to common.excel.annotation can break common.excel.enhance, while a change to common.excel.enhance can't break common.excel.annotation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→16 common.file.oss uses common.file.core part of a loop✕
- Connections
- 2 pairs of types, where a type in common.file.oss uses a type in common.file.core.
- The types involved
com.pig4cloud.pig.common.file.oss.OssAutoConfiguration→com.pig4cloud.pig.common.file.core.FilePropertiescom.pig4cloud.pig.common.file.oss.OssAutoConfiguration→com.pig4cloud.pig.common.file.core.FileTemplate
- Direction
- common.file.oss uses common.file.core, so a change to common.file.core can break common.file.oss, while a change to common.file.oss can't break common.file.core.
- 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→3 daemon.quartz.service uses common.core.util✕
- Connections
- 1 pair of types, where a type in daemon.quartz.service uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.SysJobService→com.pig4cloud.pig.common.core.util.R
- Direction
- daemon.quartz.service uses common.core.util, so a change to common.core.util can break daemon.quartz.service, while a change to daemon.quartz.service can't break common.core.util.
- Position
- Below the diagonal: daemon.quartz.service uses a module listed above it, which is the healthy direction.
11→5 daemon.quartz.service uses daemon.quartz.entity✕
- Connections
- 1 pair of types, where a type in daemon.quartz.service uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.SysJobService→com.pig4cloud.pig.daemon.quartz.entity.SysJob
- Direction
- daemon.quartz.service uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.service, while a change to daemon.quartz.service can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.service uses a module listed above it, which is the healthy direction.
12→5 daemon.quartz.support uses daemon.quartz.entity✕
- Connections
- 1 pair of types, where a type in daemon.quartz.support uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.support.QuartzProtectionSupport→com.pig4cloud.pig.daemon.quartz.entity.SysJob
- Direction
- daemon.quartz.support uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.support, while a change to daemon.quartz.support can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.support uses a module listed above it, which is the healthy direction.
12→23 daemon.quartz.support uses daemon.quartz.config part of a loop✕
- Connections
- 1 pair of types, where a type in daemon.quartz.support uses a type in daemon.quartz.config.
- The types involved
com.pig4cloud.pig.daemon.quartz.support.QuartzProtectionSupport→com.pig4cloud.pig.daemon.quartz.config.QuartzProtectionProperties
- Direction
- daemon.quartz.support uses daemon.quartz.config, so a change to daemon.quartz.config can break daemon.quartz.support, while a change to daemon.quartz.support can't break daemon.quartz.config.
- 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→1 admin.api.dto uses admin.api.entity✕
- Connections
- 2 pairs of types, where a type in admin.api.dto uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.api.dto.SysOauthClientDetailsDTO→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.api.dto.UserDTO→com.pig4cloud.pig.admin.api.entity.SysUser
- Direction
- admin.api.dto uses admin.api.entity, so a change to admin.api.entity can break admin.api.dto, while a change to admin.api.dto can't break admin.api.entity.
- Position
- Below the diagonal: admin.api.dto uses a module listed above it, which is the healthy direction.
13→7 admin.api.dto uses admin.api.vo✕
- Connections
- 1 pair of types, where a type in admin.api.dto uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.admin.api.dto.UserInfo→com.pig4cloud.pig.admin.api.vo.UserVO
- Direction
- admin.api.dto uses admin.api.vo, so a change to admin.api.vo can break admin.api.dto, while a change to admin.api.dto can't break admin.api.vo.
- Position
- Below the diagonal: admin.api.dto uses a module listed above it, which is the healthy direction.
14→2 codegen.service uses codegen.entity✕
- Connections
- 3 pairs of types, where a type in codegen.service uses a type in codegen.entity.
- The types involved
com.pig4cloud.pig.codegen.service.GenDatasourceConfService→com.pig4cloud.pig.codegen.entity.GenDatasourceConfcom.pig4cloud.pig.codegen.service.GenTableColumnService→com.pig4cloud.pig.codegen.entity.GenTableColumnEntitycom.pig4cloud.pig.codegen.service.GenTableService→com.pig4cloud.pig.codegen.entity.GenTable
- Direction
- codegen.service uses codegen.entity, so a change to codegen.entity can break codegen.service, while a change to codegen.service can't break codegen.entity.
- Position
- Below the diagonal: codegen.service uses a module listed above it, which is the healthy direction.
14→3 codegen.service uses common.core.util✕
- Connections
- 1 pair of types, where a type in codegen.service uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.codegen.service.GenTemplateService→com.pig4cloud.pig.common.core.util.R
- Direction
- codegen.service uses common.core.util, so a change to common.core.util can break codegen.service, while a change to codegen.service can't break common.core.util.
- Position
- Below the diagonal: codegen.service uses a module listed above it, which is the healthy direction.
14→8 codegen.service uses codegen.util.vo✕
- Connections
- 3 pairs of types, where a type in codegen.service uses a type in codegen.util.vo.
- The types involved
com.pig4cloud.pig.codegen.service.GenCreateTableService→com.pig4cloud.pig.codegen.util.vo.GenCreateTableVOcom.pig4cloud.pig.codegen.service.GenGroupService→com.pig4cloud.pig.codegen.util.vo.GroupVOcom.pig4cloud.pig.codegen.service.GenGroupService→com.pig4cloud.pig.codegen.util.vo.TemplateGroupDTO
- Direction
- codegen.service uses codegen.util.vo, so a change to codegen.util.vo can break codegen.service, while a change to codegen.service can't break codegen.util.vo.
- Position
- Below the diagonal: codegen.service uses a module listed above it, which is the healthy direction.
15→4 common.excel.handler uses common.excel.head✕
- Connections
- 4 pairs of types, where a type in common.excel.handler uses a type in common.excel.head.
- The types involved
com.pig4cloud.pig.common.excel.handler.AbstractSheetWriteHandler→com.pig4cloud.pig.common.excel.head.HeadGeneratorcom.pig4cloud.pig.common.excel.handler.AbstractSheetWriteHandler→com.pig4cloud.pig.common.excel.head.I18nHeaderCellWriteHandlercom.pig4cloud.pig.common.excel.handler.ManySheetWriteHandler→com.pig4cloud.pig.common.excel.head.I18nHeaderCellWriteHandlercom.pig4cloud.pig.common.excel.handler.SingleSheetWriteHandler→com.pig4cloud.pig.common.excel.head.I18nHeaderCellWriteHandler
- Direction
- common.excel.handler uses common.excel.head, so a change to common.excel.head can break common.excel.handler, while a change to common.excel.handler can't break common.excel.head.
- Position
- Below the diagonal: common.excel.handler uses a module listed above it, which is the healthy direction.
15→9 common.excel.handler uses common.excel.enhance✕
- Connections
- 3 pairs of types, where a type in common.excel.handler uses a type in common.excel.enhance.
- The types involved
com.pig4cloud.pig.common.excel.handler.AbstractSheetWriteHandler→com.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancercom.pig4cloud.pig.common.excel.handler.ManySheetWriteHandler→com.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancercom.pig4cloud.pig.common.excel.handler.SingleSheetWriteHandler→com.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancer
- Direction
- common.excel.handler uses common.excel.enhance, so a change to common.excel.enhance can break common.excel.handler, while a change to common.excel.handler can't break common.excel.enhance.
- Position
- Below the diagonal: common.excel.handler uses a module listed above it, which is the healthy direction.
15→22 common.excel.handler uses common.excel.annotation part of a loop✕
- Connections
- 5 pairs of types, where a type in common.excel.handler uses a type in common.excel.annotation.
- The types involved
com.pig4cloud.pig.common.excel.handler.AbstractSheetWriteHandler→com.pig4cloud.pig.common.excel.annotation.ResponseExcelcom.pig4cloud.pig.common.excel.handler.AbstractSheetWriteHandler→com.pig4cloud.pig.common.excel.annotation.Sheetcom.pig4cloud.pig.common.excel.handler.ManySheetWriteHandler→com.pig4cloud.pig.common.excel.annotation.ResponseExcelcom.pig4cloud.pig.common.excel.handler.SheetWriteHandler→com.pig4cloud.pig.common.excel.annotation.ResponseExcelcom.pig4cloud.pig.common.excel.handler.SingleSheetWriteHandler→com.pig4cloud.pig.common.excel.annotation.ResponseExcel
- Direction
- common.excel.handler uses common.excel.annotation, so a change to common.excel.annotation can break common.excel.handler, while a change to common.excel.handler can't break common.excel.annotation.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→10 common.file.core uses common.file.oss✕
- Connections
- 1 pair of types, where a type in common.file.core uses a type in common.file.oss.
- The types involved
com.pig4cloud.pig.common.file.core.FileProperties→com.pig4cloud.pig.common.file.oss.OssProperties
- Direction
- common.file.core uses common.file.oss, so a change to common.file.oss can break common.file.core, while a change to common.file.core can't break common.file.oss.
- Position
- Below the diagonal: common.file.core uses a module listed above it, which is the healthy direction.
17→5 daemon.quartz.util uses daemon.quartz.entity✕
- Connections
- 8 pairs of types, where a type in daemon.quartz.util uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.util.ITaskInvok→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.JarTaskInvok→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.JavaClassTaskInvok→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.RestTaskInvok→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.SpringBeanTaskInvok→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.entity.SysJobLogcom.pig4cloud.pig.daemon.quartz.util.TaskUtil→com.pig4cloud.pig.daemon.quartz.entity.SysJob
- Direction
- daemon.quartz.util uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.util, while a change to daemon.quartz.util can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.util uses a module listed above it, which is the healthy direction.
17→11 daemon.quartz.util uses daemon.quartz.service✕
- Connections
- 1 pair of types, where a type in daemon.quartz.util uses a type in daemon.quartz.service.
- The types involved
com.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.service.SysJobService
- Direction
- daemon.quartz.util uses daemon.quartz.service, so a change to daemon.quartz.service can break daemon.quartz.util, while a change to daemon.quartz.util can't break daemon.quartz.service.
- Position
- Below the diagonal: daemon.quartz.util uses a module listed above it, which is the healthy direction.
17→12 daemon.quartz.util uses daemon.quartz.support✕
- Connections
- 3 pairs of types, where a type in daemon.quartz.util uses a type in daemon.quartz.support.
- The types involved
com.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.support.ProtectionLockcom.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.support.QuartzExecutionMetadatacom.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil→com.pig4cloud.pig.daemon.quartz.support.QuartzProtectionSupport
- Direction
- daemon.quartz.util uses daemon.quartz.support, so a change to daemon.quartz.support can break daemon.quartz.util, while a change to daemon.quartz.util can't break daemon.quartz.support.
- Position
- Below the diagonal: daemon.quartz.util uses a module listed above it, which is the healthy direction.
17→23 daemon.quartz.util uses daemon.quartz.config part of a loop✕
- Connections
- 1 pair of types, where a type in daemon.quartz.util uses a type in daemon.quartz.config.
- The types involved
com.pig4cloud.pig.daemon.quartz.util.RestTaskUrlValidator→com.pig4cloud.pig.daemon.quartz.config.QuartzProtectionProperties
- Direction
- daemon.quartz.util uses daemon.quartz.config, so a change to daemon.quartz.config can break daemon.quartz.util, while a change to daemon.quartz.util can't break daemon.quartz.config.
- 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→1 admin.api.feign uses admin.api.entity✕
- Connections
- 4 pairs of types, where a type in admin.api.feign uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.api.feign.RemoteApiKeyService→com.pig4cloud.pig.admin.api.entity.SysApiKeycom.pig4cloud.pig.admin.api.feign.RemoteClientDetailsService→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.api.feign.RemoteDictService→com.pig4cloud.pig.admin.api.entity.SysDictItemcom.pig4cloud.pig.admin.api.feign.RemoteMenuService→com.pig4cloud.pig.admin.api.entity.SysMenu
- Direction
- admin.api.feign uses admin.api.entity, so a change to admin.api.entity can break admin.api.feign, while a change to admin.api.feign can't break admin.api.entity.
- Position
- Below the diagonal: admin.api.feign uses a module listed above it, which is the healthy direction.
18→3 admin.api.feign uses common.core.util✕
- Connections
- 10 pairs of types, where a type in admin.api.feign uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.admin.api.feign.RemoteApiKeyService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteClientDetailsService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteDictService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteFileService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteLogService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteMenuService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteMessageService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteParamService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteTokenService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.api.feign.RemoteUserService→com.pig4cloud.pig.common.core.util.R
- Direction
- admin.api.feign uses common.core.util, so a change to common.core.util can break admin.api.feign, while a change to admin.api.feign can't break common.core.util.
- Position
- Below the diagonal: admin.api.feign uses a module listed above it, which is the healthy direction.
18→13 admin.api.feign uses admin.api.dto✕
- Connections
- 6 pairs of types, where a type in admin.api.feign uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.api.feign.RemoteLogService→com.pig4cloud.pig.admin.api.dto.SysLogDTOcom.pig4cloud.pig.admin.api.feign.RemoteMessageService→com.pig4cloud.pig.admin.api.dto.MessageEmailDTOcom.pig4cloud.pig.admin.api.feign.RemoteMessageService→com.pig4cloud.pig.admin.api.dto.MessageHookDTOcom.pig4cloud.pig.admin.api.feign.RemoteMessageService→com.pig4cloud.pig.admin.api.dto.MessageNoticeDTOcom.pig4cloud.pig.admin.api.feign.RemoteMessageService→com.pig4cloud.pig.admin.api.dto.MessageSmsDTOcom.pig4cloud.pig.admin.api.feign.RemoteUserService→com.pig4cloud.pig.admin.api.dto.UserInfo
- Direction
- admin.api.feign uses admin.api.dto, so a change to admin.api.dto can break admin.api.feign, while a change to admin.api.feign can't break admin.api.dto.
- Position
- Below the diagonal: admin.api.feign uses a module listed above it, which is the healthy direction.
19→1 admin.mapper uses admin.api.entity✕
- Connections
- 4 pairs of types, where a type in admin.mapper uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.mapper.SysDeptMapper→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.mapper.SysMenuMapper→com.pig4cloud.pig.admin.api.entity.SysMenucom.pig4cloud.pig.admin.mapper.SysPostMapper→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.mapper.SysRoleMapper→com.pig4cloud.pig.admin.api.entity.SysRole
- Direction
- admin.mapper uses admin.api.entity, so a change to admin.api.entity can break admin.mapper, while a change to admin.mapper can't break admin.api.entity.
- Position
- Below the diagonal: admin.mapper uses a module listed above it, which is the healthy direction.
19→7 admin.mapper uses admin.api.vo✕
- Connections
- 2 pairs of types, where a type in admin.mapper uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.admin.mapper.SysAreaMapper→com.pig4cloud.pig.admin.api.vo.SysAreaChildCountVOcom.pig4cloud.pig.admin.mapper.SysUserMapper→com.pig4cloud.pig.admin.api.vo.UserVO
- Direction
- admin.mapper uses admin.api.vo, so a change to admin.api.vo can break admin.mapper, while a change to admin.mapper can't break admin.api.vo.
- Position
- Below the diagonal: admin.mapper uses a module listed above it, which is the healthy direction.
19→13 admin.mapper uses admin.api.dto✕
- Connections
- 1 pair of types, where a type in admin.mapper uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.mapper.SysUserMapper→com.pig4cloud.pig.admin.api.dto.UserDTO
- Direction
- admin.mapper uses admin.api.dto, so a change to admin.api.dto can break admin.mapper, while a change to admin.mapper can't break admin.api.dto.
- Position
- Below the diagonal: admin.mapper uses a module listed above it, which is the healthy direction.
20→1 admin.service uses admin.api.entity✕
- Connections
- 17 pairs of types, where a type in admin.service uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.service.SysApiKeyService→com.pig4cloud.pig.admin.api.entity.SysApiKeycom.pig4cloud.pig.admin.service.SysAreaService→com.pig4cloud.pig.admin.api.entity.SysAreaEntitycom.pig4cloud.pig.admin.service.SysDeptService→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.service.SysDictItemService→com.pig4cloud.pig.admin.api.entity.SysDictItemcom.pig4cloud.pig.admin.service.SysDictService→com.pig4cloud.pig.admin.api.entity.SysDictcom.pig4cloud.pig.admin.service.SysFileService→com.pig4cloud.pig.admin.api.entity.SysFileGroupcom.pig4cloud.pig.admin.service.SysMenuService→com.pig4cloud.pig.admin.api.entity.SysMenucom.pig4cloud.pig.admin.service.SysOauthClientDetailsService→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.service.SysPostService→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.service.SysPublicParamService→com.pig4cloud.pig.admin.api.entity.SysPublicParamcom.pig4cloud.pig.admin.service.SysRoleService→com.pig4cloud.pig.admin.api.entity.SysRolecom.pig4cloud.pig.admin.service.SysRoleWidgetService→com.pig4cloud.pig.admin.api.entity.SysRoleWidgetcom.pig4cloud.pig.admin.service.SysScheduleService→com.pig4cloud.pig.admin.api.entity.SysScheduleEntitycom.pig4cloud.pig.admin.service.SysSensitiveWordService→com.pig4cloud.pig.admin.api.entity.SysSensitiveWordEntitycom.pig4cloud.pig.admin.service.SysSystemConfigService→com.pig4cloud.pig.admin.api.entity.SysSystemConfigEntitycom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.entity.SysUser
- Direction
- admin.service uses admin.api.entity, so a change to admin.api.entity can break admin.service, while a change to admin.service can't break admin.api.entity.
- Position
- Below the diagonal: admin.service uses a module listed above it, which is the healthy direction.
20→3 admin.service uses common.core.util✕
- Connections
- 16 pairs of types, where a type in admin.service uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.admin.service.SysApiKeyService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysAreaService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysDeptService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysDictItemService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysDictService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysFileService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysI18nService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysMenuService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysOauthClientDetailsService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysPostService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysPublicParamService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysRoleService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysSystemConfigService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysSystemInfoService→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.common.core.util.R
- Direction
- admin.service uses common.core.util, so a change to common.core.util can break admin.service, while a change to admin.service can't break common.core.util.
- Position
- Below the diagonal: admin.service uses a module listed above it, which is the healthy direction.
20→7 admin.service uses admin.api.vo✕
- Connections
- 11 pairs of types, where a type in admin.service uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.admin.service.SysAreaService→com.pig4cloud.pig.admin.api.vo.SysAreaManageVOcom.pig4cloud.pig.admin.service.SysDeptService→com.pig4cloud.pig.admin.api.vo.DeptExcelVOcom.pig4cloud.pig.admin.service.SysDeptService→com.pig4cloud.pig.admin.api.vo.OrgTreeVOcom.pig4cloud.pig.admin.service.SysLogService→com.pig4cloud.pig.admin.api.vo.PreLogVOcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.admin.api.vo.SysMessageVOcom.pig4cloud.pig.admin.service.SysPostService→com.pig4cloud.pig.admin.api.vo.PostExcelVOcom.pig4cloud.pig.admin.service.SysRoleService→com.pig4cloud.pig.admin.api.vo.RoleExcelVOcom.pig4cloud.pig.admin.service.SysRoleService→com.pig4cloud.pig.admin.api.vo.RoleMenuVOcom.pig4cloud.pig.admin.service.SysSocialDetailsService→com.pig4cloud.pig.admin.api.vo.SysSocialDetailsVOcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.vo.UserExcelVOcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.vo.UserVO
- Direction
- admin.service uses admin.api.vo, so a change to admin.api.vo can break admin.service, while a change to admin.service can't break admin.api.vo.
- Position
- Below the diagonal: admin.service uses a module listed above it, which is the healthy direction.
20→13 admin.service uses admin.api.dto✕
- Connections
- 17 pairs of types, where a type in admin.service uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.service.SysApiKeyService→com.pig4cloud.pig.admin.api.dto.ApiKeyCreateDTOcom.pig4cloud.pig.admin.service.SysAreaService→com.pig4cloud.pig.admin.api.dto.SysAreaSortDTOcom.pig4cloud.pig.admin.service.SysAreaService→com.pig4cloud.pig.admin.api.dto.SysAreaUpdateDTOcom.pig4cloud.pig.admin.service.SysDictItemService→com.pig4cloud.pig.admin.api.dto.SysDictItemSortDTOcom.pig4cloud.pig.admin.service.SysFileService→com.pig4cloud.pig.admin.api.dto.SysFileGroupDTOcom.pig4cloud.pig.admin.service.SysLogService→com.pig4cloud.pig.admin.api.dto.SysLogDTOcom.pig4cloud.pig.admin.service.SysMenuService→com.pig4cloud.pig.admin.api.dto.SysMenuSortDTOcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.admin.api.dto.MessageEmailDTOcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.admin.api.dto.MessageHookDTOcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.admin.api.dto.MessageNoticeDTOcom.pig4cloud.pig.admin.service.SysMessageService→com.pig4cloud.pig.admin.api.dto.MessageSmsDTOcom.pig4cloud.pig.admin.service.SysOauthClientDetailsService→com.pig4cloud.pig.admin.api.dto.SysOauthClientDetailsDTOcom.pig4cloud.pig.admin.service.SysSiteConfigService→com.pig4cloud.pig.admin.api.dto.SiteConfigDTOcom.pig4cloud.pig.admin.service.SysSocialDetailsService→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.dto.RegisterUserDTOcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.dto.UserDTOcom.pig4cloud.pig.admin.service.SysUserService→com.pig4cloud.pig.admin.api.dto.UserInfo
- Direction
- admin.service uses admin.api.dto, so a change to admin.api.dto can break admin.service, while a change to admin.service can't break admin.api.dto.
- Position
- Below the diagonal: admin.service uses a module listed above it, which is the healthy direction.
21→2 codegen.controller uses codegen.entity✕
- Connections
- 8 pairs of types, where a type in codegen.controller uses a type in codegen.entity.
- The types involved
com.pig4cloud.pig.codegen.controller.GenCreateTableController→com.pig4cloud.pig.codegen.entity.GenCreateTablecom.pig4cloud.pig.codegen.controller.GenDsConfController→com.pig4cloud.pig.codegen.entity.GenDatasourceConfcom.pig4cloud.pig.codegen.controller.GenFieldTypeController→com.pig4cloud.pig.codegen.entity.GenFieldTypecom.pig4cloud.pig.codegen.controller.GenGroupController→com.pig4cloud.pig.codegen.entity.GenGroupEntitycom.pig4cloud.pig.codegen.controller.GenTableController→com.pig4cloud.pig.codegen.entity.GenTablecom.pig4cloud.pig.codegen.controller.GenTableController→com.pig4cloud.pig.codegen.entity.GenTableColumnEntitycom.pig4cloud.pig.codegen.controller.GenTemplateController→com.pig4cloud.pig.codegen.entity.GenTemplateEntitycom.pig4cloud.pig.codegen.controller.GenTemplateGroupController→com.pig4cloud.pig.codegen.entity.GenTemplateGroupEntity
- Direction
- codegen.controller uses codegen.entity, so a change to codegen.entity can break codegen.controller, while a change to codegen.controller can't break codegen.entity.
- Position
- Below the diagonal: codegen.controller uses a module listed above it, which is the healthy direction.
21→3 codegen.controller uses common.core.util✕
- Connections
- 8 pairs of types, where a type in codegen.controller uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.codegen.controller.GenCreateTableController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenDsConfController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenFieldTypeController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenGroupController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenTableController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenTemplateController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GenTemplateGroupController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.codegen.controller.GeneratorController→com.pig4cloud.pig.common.core.util.R
- Direction
- codegen.controller uses common.core.util, so a change to common.core.util can break codegen.controller, while a change to codegen.controller can't break common.core.util.
- Position
- Below the diagonal: codegen.controller uses a module listed above it, which is the healthy direction.
21→8 codegen.controller uses codegen.util.vo✕
- Connections
- 3 pairs of types, where a type in codegen.controller uses a type in codegen.util.vo.
- The types involved
com.pig4cloud.pig.codegen.controller.GenCreateTableController→com.pig4cloud.pig.codegen.util.vo.GenCreateTableVOcom.pig4cloud.pig.codegen.controller.GenGroupController→com.pig4cloud.pig.codegen.util.vo.GroupVOcom.pig4cloud.pig.codegen.controller.GenGroupController→com.pig4cloud.pig.codegen.util.vo.TemplateGroupDTO
- Direction
- codegen.controller uses codegen.util.vo, so a change to codegen.util.vo can break codegen.controller, while a change to codegen.controller can't break codegen.util.vo.
- Position
- Below the diagonal: codegen.controller uses a module listed above it, which is the healthy direction.
21→14 codegen.controller uses codegen.service✕
- Connections
- 9 pairs of types, where a type in codegen.controller uses a type in codegen.service.
- The types involved
com.pig4cloud.pig.codegen.controller.GenCreateTableController→com.pig4cloud.pig.codegen.service.GenCreateTableServicecom.pig4cloud.pig.codegen.controller.GenDsConfController→com.pig4cloud.pig.codegen.service.GenDatasourceConfServicecom.pig4cloud.pig.codegen.controller.GenFieldTypeController→com.pig4cloud.pig.codegen.service.GenFieldTypeServicecom.pig4cloud.pig.codegen.controller.GenGroupController→com.pig4cloud.pig.codegen.service.GenGroupServicecom.pig4cloud.pig.codegen.controller.GenTableController→com.pig4cloud.pig.codegen.service.GenTableColumnServicecom.pig4cloud.pig.codegen.controller.GenTableController→com.pig4cloud.pig.codegen.service.GenTableServicecom.pig4cloud.pig.codegen.controller.GenTemplateController→com.pig4cloud.pig.codegen.service.GenTemplateServicecom.pig4cloud.pig.codegen.controller.GenTemplateGroupController→com.pig4cloud.pig.codegen.service.GenTemplateGroupServicecom.pig4cloud.pig.codegen.controller.GeneratorController→com.pig4cloud.pig.codegen.service.GeneratorService
- Direction
- codegen.controller uses codegen.service, so a change to codegen.service can break codegen.controller, while a change to codegen.controller can't break codegen.service.
- Position
- Below the diagonal: codegen.controller uses a module listed above it, which is the healthy direction.
22→4 common.excel.annotation uses common.excel.head✕
- Connections
- 2 pairs of types, where a type in common.excel.annotation uses a type in common.excel.head.
- The types involved
com.pig4cloud.pig.common.excel.annotation.ResponseExcel→com.pig4cloud.pig.common.excel.head.HeadGeneratorcom.pig4cloud.pig.common.excel.annotation.Sheet→com.pig4cloud.pig.common.excel.head.HeadGenerator
- Direction
- common.excel.annotation uses common.excel.head, so a change to common.excel.head can break common.excel.annotation, while a change to common.excel.annotation can't break common.excel.head.
- Position
- Below the diagonal: common.excel.annotation uses a module listed above it, which is the healthy direction.
22→15 common.excel.annotation uses common.excel.handler✕
- Connections
- 1 pair of types, where a type in common.excel.annotation uses a type in common.excel.handler.
- The types involved
com.pig4cloud.pig.common.excel.annotation.RequestExcel→com.pig4cloud.pig.common.excel.handler.ListAnalysisEventListener
- Direction
- common.excel.annotation uses common.excel.handler, so a change to common.excel.handler can break common.excel.annotation, while a change to common.excel.annotation can't break common.excel.handler.
- Position
- Below the diagonal: common.excel.annotation uses a module listed above it, which is the healthy direction.
23→5 daemon.quartz.config uses daemon.quartz.entity✕
- Connections
- 3 pairs of types, where a type in daemon.quartz.config uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.config.PigQuartzFactory→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.config.PigQuartzFactory→com.pig4cloud.pig.daemon.quartz.entity.SysJobLogcom.pig4cloud.pig.daemon.quartz.config.PigQuartzInvokeFactory→com.pig4cloud.pig.daemon.quartz.entity.SysJob
- Direction
- daemon.quartz.config uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.config, while a change to daemon.quartz.config can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.config uses a module listed above it, which is the healthy direction.
23→11 daemon.quartz.config uses daemon.quartz.service✕
- Connections
- 1 pair of types, where a type in daemon.quartz.config uses a type in daemon.quartz.service.
- The types involved
com.pig4cloud.pig.daemon.quartz.config.PigInitQuartzJob→com.pig4cloud.pig.daemon.quartz.service.SysJobService
- Direction
- daemon.quartz.config uses daemon.quartz.service, so a change to daemon.quartz.service can break daemon.quartz.config, while a change to daemon.quartz.config can't break daemon.quartz.service.
- Position
- Below the diagonal: daemon.quartz.config uses a module listed above it, which is the healthy direction.
23→12 daemon.quartz.config uses daemon.quartz.support✕
- Connections
- 3 pairs of types, where a type in daemon.quartz.config uses a type in daemon.quartz.support.
- The types involved
com.pig4cloud.pig.daemon.quartz.config.PigQuartzFactory→com.pig4cloud.pig.daemon.quartz.support.QuartzExecutionMetadatacom.pig4cloud.pig.daemon.quartz.config.PigQuartzFactory→com.pig4cloud.pig.daemon.quartz.support.QuartzProtectionSupportcom.pig4cloud.pig.daemon.quartz.config.PigQuartzInvokeFactory→com.pig4cloud.pig.daemon.quartz.support.QuartzExecutionMetadata
- Direction
- daemon.quartz.config uses daemon.quartz.support, so a change to daemon.quartz.support can break daemon.quartz.config, while a change to daemon.quartz.config can't break daemon.quartz.support.
- Position
- Below the diagonal: daemon.quartz.config uses a module listed above it, which is the healthy direction.
23→17 daemon.quartz.config uses daemon.quartz.util✕
- Connections
- 1 pair of types, where a type in daemon.quartz.config uses a type in daemon.quartz.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.config.PigInitQuartzJob→com.pig4cloud.pig.daemon.quartz.util.TaskUtil
- Direction
- daemon.quartz.config uses daemon.quartz.util, so a change to daemon.quartz.util can break daemon.quartz.config, while a change to daemon.quartz.config can't break daemon.quartz.util.
- Position
- Below the diagonal: daemon.quartz.config uses a module listed above it, which is the healthy direction.
24→3 daemon.quartz.controller uses common.core.util✕
- Connections
- 2 pairs of types, where a type in daemon.quartz.controller uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.daemon.quartz.controller.SysJobLogController→com.pig4cloud.pig.common.core.util.R
- Direction
- daemon.quartz.controller uses common.core.util, so a change to common.core.util can break daemon.quartz.controller, while a change to daemon.quartz.controller can't break common.core.util.
- Position
- Below the diagonal: daemon.quartz.controller uses a module listed above it, which is the healthy direction.
24→5 daemon.quartz.controller uses daemon.quartz.entity✕
- Connections
- 3 pairs of types, where a type in daemon.quartz.controller uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.entity.SysJobLogcom.pig4cloud.pig.daemon.quartz.controller.SysJobLogController→com.pig4cloud.pig.daemon.quartz.entity.SysJobLog
- Direction
- daemon.quartz.controller uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.controller, while a change to daemon.quartz.controller can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.controller uses a module listed above it, which is the healthy direction.
24→11 daemon.quartz.controller uses daemon.quartz.service✕
- Connections
- 3 pairs of types, where a type in daemon.quartz.controller uses a type in daemon.quartz.service.
- The types involved
com.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.service.SysJobLogServicecom.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.service.SysJobServicecom.pig4cloud.pig.daemon.quartz.controller.SysJobLogController→com.pig4cloud.pig.daemon.quartz.service.SysJobLogService
- Direction
- daemon.quartz.controller uses daemon.quartz.service, so a change to daemon.quartz.service can break daemon.quartz.controller, while a change to daemon.quartz.controller can't break daemon.quartz.service.
- Position
- Below the diagonal: daemon.quartz.controller uses a module listed above it, which is the healthy direction.
24→17 daemon.quartz.controller uses daemon.quartz.util✕
- Connections
- 2 pairs of types, where a type in daemon.quartz.controller uses a type in daemon.quartz.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.util.RestTaskUrlValidatorcom.pig4cloud.pig.daemon.quartz.controller.SysJobController→com.pig4cloud.pig.daemon.quartz.util.TaskUtil
- Direction
- daemon.quartz.controller uses daemon.quartz.util, so a change to daemon.quartz.util can break daemon.quartz.controller, while a change to daemon.quartz.controller can't break daemon.quartz.util.
- Position
- Below the diagonal: daemon.quartz.controller uses a module listed above it, which is the healthy direction.
25→5 daemon.quartz.event uses daemon.quartz.entity✕
- Connections
- 2 pairs of types, where a type in daemon.quartz.event uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.event.SysJobEvent→com.pig4cloud.pig.daemon.quartz.entity.SysJobcom.pig4cloud.pig.daemon.quartz.event.SysJobLogEvent→com.pig4cloud.pig.daemon.quartz.entity.SysJobLog
- Direction
- daemon.quartz.event uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.event, while a change to daemon.quartz.event can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.event uses a module listed above it, which is the healthy direction.
25→11 daemon.quartz.event uses daemon.quartz.service✕
- Connections
- 1 pair of types, where a type in daemon.quartz.event uses a type in daemon.quartz.service.
- The types involved
com.pig4cloud.pig.daemon.quartz.event.SysJobLogListener→com.pig4cloud.pig.daemon.quartz.service.SysJobLogService
- Direction
- daemon.quartz.event uses daemon.quartz.service, so a change to daemon.quartz.service can break daemon.quartz.event, while a change to daemon.quartz.event can't break daemon.quartz.service.
- Position
- Below the diagonal: daemon.quartz.event uses a module listed above it, which is the healthy direction.
25→12 daemon.quartz.event uses daemon.quartz.support✕
- Connections
- 1 pair of types, where a type in daemon.quartz.event uses a type in daemon.quartz.support.
- The types involved
com.pig4cloud.pig.daemon.quartz.event.SysJobEvent→com.pig4cloud.pig.daemon.quartz.support.QuartzExecutionMetadata
- Direction
- daemon.quartz.event uses daemon.quartz.support, so a change to daemon.quartz.support can break daemon.quartz.event, while a change to daemon.quartz.event can't break daemon.quartz.support.
- Position
- Below the diagonal: daemon.quartz.event uses a module listed above it, which is the healthy direction.
25→17 daemon.quartz.event uses daemon.quartz.util✕
- Connections
- 1 pair of types, where a type in daemon.quartz.event uses a type in daemon.quartz.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.event.SysJobListener→com.pig4cloud.pig.daemon.quartz.util.TaskInvokUtil
- Direction
- daemon.quartz.event uses daemon.quartz.util, so a change to daemon.quartz.util can break daemon.quartz.event, while a change to daemon.quartz.event can't break daemon.quartz.util.
- Position
- Below the diagonal: daemon.quartz.event uses a module listed above it, which is the healthy direction.
26→3 daemon.quartz.service.impl uses common.core.util✕
- Connections
- 1 pair of types, where a type in daemon.quartz.service.impl uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.impl.SysJobServiceImpl→com.pig4cloud.pig.common.core.util.R
- Direction
- daemon.quartz.service.impl uses common.core.util, so a change to common.core.util can break daemon.quartz.service.impl, while a change to daemon.quartz.service.impl can't break common.core.util.
- Position
- Below the diagonal: daemon.quartz.service.impl uses a module listed above it, which is the healthy direction.
26→5 daemon.quartz.service.impl uses daemon.quartz.entity✕
- Connections
- 1 pair of types, where a type in daemon.quartz.service.impl uses a type in daemon.quartz.entity.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.impl.SysJobServiceImpl→com.pig4cloud.pig.daemon.quartz.entity.SysJob
- Direction
- daemon.quartz.service.impl uses daemon.quartz.entity, so a change to daemon.quartz.entity can break daemon.quartz.service.impl, while a change to daemon.quartz.service.impl can't break daemon.quartz.entity.
- Position
- Below the diagonal: daemon.quartz.service.impl uses a module listed above it, which is the healthy direction.
26→11 daemon.quartz.service.impl uses daemon.quartz.service✕
- Connections
- 2 pairs of types, where a type in daemon.quartz.service.impl uses a type in daemon.quartz.service.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.impl.SysJobLogServiceImpl→com.pig4cloud.pig.daemon.quartz.service.SysJobLogServicecom.pig4cloud.pig.daemon.quartz.service.impl.SysJobServiceImpl→com.pig4cloud.pig.daemon.quartz.service.SysJobService
- Direction
- daemon.quartz.service.impl uses daemon.quartz.service, so a change to daemon.quartz.service can break daemon.quartz.service.impl, while a change to daemon.quartz.service.impl can't break daemon.quartz.service.
- Position
- Below the diagonal: daemon.quartz.service.impl uses a module listed above it, which is the healthy direction.
26→17 daemon.quartz.service.impl uses daemon.quartz.util✕
- Connections
- 1 pair of types, where a type in daemon.quartz.service.impl uses a type in daemon.quartz.util.
- The types involved
com.pig4cloud.pig.daemon.quartz.service.impl.SysJobServiceImpl→com.pig4cloud.pig.daemon.quartz.util.JobSecurityValidator
- Direction
- daemon.quartz.service.impl uses daemon.quartz.util, so a change to daemon.quartz.util can break daemon.quartz.service.impl, while a change to daemon.quartz.service.impl can't break daemon.quartz.util.
- Position
- Below the diagonal: daemon.quartz.service.impl uses a module listed above it, which is the healthy direction.
27→1 admin.controller uses admin.api.entity✕
- Connections
- 22 pairs of types, where a type in admin.controller uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.controller.SysApiKeyController→com.pig4cloud.pig.admin.api.entity.SysApiKeycom.pig4cloud.pig.admin.controller.SysAreaController→com.pig4cloud.pig.admin.api.entity.SysAreaEntitycom.pig4cloud.pig.admin.controller.SysClientController→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.controller.SysDeptController→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.admin.api.entity.SysDictcom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.admin.api.entity.SysDictItemcom.pig4cloud.pig.admin.controller.SysFileController→com.pig4cloud.pig.admin.api.entity.SysFilecom.pig4cloud.pig.admin.controller.SysFileController→com.pig4cloud.pig.admin.api.entity.SysFileGroupcom.pig4cloud.pig.admin.controller.SysI18nController→com.pig4cloud.pig.admin.api.entity.SysI18nEntitycom.pig4cloud.pig.admin.controller.SysLogController→com.pig4cloud.pig.admin.api.entity.SysLogcom.pig4cloud.pig.admin.controller.SysMenuController→com.pig4cloud.pig.admin.api.entity.SysMenucom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.entity.SysMessageEntitycom.pig4cloud.pig.admin.controller.SysPostController→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.controller.SysPublicParamController→com.pig4cloud.pig.admin.api.entity.SysPublicParamcom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.api.entity.SysRolecom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.api.entity.SysRoleWidgetcom.pig4cloud.pig.admin.controller.SysScheduleController→com.pig4cloud.pig.admin.api.entity.SysScheduleEntitycom.pig4cloud.pig.admin.controller.SysSensitiveWordController→com.pig4cloud.pig.admin.api.entity.SysSensitiveWordEntitycom.pig4cloud.pig.admin.controller.SysSocialDetailsController→com.pig4cloud.pig.admin.api.entity.SysSocialDetailscom.pig4cloud.pig.admin.controller.SysSystemConfigController→com.pig4cloud.pig.admin.api.entity.SysSystemConfigEntitycom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.admin.api.entity.SysUser
- Direction
- admin.controller uses admin.api.entity, so a change to admin.api.entity can break admin.controller, while a change to admin.controller can't break admin.api.entity.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
27→3 admin.controller uses common.core.util✕
- Connections
- 21 pairs of types, where a type in admin.controller uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.admin.controller.SysApiKeyController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysAreaController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysClientController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysDeptController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysFileController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysI18nController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysLogController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysMenuController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysPostController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysPublicParamController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysRegisterController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysScheduleController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysSensitiveWordController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysSocialDetailsController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysSystemConfigController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysSystemInfoController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysTokenController→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.common.core.util.R
- Direction
- admin.controller uses common.core.util, so a change to common.core.util can break admin.controller, while a change to admin.controller can't break common.core.util.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
27→7 admin.controller uses admin.api.vo✕
- Connections
- 7 pairs of types, where a type in admin.controller uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.admin.controller.SysDeptController→com.pig4cloud.pig.admin.api.vo.DeptExcelVOcom.pig4cloud.pig.admin.controller.SysLogController→com.pig4cloud.pig.admin.api.vo.PreLogVOcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.vo.SysMessageVOcom.pig4cloud.pig.admin.controller.SysPostController→com.pig4cloud.pig.admin.api.vo.PostExcelVOcom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.api.vo.RoleExcelVOcom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.api.vo.RoleMenuVOcom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.admin.api.vo.UserExcelVO
- Direction
- admin.controller uses admin.api.vo, so a change to admin.api.vo can break admin.controller, while a change to admin.controller can't break admin.api.vo.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
27→13 admin.controller uses admin.api.dto✕
- Connections
- 15 pairs of types, where a type in admin.controller uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.controller.SysApiKeyController→com.pig4cloud.pig.admin.api.dto.ApiKeyCreateDTOcom.pig4cloud.pig.admin.controller.SysAreaController→com.pig4cloud.pig.admin.api.dto.SysAreaSortDTOcom.pig4cloud.pig.admin.controller.SysAreaController→com.pig4cloud.pig.admin.api.dto.SysAreaUpdateDTOcom.pig4cloud.pig.admin.controller.SysClientController→com.pig4cloud.pig.admin.api.dto.SysOauthClientDetailsDTOcom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.admin.api.dto.SysDictItemSortDTOcom.pig4cloud.pig.admin.controller.SysFileController→com.pig4cloud.pig.admin.api.dto.SysFileGroupDTOcom.pig4cloud.pig.admin.controller.SysLogController→com.pig4cloud.pig.admin.api.dto.SysLogDTOcom.pig4cloud.pig.admin.controller.SysMenuController→com.pig4cloud.pig.admin.api.dto.SysMenuSortDTOcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.dto.MessageEmailDTOcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.dto.MessageHookDTOcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.dto.MessageNoticeDTOcom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.api.dto.MessageSmsDTOcom.pig4cloud.pig.admin.controller.SysRegisterController→com.pig4cloud.pig.admin.api.dto.RegisterUserDTOcom.pig4cloud.pig.admin.controller.SysSystemInfoController→com.pig4cloud.pig.admin.api.dto.SiteConfigDTOcom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.admin.api.dto.UserDTO
- Direction
- admin.controller uses admin.api.dto, so a change to admin.api.dto can break admin.controller, while a change to admin.controller can't break admin.api.dto.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
27→18 admin.controller uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in admin.controller uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.admin.controller.SysTokenController→com.pig4cloud.pig.admin.api.feign.RemoteTokenService
- Direction
- admin.controller uses admin.api.feign, so a change to admin.api.feign can break admin.controller, while a change to admin.controller can't break admin.api.feign.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
27→20 admin.controller uses admin.service✕
- Connections
- 23 pairs of types, where a type in admin.controller uses a type in admin.service.
- The types involved
com.pig4cloud.pig.admin.controller.SysApiKeyController→com.pig4cloud.pig.admin.service.SysApiKeyServicecom.pig4cloud.pig.admin.controller.SysAreaController→com.pig4cloud.pig.admin.service.SysAreaServicecom.pig4cloud.pig.admin.controller.SysClientController→com.pig4cloud.pig.admin.service.SysOauthClientDetailsServicecom.pig4cloud.pig.admin.controller.SysDeptController→com.pig4cloud.pig.admin.service.SysDeptServicecom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.admin.service.SysDictItemServicecom.pig4cloud.pig.admin.controller.SysDictController→com.pig4cloud.pig.admin.service.SysDictServicecom.pig4cloud.pig.admin.controller.SysFileController→com.pig4cloud.pig.admin.service.SysFileServicecom.pig4cloud.pig.admin.controller.SysI18nController→com.pig4cloud.pig.admin.service.SysI18nServicecom.pig4cloud.pig.admin.controller.SysLogController→com.pig4cloud.pig.admin.service.SysLogServicecom.pig4cloud.pig.admin.controller.SysMenuController→com.pig4cloud.pig.admin.service.SysMenuServicecom.pig4cloud.pig.admin.controller.SysMessageController→com.pig4cloud.pig.admin.service.SysMessageServicecom.pig4cloud.pig.admin.controller.SysPostController→com.pig4cloud.pig.admin.service.SysPostServicecom.pig4cloud.pig.admin.controller.SysPublicParamController→com.pig4cloud.pig.admin.service.SysPublicParamServicecom.pig4cloud.pig.admin.controller.SysRegisterController→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.service.SysRoleServicecom.pig4cloud.pig.admin.controller.SysRoleController→com.pig4cloud.pig.admin.service.SysRoleWidgetServicecom.pig4cloud.pig.admin.controller.SysScheduleController→com.pig4cloud.pig.admin.service.SysScheduleServicecom.pig4cloud.pig.admin.controller.SysSensitiveWordController→com.pig4cloud.pig.admin.service.SysSensitiveWordServicecom.pig4cloud.pig.admin.controller.SysSocialDetailsController→com.pig4cloud.pig.admin.service.SysSocialDetailsServicecom.pig4cloud.pig.admin.controller.SysSystemConfigController→com.pig4cloud.pig.admin.service.SysSystemConfigServicecom.pig4cloud.pig.admin.controller.SysSystemInfoController→com.pig4cloud.pig.admin.service.SysSiteConfigServicecom.pig4cloud.pig.admin.controller.SysSystemInfoController→com.pig4cloud.pig.admin.service.SysSystemInfoServicecom.pig4cloud.pig.admin.controller.SysUserController→com.pig4cloud.pig.admin.service.SysUserService
- Direction
- admin.controller uses admin.service, so a change to admin.service can break admin.controller, while a change to admin.controller can't break admin.service.
- Position
- Below the diagonal: admin.controller uses a module listed above it, which is the healthy direction.
28→1 admin.handler uses admin.api.entity✕
- Connections
- 8 pairs of types, where a type in admin.handler uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.handler.ClarityFetchTaskHandler→com.pig4cloud.pig.admin.api.entity.SysClarityDatacom.pig4cloud.pig.admin.handler.DingTalkLoginHandler→com.pig4cloud.pig.admin.api.entity.SysUsercom.pig4cloud.pig.admin.handler.LoginHandler→com.pig4cloud.pig.admin.api.entity.SysUsercom.pig4cloud.pig.admin.handler.MiniAppLoginHandler→com.pig4cloud.pig.admin.api.entity.SysSocialDetailscom.pig4cloud.pig.admin.handler.MiniAppLoginHandler→com.pig4cloud.pig.admin.api.entity.SysUsercom.pig4cloud.pig.admin.handler.SmsLoginHandler→com.pig4cloud.pig.admin.api.entity.SysUsercom.pig4cloud.pig.admin.handler.WeChatCPLoginHandler→com.pig4cloud.pig.admin.api.entity.SysUsercom.pig4cloud.pig.admin.handler.WeChatLoginHandler→com.pig4cloud.pig.admin.api.entity.SysUser
- Direction
- admin.handler uses admin.api.entity, so a change to admin.api.entity can break admin.handler, while a change to admin.handler can't break admin.api.entity.
- Position
- Below the diagonal: admin.handler uses a module listed above it, which is the healthy direction.
28→13 admin.handler uses admin.api.dto✕
- Connections
- 7 pairs of types, where a type in admin.handler uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.handler.AbstractLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.DingTalkLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.LoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.MiniAppLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.SmsLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.WeChatCPLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.handler.WeChatLoginHandler→com.pig4cloud.pig.admin.api.dto.UserInfo
- Direction
- admin.handler uses admin.api.dto, so a change to admin.api.dto can break admin.handler, while a change to admin.handler can't break admin.api.dto.
- Position
- Below the diagonal: admin.handler uses a module listed above it, which is the healthy direction.
28→19 admin.handler uses admin.mapper✕
- Connections
- 6 pairs of types, where a type in admin.handler uses a type in admin.mapper.
- The types involved
com.pig4cloud.pig.admin.handler.ClarityFetchTaskHandler→com.pig4cloud.pig.admin.mapper.SysClarityDataMappercom.pig4cloud.pig.admin.handler.ClarityFetchTaskHandler→com.pig4cloud.pig.admin.mapper.SysSocialDetailsMappercom.pig4cloud.pig.admin.handler.DingTalkLoginHandler→com.pig4cloud.pig.admin.mapper.SysSocialDetailsMappercom.pig4cloud.pig.admin.handler.MiniAppLoginHandler→com.pig4cloud.pig.admin.mapper.SysSocialDetailsMappercom.pig4cloud.pig.admin.handler.WeChatCPLoginHandler→com.pig4cloud.pig.admin.mapper.SysSocialDetailsMappercom.pig4cloud.pig.admin.handler.WeChatLoginHandler→com.pig4cloud.pig.admin.mapper.SysSocialDetailsMapper
- Direction
- admin.handler uses admin.mapper, so a change to admin.mapper can break admin.handler, while a change to admin.handler can't break admin.mapper.
- Position
- Below the diagonal: admin.handler uses a module listed above it, which is the healthy direction.
28→20 admin.handler uses admin.service✕
- Connections
- 5 pairs of types, where a type in admin.handler uses a type in admin.service.
- The types involved
com.pig4cloud.pig.admin.handler.DingTalkLoginHandler→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.handler.MiniAppLoginHandler→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.handler.SmsLoginHandler→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.handler.WeChatCPLoginHandler→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.handler.WeChatLoginHandler→com.pig4cloud.pig.admin.service.SysUserService
- Direction
- admin.handler uses admin.service, so a change to admin.service can break admin.handler, while a change to admin.handler can't break admin.service.
- Position
- Below the diagonal: admin.handler uses a module listed above it, which is the healthy direction.
29→1 auth.support.core uses admin.api.entity✕
- Connections
- 1 pair of types, where a type in auth.support.core uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.auth.support.core.OauthClientDetailsLoader→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetails
- Direction
- auth.support.core uses admin.api.entity, so a change to admin.api.entity can break auth.support.core, while a change to auth.support.core can't break admin.api.entity.
- Position
- Below the diagonal: auth.support.core uses a module listed above it, which is the healthy direction.
29→18 auth.support.core uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in auth.support.core uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.auth.support.core.OauthClientDetailsLoader→com.pig4cloud.pig.admin.api.feign.RemoteClientDetailsService
- Direction
- auth.support.core uses admin.api.feign, so a change to admin.api.feign can break auth.support.core, while a change to auth.support.core can't break admin.api.feign.
- Position
- Below the diagonal: auth.support.core uses a module listed above it, which is the healthy direction.
30→18 auth.support.handler uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in auth.support.handler uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.auth.support.handler.PigAuthenticationFailureEventHandler→com.pig4cloud.pig.admin.api.feign.RemoteUserService
- Direction
- auth.support.handler uses admin.api.feign, so a change to admin.api.feign can break auth.support.handler, while a change to auth.support.handler can't break admin.api.feign.
- Position
- Below the diagonal: auth.support.handler uses a module listed above it, which is the healthy direction.
31→1 codegen.service.impl uses admin.api.entity✕
- Connections
- 1 pair of types, where a type in codegen.service.impl uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.admin.api.entity.SysMenu
- Direction
- codegen.service.impl uses admin.api.entity, so a change to admin.api.entity can break codegen.service.impl, while a change to codegen.service.impl can't break admin.api.entity.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
31→2 codegen.service.impl uses codegen.entity✕
- Connections
- 8 pairs of types, where a type in codegen.service.impl uses a type in codegen.entity.
- The types involved
com.pig4cloud.pig.codegen.service.impl.GenDatasourceConfServiceImpl→com.pig4cloud.pig.codegen.entity.GenDatasourceConfcom.pig4cloud.pig.codegen.service.impl.GenTableColumnServiceImpl→com.pig4cloud.pig.codegen.entity.GenFieldTypecom.pig4cloud.pig.codegen.service.impl.GenTableColumnServiceImpl→com.pig4cloud.pig.codegen.entity.GenTableColumnEntitycom.pig4cloud.pig.codegen.service.impl.GenTableServiceImpl→com.pig4cloud.pig.codegen.entity.GenTablecom.pig4cloud.pig.codegen.service.impl.GenTableServiceImpl→com.pig4cloud.pig.codegen.entity.GenTableColumnEntitycom.pig4cloud.pig.codegen.service.impl.GenTemplateServiceImpl→com.pig4cloud.pig.codegen.entity.GenGroupEntitycom.pig4cloud.pig.codegen.service.impl.GenTemplateServiceImpl→com.pig4cloud.pig.codegen.entity.GenTemplateEntitycom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.entity.GenTable
- Direction
- codegen.service.impl uses codegen.entity, so a change to codegen.entity can break codegen.service.impl, while a change to codegen.service.impl can't break codegen.entity.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
31→3 codegen.service.impl uses common.core.util✕
- Connections
- 1 pair of types, where a type in codegen.service.impl uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.codegen.service.impl.GenTemplateServiceImpl→com.pig4cloud.pig.common.core.util.R
- Direction
- codegen.service.impl uses common.core.util, so a change to common.core.util can break codegen.service.impl, while a change to codegen.service.impl can't break common.core.util.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
31→8 codegen.service.impl uses codegen.util.vo✕
- Connections
- 5 pairs of types, where a type in codegen.service.impl uses a type in codegen.util.vo.
- The types involved
com.pig4cloud.pig.codegen.service.impl.CreateTableServiceImpl→com.pig4cloud.pig.codegen.util.vo.GenCreateTableColumnVOcom.pig4cloud.pig.codegen.service.impl.CreateTableServiceImpl→com.pig4cloud.pig.codegen.util.vo.GenCreateTableVOcom.pig4cloud.pig.codegen.service.impl.GenGroupServiceImpl→com.pig4cloud.pig.codegen.util.vo.GroupVOcom.pig4cloud.pig.codegen.service.impl.GenGroupServiceImpl→com.pig4cloud.pig.codegen.util.vo.TemplateGroupDTOcom.pig4cloud.pig.codegen.service.impl.GenTemplateServiceImpl→com.pig4cloud.pig.codegen.util.vo.GenTemplateFileVO
- Direction
- codegen.service.impl uses codegen.util.vo, so a change to codegen.util.vo can break codegen.service.impl, while a change to codegen.service.impl can't break codegen.util.vo.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
31→14 codegen.service.impl uses codegen.service✕
- Connections
- 17 pairs of types, where a type in codegen.service.impl uses a type in codegen.service.
- The types involved
com.pig4cloud.pig.codegen.service.impl.CreateTableServiceImpl→com.pig4cloud.pig.codegen.service.GenCreateTableServicecom.pig4cloud.pig.codegen.service.impl.GenDatasourceConfServiceImpl→com.pig4cloud.pig.codegen.service.GenDatasourceConfServicecom.pig4cloud.pig.codegen.service.impl.GenFieldTypeServiceImpl→com.pig4cloud.pig.codegen.service.GenFieldTypeServicecom.pig4cloud.pig.codegen.service.impl.GenGroupServiceImpl→com.pig4cloud.pig.codegen.service.GenGroupServicecom.pig4cloud.pig.codegen.service.impl.GenGroupServiceImpl→com.pig4cloud.pig.codegen.service.GenTemplateGroupServicecom.pig4cloud.pig.codegen.service.impl.GenTableColumnServiceImpl→com.pig4cloud.pig.codegen.service.GenTableColumnServicecom.pig4cloud.pig.codegen.service.impl.GenTableServiceImpl→com.pig4cloud.pig.codegen.service.GenGroupServicecom.pig4cloud.pig.codegen.service.impl.GenTableServiceImpl→com.pig4cloud.pig.codegen.service.GenTableColumnServicecom.pig4cloud.pig.codegen.service.impl.GenTableServiceImpl→com.pig4cloud.pig.codegen.service.GenTableServicecom.pig4cloud.pig.codegen.service.impl.GenTemplateGroupServiceImpl→com.pig4cloud.pig.codegen.service.GenTemplateGroupServicecom.pig4cloud.pig.codegen.service.impl.GenTemplateServiceImpl→com.pig4cloud.pig.codegen.service.GenTemplateServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GenFieldTypeServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GenGroupServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GenTableColumnServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GenTableServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GenTemplateServicecom.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.codegen.service.GeneratorService
- Direction
- codegen.service.impl uses codegen.service, so a change to codegen.service can break codegen.service.impl, while a change to codegen.service.impl can't break codegen.service.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
31→18 codegen.service.impl uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in codegen.service.impl uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.codegen.service.impl.GeneratorServiceImpl→com.pig4cloud.pig.admin.api.feign.RemoteMenuService
- Direction
- codegen.service.impl uses admin.api.feign, so a change to admin.api.feign can break codegen.service.impl, while a change to codegen.service.impl can't break admin.api.feign.
- Position
- Below the diagonal: codegen.service.impl uses a module listed above it, which is the healthy direction.
32→15 common.excel.aop uses common.excel.handler✕
- Connections
- 1 pair of types, where a type in common.excel.aop uses a type in common.excel.handler.
- The types involved
com.pig4cloud.pig.common.excel.aop.ResponseExcelReturnValueHandler→com.pig4cloud.pig.common.excel.handler.SheetWriteHandler
- Direction
- common.excel.aop uses common.excel.handler, so a change to common.excel.handler can break common.excel.aop, while a change to common.excel.aop can't break common.excel.handler.
- Position
- Below the diagonal: common.excel.aop uses a module listed above it, which is the healthy direction.
32→22 common.excel.aop uses common.excel.annotation✕
- Connections
- 1 pair of types, where a type in common.excel.aop uses a type in common.excel.annotation.
- The types involved
com.pig4cloud.pig.common.excel.aop.DynamicNameAspect→com.pig4cloud.pig.common.excel.annotation.ResponseExcel
- Direction
- common.excel.aop uses common.excel.annotation, so a change to common.excel.annotation can break common.excel.aop, while a change to common.excel.aop can't break common.excel.annotation.
- Position
- Below the diagonal: common.excel.aop uses a module listed above it, which is the healthy direction.
33→13 common.log.event uses admin.api.dto✕
- Connections
- 1 pair of types, where a type in common.log.event uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.common.log.event.SysLogEvent→com.pig4cloud.pig.admin.api.dto.SysLogDTO
- Direction
- common.log.event uses admin.api.dto, so a change to admin.api.dto can break common.log.event, while a change to common.log.event can't break admin.api.dto.
- Position
- Below the diagonal: common.log.event uses a module listed above it, which is the healthy direction.
33→18 common.log.event uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in common.log.event uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.common.log.event.SysLogListener→com.pig4cloud.pig.admin.api.feign.RemoteLogService
- Direction
- common.log.event uses admin.api.feign, so a change to admin.api.feign can break common.log.event, while a change to common.log.event can't break admin.api.feign.
- Position
- Below the diagonal: common.log.event uses a module listed above it, which is the healthy direction.
34→13 common.security.service uses admin.api.dto✕
- Connections
- 1 pair of types, where a type in common.security.service uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.common.security.service.PigUserDetailsService→com.pig4cloud.pig.admin.api.dto.UserInfo
- Direction
- common.security.service uses admin.api.dto, so a change to admin.api.dto can break common.security.service, while a change to common.security.service can't break admin.api.dto.
- Position
- Below the diagonal: common.security.service uses a module listed above it, which is the healthy direction.
34→18 common.security.service uses admin.api.feign✕
- Connections
- 3 pairs of types, where a type in common.security.service uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.common.security.service.PigDefaultUserDetailsServiceImpl→com.pig4cloud.pig.admin.api.feign.RemoteUserServicecom.pig4cloud.pig.common.security.service.PigMobileUserDetailServiceImpl→com.pig4cloud.pig.admin.api.feign.RemoteUserServicecom.pig4cloud.pig.common.security.service.PigRemoteRegisteredClientRepository→com.pig4cloud.pig.admin.api.feign.RemoteClientDetailsService
- Direction
- common.security.service uses admin.api.feign, so a change to admin.api.feign can break common.security.service, while a change to common.security.service can't break admin.api.feign.
- Position
- Below the diagonal: common.security.service uses a module listed above it, which is the healthy direction.
35→1 admin.service.impl uses admin.api.entity✕
- Connections
- 20 pairs of types, where a type in admin.service.impl uses a type in admin.api.entity.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysApiKeyServiceImpl→com.pig4cloud.pig.admin.api.entity.SysApiKeycom.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.admin.api.entity.SysAreaEntitycom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.service.impl.SysDictItemServiceImpl→com.pig4cloud.pig.admin.api.entity.SysDictItemcom.pig4cloud.pig.admin.service.impl.SysDictServiceImpl→com.pig4cloud.pig.admin.api.entity.SysDictcom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.admin.api.entity.SysFileGroupcom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.admin.api.entity.SysMenucom.pig4cloud.pig.admin.service.impl.SysOauthClientDetailsServiceImpl→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.service.impl.SysPostServiceImpl→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.service.impl.SysPublicParamServiceImpl→com.pig4cloud.pig.admin.api.entity.SysPublicParamcom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.admin.api.entity.SysRolecom.pig4cloud.pig.admin.service.impl.SysRoleWidgetServiceImpl→com.pig4cloud.pig.admin.api.entity.SysRoleWidgetcom.pig4cloud.pig.admin.service.impl.SysScheduleServiceImpl→com.pig4cloud.pig.admin.api.entity.SysScheduleEntitycom.pig4cloud.pig.admin.service.impl.SysSensitiveWordServiceImpl→com.pig4cloud.pig.admin.api.entity.SysSensitiveWordEntitycom.pig4cloud.pig.admin.service.impl.SysSiteConfigServiceImpl→com.pig4cloud.pig.admin.api.entity.SysOauthClientDetailscom.pig4cloud.pig.admin.service.impl.SysSystemConfigServiceImpl→com.pig4cloud.pig.admin.api.entity.SysSystemConfigEntitycom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.entity.SysDeptcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.entity.SysPostcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.entity.SysRolecom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.entity.SysUser
- Direction
- admin.service.impl uses admin.api.entity, so a change to admin.api.entity can break admin.service.impl, while a change to admin.service.impl can't break admin.api.entity.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→3 admin.service.impl uses common.core.util✕
- Connections
- 16 pairs of types, where a type in admin.service.impl uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysApiKeyServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysDictItemServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysDictServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysI18nServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysOauthClientDetailsServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysPostServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysPublicParamServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysSystemConfigServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysSystemInfoServiceImpl→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.common.core.util.R
- Direction
- admin.service.impl uses common.core.util, so a change to common.core.util can break admin.service.impl, while a change to admin.service.impl can't break common.core.util.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→7 admin.service.impl uses admin.api.vo✕
- Connections
- 11 pairs of types, where a type in admin.service.impl uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.admin.api.vo.SysAreaManageVOcom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.api.vo.DeptExcelVOcom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.api.vo.OrgTreeVOcom.pig4cloud.pig.admin.service.impl.SysLogServiceImpl→com.pig4cloud.pig.admin.api.vo.PreLogVOcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.vo.SysMessageVOcom.pig4cloud.pig.admin.service.impl.SysPostServiceImpl→com.pig4cloud.pig.admin.api.vo.PostExcelVOcom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.admin.api.vo.RoleExcelVOcom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.admin.api.vo.RoleMenuVOcom.pig4cloud.pig.admin.service.impl.SysSocialDetailsServiceImpl→com.pig4cloud.pig.admin.api.vo.SysSocialDetailsVOcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.vo.UserExcelVOcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.vo.UserVO
- Direction
- admin.service.impl uses admin.api.vo, so a change to admin.api.vo can break admin.service.impl, while a change to admin.service.impl can't break admin.api.vo.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→13 admin.service.impl uses admin.api.dto✕
- Connections
- 17 pairs of types, where a type in admin.service.impl uses a type in admin.api.dto.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysApiKeyServiceImpl→com.pig4cloud.pig.admin.api.dto.ApiKeyCreateDTOcom.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.admin.api.dto.SysAreaSortDTOcom.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.admin.api.dto.SysAreaUpdateDTOcom.pig4cloud.pig.admin.service.impl.SysDictItemServiceImpl→com.pig4cloud.pig.admin.api.dto.SysDictItemSortDTOcom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.admin.api.dto.SysFileGroupDTOcom.pig4cloud.pig.admin.service.impl.SysLogServiceImpl→com.pig4cloud.pig.admin.api.dto.SysLogDTOcom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.admin.api.dto.SysMenuSortDTOcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.dto.MessageEmailDTOcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.dto.MessageHookDTOcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.dto.MessageNoticeDTOcom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.dto.MessageSmsDTOcom.pig4cloud.pig.admin.service.impl.SysOauthClientDetailsServiceImpl→com.pig4cloud.pig.admin.api.dto.SysOauthClientDetailsDTOcom.pig4cloud.pig.admin.service.impl.SysSiteConfigServiceImpl→com.pig4cloud.pig.admin.api.dto.SiteConfigDTOcom.pig4cloud.pig.admin.service.impl.SysSocialDetailsServiceImpl→com.pig4cloud.pig.admin.api.dto.UserInfocom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.dto.RegisterUserDTOcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.dto.UserDTOcom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.api.dto.UserInfo
- Direction
- admin.service.impl uses admin.api.dto, so a change to admin.api.dto can break admin.service.impl, while a change to admin.service.impl can't break admin.api.dto.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→16 admin.service.impl uses common.file.core✕
- Connections
- 3 pairs of types, where a type in admin.service.impl uses a type in common.file.core.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.common.file.core.FilePropertiescom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.common.file.core.FileTemplatecom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.common.file.core.FileTemplate
- Direction
- admin.service.impl uses common.file.core, so a change to common.file.core can break admin.service.impl, while a change to admin.service.impl can't break common.file.core.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→18 admin.service.impl uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in admin.service.impl uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.api.feign.RemoteLogService
- Direction
- admin.service.impl uses admin.api.feign, so a change to admin.api.feign can break admin.service.impl, while a change to admin.service.impl can't break admin.api.feign.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→19 admin.service.impl uses admin.mapper✕
- Connections
- 16 pairs of types, where a type in admin.service.impl uses a type in admin.mapper.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.mapper.SysDeptMappercom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.mapper.SysPostMappercom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.mapper.SysRoleMappercom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserMappercom.pig4cloud.pig.admin.service.impl.SysDictServiceImpl→com.pig4cloud.pig.admin.mapper.SysDictItemMappercom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.admin.mapper.SysFileGroupMappercom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.admin.mapper.SysRoleMenuMappercom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.mapper.SysFileMappercom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.mapper.SysMessageRelationMappercom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.mapper.SysSystemConfigMappercom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserMappercom.pig4cloud.pig.admin.service.impl.SysSocialDetailsServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserMappercom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.mapper.SysDeptMappercom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserDeptMappercom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserPostMappercom.pig4cloud.pig.admin.service.impl.SysUserServiceImpl→com.pig4cloud.pig.admin.mapper.SysUserRoleMapper
- Direction
- admin.service.impl uses admin.mapper, so a change to admin.mapper can break admin.service.impl, while a change to admin.service.impl can't break admin.mapper.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→20 admin.service.impl uses admin.service✕
- Connections
- 35 pairs of types, where a type in admin.service.impl uses a type in admin.service. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysApiKeyServiceImpl→com.pig4cloud.pig.admin.service.SysApiKeyServicecom.pig4cloud.pig.admin.service.impl.SysApiKeyServiceImpl→com.pig4cloud.pig.admin.service.SysUserServicecom.pig4cloud.pig.admin.service.impl.SysAreaServiceImpl→com.pig4cloud.pig.admin.service.SysAreaServicecom.pig4cloud.pig.admin.service.impl.SysDeptServiceImpl→com.pig4cloud.pig.admin.service.SysDeptServicecom.pig4cloud.pig.admin.service.impl.SysDictItemServiceImpl→com.pig4cloud.pig.admin.service.SysDictItemServicecom.pig4cloud.pig.admin.service.impl.SysDictItemServiceImpl→com.pig4cloud.pig.admin.service.SysDictServicecom.pig4cloud.pig.admin.service.impl.SysDictServiceImpl→com.pig4cloud.pig.admin.service.SysDictServicecom.pig4cloud.pig.admin.service.impl.SysFileServiceImpl→com.pig4cloud.pig.admin.service.SysFileServicecom.pig4cloud.pig.admin.service.impl.SysI18nServiceImpl→com.pig4cloud.pig.admin.service.SysI18nServicecom.pig4cloud.pig.admin.service.impl.SysLogServiceImpl→com.pig4cloud.pig.admin.service.SysLogServicecom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.admin.service.SysI18nServicecom.pig4cloud.pig.admin.service.impl.SysMenuServiceImpl→com.pig4cloud.pig.admin.service.SysMenuServicecom.pig4cloud.pig.admin.service.impl.SysMessageServiceImpl→com.pig4cloud.pig.admin.service.SysMessageServicecom.pig4cloud.pig.admin.service.impl.SysOauthClientDetailsServiceImpl→com.pig4cloud.pig.admin.service.SysOauthClientDetailsServicecom.pig4cloud.pig.admin.service.impl.SysPostServiceImpl→com.pig4cloud.pig.admin.service.SysPostServicecom.pig4cloud.pig.admin.service.impl.SysPublicParamServiceImpl→com.pig4cloud.pig.admin.service.SysPublicParamServicecom.pig4cloud.pig.admin.service.impl.SysRoleMenuServiceImpl→com.pig4cloud.pig.admin.service.SysRoleMenuServicecom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.admin.service.SysRoleMenuServicecom.pig4cloud.pig.admin.service.impl.SysRoleServiceImpl→com.pig4cloud.pig.admin.service.SysRoleServicecom.pig4cloud.pig.admin.service.impl.SysRoleWidgetServiceImpl→com.pig4cloud.pig.admin.service.SysRoleWidgetServicecom.pig4cloud.pig.admin.service.impl.SysScheduleServiceImpl→com.pig4cloud.pig.admin.service.SysScheduleServicecom.pig4cloud.pig.admin.service.impl.SysSensitiveWordServiceImpl→com.pig4cloud.pig.admin.service.SysSensitiveWordServicecom.pig4cloud.pig.admin.service.impl.SysSiteConfigServiceImpl→com.pig4cloud.pig.admin.service.SysI18nServicecom.pig4cloud.pig.admin.service.impl.SysSiteConfigServiceImpl→com.pig4cloud.pig.admin.service.SysOauthClientDetailsServicecom.pig4cloud.pig.admin.service.impl.SysSiteConfigServiceImpl→com.pig4cloud.pig.admin.service.SysPublicParamService
- Direction
- admin.service.impl uses admin.service, so a change to admin.service can break admin.service.impl, while a change to admin.service.impl can't break admin.service.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
35→28 admin.service.impl uses admin.handler✕
- Connections
- 2 pairs of types, where a type in admin.service.impl uses a type in admin.handler.
- The types involved
com.pig4cloud.pig.admin.service.impl.SysSocialDetailsServiceImpl→com.pig4cloud.pig.admin.handler.LoginHandlercom.pig4cloud.pig.admin.service.impl.SysSystemInfoServiceImpl→com.pig4cloud.pig.admin.handler.ClarityFetchTaskHandler
- Direction
- admin.service.impl uses admin.handler, so a change to admin.handler can break admin.service.impl, while a change to admin.service.impl can't break admin.handler.
- Position
- Below the diagonal: admin.service.impl uses a module listed above it, which is the healthy direction.
36→3 auth.endpoint uses common.core.util✕
- Connections
- 2 pairs of types, where a type in auth.endpoint uses a type in common.core.util.
- The types involved
com.pig4cloud.pig.auth.endpoint.ImageCodeEndpoint→com.pig4cloud.pig.common.core.util.Rcom.pig4cloud.pig.auth.endpoint.PigTokenEndpoint→com.pig4cloud.pig.common.core.util.R
- Direction
- auth.endpoint uses common.core.util, so a change to common.core.util can break auth.endpoint, while a change to auth.endpoint can't break common.core.util.
- Position
- Below the diagonal: auth.endpoint uses a module listed above it, which is the healthy direction.
36→7 auth.endpoint uses admin.api.vo✕
- Connections
- 1 pair of types, where a type in auth.endpoint uses a type in admin.api.vo.
- The types involved
com.pig4cloud.pig.auth.endpoint.PigTokenEndpoint→com.pig4cloud.pig.admin.api.vo.TokenVO
- Direction
- auth.endpoint uses admin.api.vo, so a change to admin.api.vo can break auth.endpoint, while a change to auth.endpoint can't break admin.api.vo.
- Position
- Below the diagonal: auth.endpoint uses a module listed above it, which is the healthy direction.
36→29 auth.endpoint uses auth.support.core✕
- Connections
- 2 pairs of types, where a type in auth.endpoint uses a type in auth.support.core.
- The types involved
com.pig4cloud.pig.auth.endpoint.PigTokenEndpoint→com.pig4cloud.pig.auth.support.core.AuthCaptchaSupportcom.pig4cloud.pig.auth.endpoint.PigTokenEndpoint→com.pig4cloud.pig.auth.support.core.OauthClientDetailsLoader
- Direction
- auth.endpoint uses auth.support.core, so a change to auth.support.core can break auth.endpoint, while a change to auth.endpoint can't break auth.support.core.
- Position
- Below the diagonal: auth.endpoint uses a module listed above it, which is the healthy direction.
37→29 auth.support.filter uses auth.support.core✕
- Connections
- 3 pairs of types, where a type in auth.support.filter uses a type in auth.support.core.
- The types involved
com.pig4cloud.pig.auth.support.filter.FormLoginValidateCodeFilter→com.pig4cloud.pig.auth.support.core.AuthCaptchaSupportcom.pig4cloud.pig.auth.support.filter.PasswordDecoderFilter→com.pig4cloud.pig.auth.support.core.OauthClientDetailsLoadercom.pig4cloud.pig.auth.support.filter.ValidateCodeFilter→com.pig4cloud.pig.auth.support.core.AuthCaptchaSupport
- Direction
- auth.support.filter uses auth.support.core, so a change to auth.support.core can break auth.support.filter, while a change to auth.support.filter can't break auth.support.core.
- Position
- Below the diagonal: auth.support.filter uses a module listed above it, which is the healthy direction.
37→30 auth.support.filter uses auth.support.handler✕
- Connections
- 1 pair of types, where a type in auth.support.filter uses a type in auth.support.handler.
- The types involved
com.pig4cloud.pig.auth.support.filter.FormLoginValidateCodeFilter→com.pig4cloud.pig.auth.support.handler.FormAuthenticationFailureHandler
- Direction
- auth.support.filter uses auth.support.handler, so a change to auth.support.handler can break auth.support.filter, while a change to auth.support.filter can't break auth.support.handler.
- Position
- Below the diagonal: auth.support.filter uses a module listed above it, which is the healthy direction.
38→4 common.excel uses common.excel.head✕
- Connections
- 1 pair of types, where a type in common.excel uses a type in common.excel.head.
- The types involved
com.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.head.I18nHeaderCellWriteHandler
- Direction
- common.excel uses common.excel.head, so a change to common.excel.head can break common.excel, while a change to common.excel can't break common.excel.head.
- Position
- Below the diagonal: common.excel uses a module listed above it, which is the healthy direction.
38→9 common.excel uses common.excel.enhance✕
- Connections
- 1 pair of types, where a type in common.excel uses a type in common.excel.enhance.
- The types involved
com.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.enhance.WriterBuilderEnhancer
- Direction
- common.excel uses common.excel.enhance, so a change to common.excel.enhance can break common.excel, while a change to common.excel can't break common.excel.enhance.
- Position
- Below the diagonal: common.excel uses a module listed above it, which is the healthy direction.
38→15 common.excel uses common.excel.handler✕
- Connections
- 3 pairs of types, where a type in common.excel uses a type in common.excel.handler.
- The types involved
com.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.handler.ManySheetWriteHandlercom.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.handler.SheetWriteHandlercom.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.handler.SingleSheetWriteHandler
- Direction
- common.excel uses common.excel.handler, so a change to common.excel.handler can break common.excel, while a change to common.excel can't break common.excel.handler.
- Position
- Below the diagonal: common.excel uses a module listed above it, which is the healthy direction.
38→32 common.excel uses common.excel.aop✕
- Connections
- 3 pairs of types, where a type in common.excel uses a type in common.excel.aop.
- The types involved
com.pig4cloud.pig.common.excel.ExcelHandlerConfiguration→com.pig4cloud.pig.common.excel.aop.ResponseExcelReturnValueHandlercom.pig4cloud.pig.common.excel.ResponseExcelAutoConfiguration→com.pig4cloud.pig.common.excel.aop.DynamicNameAspectcom.pig4cloud.pig.common.excel.ResponseExcelAutoConfiguration→com.pig4cloud.pig.common.excel.aop.ResponseExcelReturnValueHandler
- Direction
- common.excel uses common.excel.aop, so a change to common.excel.aop can break common.excel, while a change to common.excel can't break common.excel.aop.
- Position
- Below the diagonal: common.excel uses a module listed above it, which is the healthy direction.
39→18 common.log uses admin.api.feign✕
- Connections
- 1 pair of types, where a type in common.log uses a type in admin.api.feign.
- The types involved
com.pig4cloud.pig.common.log.LogAutoConfiguration→com.pig4cloud.pig.admin.api.feign.RemoteLogService
- Direction
- common.log uses admin.api.feign, so a change to admin.api.feign can break common.log, while a change to common.log can't break admin.api.feign.
- Position
- Below the diagonal: common.log uses a module listed above it, which is the healthy direction.
39→33 common.log uses common.log.event✕
- Connections
- 1 pair of types, where a type in common.log uses a type in common.log.event.
- The types involved
com.pig4cloud.pig.common.log.LogAutoConfiguration→com.pig4cloud.pig.common.log.event.SysLogListener
- Direction
- common.log uses common.log.event, so a change to common.log.event can break common.log, while a change to common.log can't break common.log.event.
- Position
- Below the diagonal: common.log uses a module listed above it, which is the healthy direction.
40→30 auth.config uses auth.support.handler✕
- Connections
- 2 pairs of types, where a type in auth.config uses a type in auth.support.handler.
- The types involved
com.pig4cloud.pig.auth.config.AuthorizationServerConfiguration→com.pig4cloud.pig.auth.support.handler.PigAuthenticationFailureEventHandlercom.pig4cloud.pig.auth.config.AuthorizationServerConfiguration→com.pig4cloud.pig.auth.support.handler.PigAuthenticationSuccessEventHandler
- Direction
- auth.config uses auth.support.handler, so a change to auth.support.handler can break auth.config, while a change to auth.config can't break auth.support.handler.
- Position
- Below the diagonal: auth.config uses a module listed above it, which is the healthy direction.
40→37 auth.config uses auth.support.filter✕
- Connections
- 3 pairs of types, where a type in auth.config uses a type in auth.support.filter.
- The types involved
com.pig4cloud.pig.auth.config.AuthorizationServerConfiguration→com.pig4cloud.pig.auth.support.filter.FormLoginValidateCodeFiltercom.pig4cloud.pig.auth.config.AuthorizationServerConfiguration→com.pig4cloud.pig.auth.support.filter.PasswordDecoderFiltercom.pig4cloud.pig.auth.config.AuthorizationServerConfiguration→com.pig4cloud.pig.auth.support.filter.ValidateCodeFilter
- Direction
- auth.config uses auth.support.filter, so a change to auth.support.filter can break auth.config, while a change to auth.config can't break auth.support.filter.
- Position
- Below the diagonal: auth.config 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 |
|---|---|---|
| A07:2025 — Authentication Failures | 126 | High / Critical |
| A02:2025 — Security Misconfiguration | 40 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 36 | High / Critical |
| A05:2025 — Injection | 15 | High / Critical |
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +6.2 pts | Medium | Keyboard semantics |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.6 pts | Medium | Page structure |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +1.7 pts | Low | ADR Quality |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +2.9 pts | Medium | Forms & labels |
| 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. | +2.6 pts | Medium | Visual & motion safety |
| Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. | +1.2 pts | Low | REDACTED Scanning |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +0.9 pts | Low | REDACTED Scanning |
| Resolve the 1 Banned license finding(s) in License Compliance. | +0.9 pts | Low | License Compliance |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.1 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 2.7 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.0 | Slop | Secrets (history): High secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.6 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): High secret: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 61 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, 428 of 439 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 (.java) 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.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — a Maven build resolved 359 artifact(s) (238 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (pig-common/pig-common-bom/REDACTED), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. 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. D24 compares a comment's words with the identifiers, literals and constructs of the code it annotates, using English function-word and rationale lexicons. Comments in another script or language were left unread rather than counted as clean.
- 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.
- AC3 Page structure — 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. 7 further occurrence(s) are not listed individually; the score already reflects all 47.
- AC4 Keyboard semantics — 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. 83 further occurrence(s) are not listed individually; the score already reflects all 123.
- 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 18 — an image could not be pulled) — pig-codegen Warning context canceled pig-upms Warning context canceled pig-mysql Warning context canceled pig-gateway Warning context canceled pig-quartz Warning context canceled pig-monitor Warning context canceled pig-register Warning context canceled pig-auth Warning context canceled Error response from daemon: Get "https://registry.cn-hangzhou.aliyuncs.com/v2/": Forbidden; the earlier `compose pull` step reported: pig-upms Warning context canceled pig-mysql Warning context canceled pig-gateway Warning context canceled WARNING: Some service image(s) must be built from source by running: docker compose build pig-register pig-auth pig-quartz pig-codegen pig-monitor pig-upms pig-mysql pig-gateway Error response from daemon: Get "https://registry.cn-hangzhou.aliyuncs.com/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 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").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a 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.
- 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.
- 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".
- 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
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was doT.doT.template at 21.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with doT.doT.template (cyclomatic 21), MonitorStatService.service (cyclomatic 20), PigCustomOpaqueTokenIntrospector.handleApiKeyToken (cyclomatic 17). — 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 4 together lifts Cyclomatic Complexity from 9.3 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
9 method(s) exceeded the cognitive complexity threshold of 15; the worst was PigSentinelInvocationHandler.invoke at 39.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with PigSentinelInvocationHandler.invoke (cognitive 39). — Refactoring it lifts Cognitive Complexity from 8.3 to about 8.6/10.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with RedisUtils.java. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
20 duplicated block group(s) detected. 2.4 % of the production lines (998 of 41,240) are in a reported copy. A further 27 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 4 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with SysPostServiceImpl.java, RedisUtils.java, LocalDateStringConverter.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 4 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with SysUserServiceImpl.java (2), DictResolver.java, OAuth2ResourceOwnerPasswordAuthenticationProvider.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with JsonLongArrayTypeHandler.java (3). — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
20 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 2 module(s) off the main sequence, with abstractness counted on 19 of the 20 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
5 of 66 classes have LCOM4 above 3.
What to do
- Resolve the 5 Low cohesion finding(s) in Cohesion (LCOM4) — start with GlobalBizExceptionHandler.java, REDACTED, SysDeptServiceImpl.java. — One of this dimension's main actionable groups (5 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 50 tests.
D13 · REDACTED Scanning
1 secret(s) detected. 2 password hash(es) are listed to check and are not counted as leaked credentials.
What to do
- Resolve the 2 REDACTED finding(s) in REDACTED Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D14 · License Compliance
1 of 10 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 25 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 199 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java (3 of 4 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with SysUserServiceImpl.java. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
51 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysMessageServiceImpl.java. Counted over 209 of the 532 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 41240 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.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 1 document(s) read across 25 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 20 build units (Maven) flagged as possibly oversized/incoherent.
D27 · Navigability
58 % of calls cross a namespace and 17 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
136 finding(s): 0 critical, 89 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 72 High secret finding(s) in Secrets (history) — start with REDACTED (30), REDACTED (29), REDACTED (4). — One of this dimension's main actionable groups (72 issue-level).
- Resolve the 33 REDACTED finding(s) in Secrets (history) — start with REDACTED (8), REDACTED (7), REDACTED (4). — One of this dimension's main actionable groups (33 recommendation-level).
- Resolve the 17 REDACTED finding(s) in Secrets (history) — start with REDACTED (5), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (17 issue-level).
D29 · Static Analysis (SAST)
15 finding(s): 0 critical, 9 high, 4 medium, 2 low. 3 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 7 file(s) — `pig-auth/src/main/resources/application.yml`, `pig-boot/src/main/resources/application.yml`, `pig-gateway/src/main/resources/application.yml`, `pig-upms/pig-upms-biz/src/main/resources/application.yml`, `pig-visual/pig-codegen/src/main/resources/application.yml`, … (+2 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 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 issue-level).
- No action in Static Analysis (SAST) — all 3 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 (3 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
36 finding(s): 1 critical, 4 high, 1 medium, 30 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
40 finding(s): 0 critical, 17 high, 9 medium, 14 low.
What to do
- Resolve the 17 High IaC finding(s) in IaC & Container Security — start with REDACTED (15), REDACTED, REDACTED. — One of this dimension's main actionable groups (17 issue-level).
- Resolve the 14 Low IaC finding(s) in IaC & Container Security — start with REDACTED (14). — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 9 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
D34 · Knowledge Freshness
26 of 209 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is pig-common/pig-common-core/src/main/java/com/pig4cloud/pig/common/core/util/RetOps.java. Counted over 209 of the 532 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 26 Orphaned file finding(s) in Knowledge Freshness — start with RetOps.java, PigAuthenticationSuccessEventHandler.java, CustomeOAuth2AccessTokenGenerator.java. — One of this dimension's main actionable groups (26 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: PigTokenEndpoint.java↔RemoteTokenService.java 67%; SysUser.java↔UserVO.java 64%; RemoteUserService.java↔SysUserController.java 58%
What to do
- Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with PigTokenEndpoint.java. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Change coupling finding(s) in Change Coupling — start with SysUser.java, RemoteUserService.java, SysUserController.java. — One of this dimension's main actionable groups (3 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 47 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
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×2) — pig-auth/src/main/resources/templates/ftl/confirm.ftl:32, pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:23
- 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. — pig-auth/src/main/resources/templates/ftl/confirm.ftl:34
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:38
- 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. (×4) — pig-auth/src/main/resources/templates/ftl/login.ftl:21, pig-auth/src/main/resources/templates/ftl/login.ftl:26, pig-visual/pig-monitor/src/main/resources/druid/login.html:58, …
- A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — pig-visual/pig-monitor/src/main/resources/druid/login.html:53
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
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×14) — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:2, pig-visual/pig-monitor/src/main/resources/druid/activeConnectionStackTrace.html:2, pig-visual/pig-monitor/src/main/resources/druid/api.html:2, …
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×15) — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:2, pig-visual/pig-monitor/src/main/resources/druid/activeConnectionStackTrace.html:2, pig-visual/pig-monitor/src/main/resources/druid/api.html:2, …
- 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). (×8) — pig-visual/pig-monitor/src/main/resources/druid/index.html:19, pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:21, pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:28, …
- An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. — pig-visual/pig-monitor/src/main/resources/druid/nopermit.html:2
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:21
- An empty heading appears in the document outline announced with no text. Give the heading text, or remove it if it's decorative. — pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:21
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. (×40) — pig-visual/pig-monitor/src/main/resources/druid/header.html:2, pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:19, pig-visual/pig-monitor/src/main/resources/druid/spring.html:38, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC6 · Visual & motion safety
- `.animate-spin-slow` moves (`animation: spin 2s linear infinite`) 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. — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:30
- <button> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:38
- <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). (×3) — pig-auth/src/main/resources/templates/ftl/login.ftl:21, pig-auth/src/main/resources/templates/ftl/login.ftl:26, pig-auth/src/main/resources/templates/ftl/login.ftl:33
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.
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
- `FeignClientEndpoint` is a singleton (@Bean: the container shares one instance across every request thread) but mutates instance state outside any lock (clientList; e.g. `clientList` in `afterSingletonsInstantiated` at line 45). — pig-common/pig-common-feign/src/main/java/com/pig4cloud/pig/common/feign/endpoint/FeignClientEndpoint.java:28
What to do
- Java/Kotlin: keep container singletons stateless — move per-request data into locals or a request-scoped bean — or back the state with java.util.concurrent types (ConcurrentHashMap, AtomicInteger/AtomicReference), guard it with synchronized / a Lock (Kotlin: withLock), or mark a flag that is only ever overwritten volatile (@Volatile).
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `SysUserService` declares 19 abstract methods: `changePassword`, `checkPassword`, `deleteUserByIds`, `forgetUserPassword`, `getUserDeptList`, `getUserInfo`, `getUsersWithRolePage`, `importUser`, `listAncestorUsers`, `listUser`, `lockUser`, `registerUser`, `resetUserPassword`, `saveUser`, `selectUserVoById`, `unbinding`, `updateUser`, `updateUserDept`, `updateUserInfo`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/SysUserService.java:41
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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
What to do
- Run the test suite in CI via an explicit runner step (`mvn test` for the toolchain this pipeline already uses) and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- Only 14/17 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `pig-boot`, `pig-common/pig-common-oss`, `pig-register`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 2 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:6
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
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.
P7 · Outbound HTTP resilience
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- `https://cdn.tailwindcss.com` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — pig-auth/src/main/resources/templates/ftl/layout/base.ftl:7
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X12 · Unreachable branch
- `parameterNames == null` can never be true where it stands: control only reaches it when `parameterNames != null` (line 111). The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it. — REDACTED:113
What to do
- Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
- `serviceList[i]` is text this program did not author, and it is written into an unquoted attribute through the DOM library's `.append()` 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. HTML text encoding does not help in an unquoted attribute — whitespace ends it; quote the attribute and encode the value. — pig-visual/pig-monitor/src/main/resources/druid/js/common.js:36
- `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. (×2) — pig-visual/pig-monitor/src/main/resources/druid/js/common.js:114, pig-visual/pig-monitor/src/main/resources/druid/js/common.js:126
- `str` is text this program did not author, and it is written into a quoted attribute value through the DOM library's `.append()` 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. — pig-visual/pig-monitor/src/main/resources/druid/js/lang.js:270
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.
X27 · Collection changed while being enumerated
X3 · Exception handling
- `catch (RuntimeException)` 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. — pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/util/RestTaskUrlValidator.java:77
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/service/impl/GenDatasourceConfServiceImpl.java:202, REDACTED:124
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X4 · Structured logging
- `debug` at line 103 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.debug("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. — pig-common/pig-common-core/src/main/java/com/pig4cloud/pig/common/core/util/SpringContextHolder.java:103
- `debug` at line 47 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.debug("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. — pig-auth/src/main/java/com/pig4cloud/pig/auth/support/sms/OAuth2ResourceOwnerSmsAuthenticationProvider.java:47
- `debug` at line 52 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.debug("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. — pig-auth/src/main/java/com/pig4cloud/pig/auth/support/password/OAuth2ResourceOwnerPasswordAuthenticationProvider.java:52
- `debug` at line 139 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.debug("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. — pig-auth/src/main/java/com/pig4cloud/pig/auth/support/base/OAuth2ResourceOwnerBaseAuthenticationProvider.java:139
What to do
- Interpolated log message defeats structured logging
X5 · Nullable reference types
- 0/126 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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 |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62.2 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 86.7 | Strong | Solid. |
| Maturity | 57.2 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 55.4 | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 56.9 | Adequate — gated by D28, D29, D31 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 43.7 | Weak — gated by AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 6 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 check(s) not relevant to this codebase
- AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
- 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 18 — an image could not be pulled) — pig-codegen Warning context canceled pig-upms Warning context canceled pig-mysql Warning context canceled pig-gateway Warning context canceled pig-quartz Warning context canceled pig-monitor Warning context canceled pig-register Warning context canceled pig-auth Warning context canceled Error response from daemon: Get "https://registry.cn-hangzhou.aliyuncs.com/v2/": Forbidden; the earlier `compose pull` step reported: pig-upms Warning context canceled pig-mysql Warning context canceled pig-gateway Warning context canceled WARNING: Some service image(s) must be built from source by running: docker compose build pig-register pig-auth pig-quartz pig-codegen pig-monitor pig-upms pig-mysql pig-gateway Error response from daemon: Get "https://registry.cn-hangzhou.aliyuncs.com/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; 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.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — a Maven build resolved 359 artifact(s) (238 behind a shipped release, reported), but the build resolved only part of the graph, so this dimension's own question is only partly answered. NOT a finding that these dependencies are current or healthy.
- 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 does not read html yet; 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 — 3 of 6 comment blocks were not judged (3 in a non-Latin script): redundancy is judged by word overlap with the code's identifiers, which cannot be measured across languages.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files).
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no 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 of 3 signals for this style — below the bar we score at): 12 value object(s); 2 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 only 1 of the 3 signals this lens looks for (3 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 3 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (path 1, command argument 2); 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'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a REDACTED, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java was read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 146 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang pig-auth/src/main/resources/templates/ftl/layout/base.ftl:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/activeConnectionStackTrace.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/api.html:2
- <html> without a lang REDACTED:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/datasource.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/index.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/nopermit.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/spring.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/sql.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/wall.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/webapp.html:2
- <html> without a lang pig-visual/pig-monitor/src/main/resources/druid/websession-detail.html:2
- <input> without a programmatic label pig-auth/src/main/resources/templates/ftl/confirm.ftl:32
- <input> without a programmatic label pig-auth/src/main/resources/templates/ftl/login.ftl:21
- <input> without a programmatic label pig-auth/src/main/resources/templates/ftl/login.ftl:26
- <input> without a programmatic label pig-visual/pig-monitor/src/main/resources/druid/login.html:58
- <input> without a programmatic label pig-visual/pig-monitor/src/main/resources/druid/login.html:61
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control pig-auth/src/main/resources/templates/ftl/confirm.ftl:34
- <button> with no accessible text pig-auth/src/main/resources/templates/ftl/layout/base.ftl:38
- <textarea> without a programmatic label pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:23
- Document <title> is empty pig-visual/pig-monitor/src/main/resources/druid/nopermit.html:2
- REDACTED
- Banned license: io.github.pig-mesh.plugin:screw-spring-boot-starter
- REDACTED
- REDACTED
- REDACTED
- Boundary-crossing change coupling: PigTokenEndpoint.java ↔ RemoteTokenService.java pig-auth/src/main/java/com/pig4cloud/pig/auth/endpoint/PigTokenEndpoint.java:1
Serious — 163 finding(s)
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/header.html:2
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:19
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:38
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:39
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:40
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:41
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:42
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:43
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:44
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/spring.html:45
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:19
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:45
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:46
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:47
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:48
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:49
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:50
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:52
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:56
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:57
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:58
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:59
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:60
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:62
- Anchor without href pig-visual/pig-monitor/src/main/resources/druid/sql.html:63
- Page without a main landmark pig-auth/src/main/resources/templates/ftl/layout/base.ftl:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/activeConnectionStackTrace.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/api.html:2
- Page without a main landmark REDACTED:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/datasource.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/index.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/login.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/nopermit.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/spring.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/sql.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/wall.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/webapp.html:2
- Page without a main landmark pig-visual/pig-monitor/src/main/resources/druid/websession-detail.html:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/index.html:19
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/spring-detail.html:21
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:28
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:50
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:64
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:82
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/wall.html:28
- Data table has no header cells pig-visual/pig-monitor/src/main/resources/druid/websession-detail.html:20
- Low cohesion: GlobalBizExceptionHandler (LCOM4 15) pig-common/pig-common-sentinel/src/main/java/com/pig4cloud/pig/common/sentinel/handle/GlobalBizExceptionHandler.java:67
- Low cohesion: WebUtils (LCOM4 5) REDACTED:53
- Low cohesion: SysDeptServiceImpl (LCOM4 5) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysDeptServiceImpl.java:60
- Low cohesion: SysUserServiceImpl (LCOM4 5) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java:76
- Low cohesion: PigTokenEndpoint (LCOM4 4) pig-auth/src/main/java/com/pig4cloud/pig/auth/endpoint/PigTokenEndpoint.java:74
- Focus outline removed inline pig-auth/src/main/resources/templates/ftl/layout/base.ftl:38
- Focus outline removed inline pig-auth/src/main/resources/templates/ftl/login.ftl:21
- Focus outline removed inline pig-auth/src/main/resources/templates/ftl/login.ftl:26
- Focus outline removed inline pig-auth/src/main/resources/templates/ftl/login.ftl:33
- Edited copy of a member (10 corresponding lines) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysPostServiceImpl.java:123
- Edited copy of a member (10 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/cache/RedisUtils.java:318
- Edited copy of a member (10 corresponding lines) pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/converters/LocalDateStringConverter.java:38
- Edited copy of a member (10 corresponding lines) pig-common/pig-common-security/src/main/java/com/pig4cloud/pig/common/security/component/PigCustomOpaqueTokenIntrospector.java:190
- Duplicated block (5 lines × 2) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/resolver/DictResolver.java:70
- Duplicated block (5 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java:147
- Duplicated block (5 lines × 2) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/password/OAuth2ResourceOwnerPasswordAuthenticationProvider.java:50
- Duplicated block (5 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java:674
- Untrusted text written into markup unescaped pig-visual/pig-monitor/src/main/resources/druid/js/common.js:36
- Untrusted text written into markup unescaped pig-visual/pig-monitor/src/main/resources/druid/js/common.js:114
- Untrusted text written into markup unescaped pig-visual/pig-monitor/src/main/resources/druid/js/common.js:126
- Untrusted text written into markup unescaped pig-visual/pig-monitor/src/main/resources/druid/js/lang.js:270
- Change coupling: SysUser.java ↔ UserVO.java pig-upms/pig-upms-api/src/main/java/com/pig4cloud/pig/admin/api/entity/SysUser.java:1
- Change coupling: RemoteUserService.java ↔ SysUserController.java pig-upms/pig-upms-api/src/main/java/com/pig4cloud/pig/admin/api/feign/RemoteUserService.java:1
- Change coupling: SysUserController.java ↔ SysUserServiceImpl.java pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/controller/SysUserController.java:1
- Edited copy of a member (6 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/handler/JsonLongArrayTypeHandler.java:37
- Edited copy of a member (6 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/handler/JsonLongArrayTypeHandler.java:46
- Edited copy of a member (6 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/handler/JsonLongArrayTypeHandler.java:55
- Duplicated block (8 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysMessageServiceImpl.java:357
- Duplicated block (8 lines × 2) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:266
- Duplicated block (8 lines × 2) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/util/JavaClassTaskInvok.java:72
- Swallowed exception (caught, then discarded) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/util/RestTaskUrlValidator.java:77
- Swallowed exception (caught, then discarded) pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/service/impl/GenDatasourceConfServiceImpl.java:202
- Swallowed exception (caught, then discarded) REDACTED:124
- REDACTED
- REDACTED
- Edited copy of a member (20 corresponding lines) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:254
- Edited copy of a member (20 corresponding lines) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/handler/PigAuthenticationSuccessEventHandler.java:135
- Edited copy of a member (11 corresponding lines) pig-upms/pig-upms-api/src/main/java/com/pig4cloud/pig/admin/api/utils/DataUtil.java:43
- Edited copy of a member (11 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/resolver/DictResolver.java:69
- Edited copy of a member (9 corresponding lines) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/support/QuartzProtectionSupport.java:71
- Edited copy of a member (9 corresponding lines) pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/handler/ManySheetWriteHandler.java:38
- Edited copy of a member (7 corresponding lines) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:303
- Edited copy of a member (7 corresponding lines) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/password/OAuth2ResourceOwnerPasswordAuthenticationProvider.java:57
- Duplicated block (12 lines × 2) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:82
- Duplicated block (12 lines × 2) pig-auth/src/main/java/com/pig4cloud/pig/auth/config/AuthorizationServerConfiguration.java:121
- Duplicated block (11 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysDeptServiceImpl.java:115
- Duplicated block (11 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysMessageServiceImpl.java:345
- Duplicated block (7–8 lines × 2) pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/service/impl/GeneratorServiceImpl.java:104
- Duplicated block (7–8 lines × 2) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:71
- <fieldset> without a <legend> pig-visual/pig-monitor/src/main/resources/druid/login.html:53
- Heading level jumps from h3 to h5 pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:21
- Empty <h5> heading pig-visual/pig-monitor/src/main/resources/druid/sql-detail.html:21
- Animation without a prefers-reduced-motion guard pig-auth/src/main/resources/templates/ftl/layout/base.ftl:30
- Stateful singleton: FeignClientEndpoint pig-common/pig-common-feign/src/main/java/com/pig4cloud/pig/common/feign/endpoint/FeignClientEndpoint.java:28
- doT.doT.template (cyclomatic 21) REDACTED:87
- MonitorStatService.service (cyclomatic 20) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:133
- PigCustomOpaqueTokenIntrospector.handleApiKeyToken (cyclomatic 17) pig-common/pig-common-security/src/main/java/com/pig4cloud/pig/common/security/component/PigCustomOpaqueTokenIntrospector.java:118
- PigSentinelInvocationHandler.invoke (cyclomatic 16) pig-common/pig-common-sentinel/src/main/java/com/pig4cloud/pig/common/sentinel/feign/PigSentinelInvocationHandler.java:65
- Repeated repair: pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysUserServiceImpl.java:411
- PigSentinelInvocationHandler.invoke (cognitive 39) pig-common/pig-common-sentinel/src/main/java/com/pig4cloud/pig/common/sentinel/feign/PigSentinelInvocationHandler.java:65
- template (cognitive 21) REDACTED:87
- MonitorStatService.service (cognitive 20) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:133
- resolveDefs (cognitive 20) REDACTED:51
- PigFeignClientsRegistrar.registerFeignClients (cognitive 19) pig-common/pig-common-feign/src/main/java/org/springframework/cloud/openfeign/PigFeignClientsRegistrar.java:68
- PigCustomOpaqueTokenIntrospector.handleApiKeyToken (cognitive 19) pig-common/pig-common-security/src/main/java/com/pig4cloud/pig/common/security/component/PigCustomOpaqueTokenIntrospector.java:118
- FeignClientEndpoint.getClientList (cognitive 18) pig-common/pig-common-feign/src/main/java/com/pig4cloud/pig/common/feign/endpoint/FeignClientEndpoint.java:49
- REDACTED
- REDACTED
- TooManyMethods: RedisUtils pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/cache/RedisUtils.java:22
- REDACTED
- Edited copy of a member (46 corresponding lines) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/util/JavaClassTaskInvok.java:46
- Edited copy of a member (26 corresponding lines) pig-visual/pig-monitor/src/main/java/com/pig4cloud/pig/monitor/service/impl/MonitorStatService.java:70
- Edited copy of a member (33 corresponding lines) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/service/impl/SysJobServiceImpl.java:100
- Edited copy of a member (25 corresponding lines) pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/handler/ManySheetWriteHandler.java:49
- Edited copy of a member (17 corresponding lines) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/handler/DingTalkLoginHandler.java:53
- Edited copy of a member (16 corresponding lines) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/config/PigInitQuartzJob.java:46
- Edited copy of a member (13 corresponding lines) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/core/AuthCaptchaSupport.java:63
- Edited copies of one member (4 members, 17+ corresponding lines) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/handler/DingTalkLoginHandler.java:78
- Edited copy of a member (12 corresponding lines) pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/cache/RedisUtils.java:214
- Edited copy of a member (8 corresponding lines) pig-common/pig-common-sentinel/src/main/java/com/pig4cloud/pig/common/sentinel/handle/GlobalBizExceptionHandler.java:317
- Edited copies of one member (4 members, 8+ corresponding lines) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysDictItemServiceImpl.java:60
- Edited copies of one member (3 members, 10+ corresponding lines) pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/converters/LocalDateStringConverter.java:51
- Duplicated block (10–12 lines × 2) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/core/AuthCaptchaSupport.java:64
- Duplicated block (10–11 lines × 2) pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/service/impl/SysJobServiceImpl.java:124
- Duplicated block (9–10 lines × 2) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/base/OAuth2ResourceOwnerBaseAuthenticationConverter.java:64
- Duplicated block (7 lines × 2) pig-common/pig-common-feign/src/main/java/org/springframework/cloud/openfeign/PigFeignClientsRegistrar.java:161
- Duplicated block (6 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysDeptServiceImpl.java:291
- Duplicated block (9 lines × 2) pig-auth/src/main/java/com/pig4cloud/pig/auth/support/handler/PigAuthenticationSuccessEventHandler.java:143
- Duplicated block (34 lines × 2) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysPostServiceImpl.java:83
- Third-party script without Subresource Integrity pig-auth/src/main/resources/templates/ftl/layout/base.ftl:7
- Branch is unreachable — its condition cannot hold here REDACTED:113
Minor — 128 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file pig-common/pig-common-core/src/main/java/com/pig4cloud/pig/common/core/util/RetOps.java:1
- Orphaned file pig-auth/src/main/java/com/pig4cloud/pig/auth/support/handler/PigAuthenticationSuccessEventHandler.java:1
- Orphaned file pig-auth/src/main/java/com/pig4cloud/pig/auth/support/CustomeOAuth2AccessTokenGenerator.java:1
- Orphaned file pig-gateway/src/main/java/com/pig4cloud/pig/gateway/config/SpringDocConfiguration.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/controller/GenTemplateGroupController.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/controller/GenFieldTypeController.java:1
- Orphaned file pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/controller/SysScheduleController.java:1
- Orphaned file pig-common/pig-common-xss/src/main/java/com/pig4cloud/pig/common/xss/utils/XssUtil.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/service/impl/GenGroupServiceImpl.java:1
- Orphaned file pig-common/pig-common-swagger/src/main/java/com/pig4cloud/pig/common/swagger/config/OpenAPIDefinition.java:1
- Orphaned file pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysScheduleServiceImpl.java:1
- Orphaned file pig-common/pig-common-data/src/main/java/com/pig4cloud/pig/common/data/resolver/DictResolver.java:1
- Orphaned file pig-auth/src/main/java/com/pig4cloud/pig/auth/support/base/OAuth2ResourceOwnerBaseAuthenticationConverter.java:1
- Orphaned file pig-common/pig-common-security/src/main/java/com/pig4cloud/pig/common/security/util/OAuth2EndpointUtils.java:1
- Orphaned file pig-auth/src/main/java/com/pig4cloud/pig/auth/support/password/OAuth2ResourceOwnerPasswordAuthenticationProvider.java:1
- Orphaned file pig-upms/pig-upms-api/src/main/java/com/pig4cloud/pig/admin/api/entity/SysPost.java:1
- Orphaned file pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/ExcelHandlerConfiguration.java:1
- Orphaned file pig-auth/src/main/java/com/pig4cloud/pig/auth/support/sms/OAuth2ResourceOwnerSmsAuthenticationProvider.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/entity/GenFieldType.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/entity/GenTableColumnEntity.java:1
- Orphaned file pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/converters/LocalDateTimeStringConverter.java:1
- Orphaned file pig-visual/pig-codegen/src/main/java/com/pig4cloud/pig/codegen/entity/GenTemplateEntity.java:1
- Orphaned file pig-common/pig-common-oss/src/main/java/com/pig4cloud/pig/common/file/core/FileTemplate.java:1
- Orphaned file pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/impl/SysI18nServiceImpl.java:1
- Orphaned file pig-upms/pig-upms-api/src/main/java/com/pig4cloud/pig/admin/api/utils/DataUtil.java:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate pig-visual/pig-quartz/src/main/java/com/pig4cloud/pig/daemon/quartz/util/JavaClassTaskInvok.java:74
- Duplicated predicate pig-auth/src/main/java/com/pig4cloud/pig/auth/support/base/OAuth2ResourceOwnerBaseAuthenticationConverter.java:65
- Duplicated predicate pig-auth/src/main/java/com/pig4cloud/pig/auth/support/handler/PigAuthenticationSuccessEventHandler.java:146
- Duplicated predicate pig-auth/src/main/java/com/pig4cloud/pig/auth/support/core/AuthCaptchaSupport.java:69
- Duplicated predicate pig-common/pig-common-excel/src/main/java/com/pig4cloud/pig/common/excel/converters/LocalDateStringConverter.java:39
- Duplicated predicate REDACTED:208
- Interpolated log message defeats structured logging pig-common/pig-common-core/src/main/java/com/pig4cloud/pig/common/core/util/SpringContextHolder.java:103
- Interpolated log message defeats structured logging pig-auth/src/main/java/com/pig4cloud/pig/auth/support/sms/OAuth2ResourceOwnerSmsAuthenticationProvider.java:47
- Interpolated log message defeats structured logging pig-auth/src/main/java/com/pig4cloud/pig/auth/support/password/OAuth2ResourceOwnerPasswordAuthenticationProvider.java:52
- Interpolated log message defeats structured logging pig-auth/src/main/java/com/pig4cloud/pig/auth/support/base/OAuth2ResourceOwnerBaseAuthenticationProvider.java:139
- REDACTED
- REDACTED
- Fat interface: SysUserService (19 abstract methods) pig-upms/pig-upms-biz/src/main/java/com/pig4cloud/pig/admin/service/SysUserService.java:41
- Off-boarding risk: anonymized user #1
- No ADRs found REDACTED:193
- REDACTED
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- Logging is not universal
- No SAST REDACTED:6
- No rollback/health safety
- No changelog
- Java packages are not null-marked everywhere
Minor — 2 finding(s)
- Off the main sequence: pig-common-oss
- Off the main sequence: pig-common-sentinel
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-54d13a3388e147b789b1cc9fc21c0935/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-54d13a3388e147b789b1cc9fc21c0935/history-1.json --exit-code 0 --source . | 19 | artifacts/raw/gitleaks-history-1.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-54d13a3388e147b789b1cc9fc21c0935/history-2.json --exit-code 0 --source . | 40 | artifacts/raw/gitleaks-history-2.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=1635" --report-format json --report-path /tmp/watchdog-gitleaks-54d13a3388e147b789b1cc9fc21c0935/history-3.json --exit-code 0 --source . | 109 | artifacts/raw/gitleaks-history-3.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-54d13a3388e147b789b1cc9fc21c0935/tree.json --exit-code 0 --source . | 4 | 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 . | 15 | 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 . | 36 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 40 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |