Executive summary
xiongchun/pangu-framework is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because it has controls that only work with a mouse and images with no text description. It scores 35.9 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 32.2, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is fixing the password or key in the code, worth about 1.6 points. Making the controls keyboard-usable would lift Accessibility itself, also worth about 1.6.
Eighty known security holes in the packages the code depends on can be used by attackers. Sixty-six passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and twenty-eight controls can't be used without a mouse. Replacing each exposed password or key, making the controls work with a keyboard and updating the vulnerable packages would close these risks. Pinning each tool to an exact version would fix the four pipeline tools referenced by a changeable name. The 18 images with no text description need a text description.
The product code is 66,102 lines, about €57,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
Rebuild cost: about €57,000 · Estimate
| Cost to rebuild | €19,000 to €95,000, for 317 to 1,004 hours of work, about 0.4 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 36. 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: 66,102 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 gitee.pulanos.pangu.framework.generator.pojo | 2 gitee.pulanos.pangu.framework.sdk.dto | 3 gitee.pulanos.pangu.framework.sdk.dto.page | 4 gitee.pulanos.pangu.framework.sdk.exception | 5 gitee.pulanos.pangu.framework.starter.base.handler | 6 gitee.pulanos.pangu.showcases.cache.layering.pojo | 7 gitee.pulanos.pangu.showcases.crud.dao.entity | 8 gitee.pulanos.pangu.showcases.dubbo.api.dto | 9 gitee.pulanos.pangu.showcases.dubbo.api.entity | 10 gitee.pulanos.pangu.showcases.dubbo.triple.api | 11 gitee.pulanos.pangu.showcases.seata.api.dto | 12 gitee.pulanos.pangu.showcases.webapi.local.dao.entity | 13 pulanit.pangu.admin.common.domain | 14 pulanit.pangu.admin.system.api.entity | 15 pulanit.pangu.admin.system.dao.mapper | 16 gitee.pulanos.pangu.framework.generator | 17 gitee.pulanos.pangu.framework.generator.utils | 18 gitee.pulanos.pangu.framework.starter.base | 19 gitee.pulanos.pangu.showcases.cache.layering.service | 20 gitee.pulanos.pangu.showcases.crud.dao.mapper | 21 gitee.pulanos.pangu.showcases.dubbo.api.service | 22 gitee.pulanos.pangu.showcases.seata.api.service | 23 gitee.pulanos.pangu.showcases.webapi.local.service | 24 pulanit.pangu.admin.system.api.param | 25 gitee.pulanos.pangu.showcases.crud.service | 26 gitee.pulanos.pangu.showcases.dubbo.consumer.manager | 27 gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service | 28 gitee.pulanos.pangu.showcases.dubbo.provider.service | 29 gitee.pulanos.pangu.showcases.seata.at.service | 30 gitee.pulanos.pangu.showcases.webapi.dubbo.service | 31 gitee.pulanos.pangu.showcases.webapi.local.controller | 32 pulanit.pangu.admin.system.api.service | 33 pulanit.pangu.admin.system.dao.mapper2 | 34 pulanit.pangu.admin.system.manager | 35 gitee.pulanos.pangu.showcases.webapi.dubbo.controller | 36 pulanit.pangu.admin.system.service | 37 pulanit.pangu.admin.web.config | 38 pulanit.pangu.admin.web.controller.home | 39 pulanit.pangu.admin.web.controller.permission | 40 pulanit.pangu.admin.web.log |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 gitee.pulanos.pangu.framework.generator.pojo | ||||||||||||||||||||||||||||||||||||||||
| 2 gitee.pulanos.pangu.framework.sdk.dto | ||||||||||||||||||||||||||||||||||||||||
| 3 gitee.pulanos.pangu.framework.sdk.dto.page | ||||||||||||||||||||||||||||||||||||||||
| 4 gitee.pulanos.pangu.framework.sdk.exception | ||||||||||||||||||||||||||||||||||||||||
| 5 gitee.pulanos.pangu.framework.starter.base.handler | ||||||||||||||||||||||||||||||||||||||||
| 6 gitee.pulanos.pangu.showcases.cache.layering.pojo | ||||||||||||||||||||||||||||||||||||||||
| 7 gitee.pulanos.pangu.showcases.crud.dao.entity | ||||||||||||||||||||||||||||||||||||||||
| 8 gitee.pulanos.pangu.showcases.dubbo.api.dto | ||||||||||||||||||||||||||||||||||||||||
| 9 gitee.pulanos.pangu.showcases.dubbo.api.entity | ||||||||||||||||||||||||||||||||||||||||
| 10 gitee.pulanos.pangu.showcases.dubbo.triple.api | ||||||||||||||||||||||||||||||||||||||||
| 11 gitee.pulanos.pangu.showcases.seata.api.dto | ||||||||||||||||||||||||||||||||||||||||
| 12 gitee.pulanos.pangu.showcases.webapi.local.dao.entity | ||||||||||||||||||||||||||||||||||||||||
| 13 pulanit.pangu.admin.common.domain | ||||||||||||||||||||||||||||||||||||||||
| 14 pulanit.pangu.admin.system.api.entity | ||||||||||||||||||||||||||||||||||||||||
| 15 pulanit.pangu.admin.system.dao.mapper | ||||||||||||||||||||||||||||||||||||||||
| 16 gitee.pulanos.pangu.framework.generator | 6 | |||||||||||||||||||||||||||||||||||||||
| 17 gitee.pulanos.pangu.framework.generator.utils | 2 | |||||||||||||||||||||||||||||||||||||||
| 18 gitee.pulanos.pangu.framework.starter.base | 3 | |||||||||||||||||||||||||||||||||||||||
| 19 gitee.pulanos.pangu.showcases.cache.layering.service | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 gitee.pulanos.pangu.showcases.crud.dao.mapper | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 gitee.pulanos.pangu.showcases.dubbo.api.service | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 gitee.pulanos.pangu.showcases.seata.api.service | 3 | |||||||||||||||||||||||||||||||||||||||
| 23 gitee.pulanos.pangu.showcases.webapi.local.service | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 pulanit.pangu.admin.system.api.param | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 25 gitee.pulanos.pangu.showcases.crud.service | 2 | |||||||||||||||||||||||||||||||||||||||
| 26 gitee.pulanos.pangu.showcases.dubbo.consumer.manager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 gitee.pulanos.pangu.showcases.dubbo.provider.service | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 29 gitee.pulanos.pangu.showcases.seata.at.service | 4 | 6 | ||||||||||||||||||||||||||||||||||||||
| 30 gitee.pulanos.pangu.showcases.webapi.dubbo.service | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 gitee.pulanos.pangu.showcases.webapi.local.controller | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 pulanit.pangu.admin.system.api.service | 2 | 5 | 9 | |||||||||||||||||||||||||||||||||||||
| 33 pulanit.pangu.admin.system.dao.mapper2 | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 pulanit.pangu.admin.system.manager | 4 | 8 | 1 | |||||||||||||||||||||||||||||||||||||
| 35 gitee.pulanos.pangu.showcases.webapi.dubbo.controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 pulanit.pangu.admin.system.service | 2 | 5 | 10 | 9 | 5 | 1 | 4 | |||||||||||||||||||||||||||||||||
| 37 pulanit.pangu.admin.web.config | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 pulanit.pangu.admin.web.controller.home | 1 | 1 | 2 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 pulanit.pangu.admin.web.controller.permission | 4 | 2 | 5 | 7 | 5 | |||||||||||||||||||||||||||||||||||
| 40 pulanit.pangu.admin.web.log | 1 | 2 |
16→1 gitee.pulanos.pangu.framework.generator uses gitee.pulanos.pangu.framework.generator.pojo✕
- Connections
- 6 pairs of types, where a type in gitee.pulanos.pangu.framework.generator uses a type in gitee.pulanos.pangu.framework.generator.pojo.
- The types involved
com.gitee.pulanos.pangu.framework.generator.EntityGenerator→com.gitee.pulanos.pangu.framework.generator.pojo.Columncom.gitee.pulanos.pangu.framework.generator.EntityGenerator→com.gitee.pulanos.pangu.framework.generator.pojo.PluginConfigcom.gitee.pulanos.pangu.framework.generator.EntityGenerator→com.gitee.pulanos.pangu.framework.generator.pojo.Tablecom.gitee.pulanos.pangu.framework.generator.MapperGenerator→com.gitee.pulanos.pangu.framework.generator.pojo.PluginConfigcom.gitee.pulanos.pangu.framework.generator.MapperGenerator→com.gitee.pulanos.pangu.framework.generator.pojo.Tablecom.gitee.pulanos.pangu.framework.generator.PanGuGeneratorMojo→com.gitee.pulanos.pangu.framework.generator.pojo.PluginConfig
- Direction
- gitee.pulanos.pangu.framework.generator uses gitee.pulanos.pangu.framework.generator.pojo, so a change to gitee.pulanos.pangu.framework.generator.pojo can break gitee.pulanos.pangu.framework.generator, while a change to gitee.pulanos.pangu.framework.generator can't break gitee.pulanos.pangu.framework.generator.pojo.
- Position
- Below the diagonal: gitee.pulanos.pangu.framework.generator uses a module listed above it, which is the healthy direction.
17→1 gitee.pulanos.pangu.framework.generator.utils uses gitee.pulanos.pangu.framework.generator.pojo✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.framework.generator.utils uses a type in gitee.pulanos.pangu.framework.generator.pojo.
- The types involved
com.gitee.pulanos.pangu.framework.generator.utils.DbMetaInfoUtil→com.gitee.pulanos.pangu.framework.generator.pojo.Columncom.gitee.pulanos.pangu.framework.generator.utils.DbMetaInfoUtil→com.gitee.pulanos.pangu.framework.generator.pojo.Table
- Direction
- gitee.pulanos.pangu.framework.generator.utils uses gitee.pulanos.pangu.framework.generator.pojo, so a change to gitee.pulanos.pangu.framework.generator.pojo can break gitee.pulanos.pangu.framework.generator.utils, while a change to gitee.pulanos.pangu.framework.generator.utils can't break gitee.pulanos.pangu.framework.generator.pojo.
- Position
- Below the diagonal: gitee.pulanos.pangu.framework.generator.utils uses a module listed above it, which is the healthy direction.
18→5 gitee.pulanos.pangu.framework.starter.base uses gitee.pulanos.pangu.framework.starter.base.handler✕
- Connections
- 3 pairs of types, where a type in gitee.pulanos.pangu.framework.starter.base uses a type in gitee.pulanos.pangu.framework.starter.base.handler.
- The types involved
com.gitee.pulanos.pangu.framework.starter.base.BaseAutoConfiguration→com.gitee.pulanos.pangu.framework.starter.base.handler.ApplicationReadyEventListenercom.gitee.pulanos.pangu.framework.starter.base.BaseAutoConfiguration→com.gitee.pulanos.pangu.framework.starter.base.handler.AvailabilityChangeEventListenercom.gitee.pulanos.pangu.framework.starter.base.BaseAutoConfiguration→com.gitee.pulanos.pangu.framework.starter.base.handler.LogLevelChangeEventListener
- Direction
- gitee.pulanos.pangu.framework.starter.base uses gitee.pulanos.pangu.framework.starter.base.handler, so a change to gitee.pulanos.pangu.framework.starter.base.handler can break gitee.pulanos.pangu.framework.starter.base, while a change to gitee.pulanos.pangu.framework.starter.base can't break gitee.pulanos.pangu.framework.starter.base.handler.
- Position
- Below the diagonal: gitee.pulanos.pangu.framework.starter.base uses a module listed above it, which is the healthy direction.
19→6 gitee.pulanos.pangu.showcases.cache.layering.service uses gitee.pulanos.pangu.showcases.cache.layering.pojo✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.cache.layering.service uses a type in gitee.pulanos.pangu.showcases.cache.layering.pojo.
- The types involved
com.gitee.pulanos.pangu.showcases.cache.layering.service.AnnotationBasedDemoService→com.gitee.pulanos.pangu.showcases.cache.layering.pojo.UserVO
- Direction
- gitee.pulanos.pangu.showcases.cache.layering.service uses gitee.pulanos.pangu.showcases.cache.layering.pojo, so a change to gitee.pulanos.pangu.showcases.cache.layering.pojo can break gitee.pulanos.pangu.showcases.cache.layering.service, while a change to gitee.pulanos.pangu.showcases.cache.layering.service can't break gitee.pulanos.pangu.showcases.cache.layering.pojo.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.cache.layering.service uses a module listed above it, which is the healthy direction.
20→7 gitee.pulanos.pangu.showcases.crud.dao.mapper uses gitee.pulanos.pangu.showcases.crud.dao.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.crud.dao.mapper uses a type in gitee.pulanos.pangu.showcases.crud.dao.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.crud.dao.mapper.CrudMapper→com.gitee.pulanos.pangu.showcases.crud.dao.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.crud.dao.mapper uses gitee.pulanos.pangu.showcases.crud.dao.entity, so a change to gitee.pulanos.pangu.showcases.crud.dao.entity can break gitee.pulanos.pangu.showcases.crud.dao.mapper, while a change to gitee.pulanos.pangu.showcases.crud.dao.mapper can't break gitee.pulanos.pangu.showcases.crud.dao.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.crud.dao.mapper uses a module listed above it, which is the healthy direction.
21→8 gitee.pulanos.pangu.showcases.dubbo.api.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.showcases.dubbo.api.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserInDtocom.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserOutDto
- Direction
- gitee.pulanos.pangu.showcases.dubbo.api.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.dubbo.api.service, while a change to gitee.pulanos.pangu.showcases.dubbo.api.service can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.api.service uses a module listed above it, which is the healthy direction.
21→9 gitee.pulanos.pangu.showcases.dubbo.api.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.api.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService→com.gitee.pulanos.pangu.showcases.dubbo.api.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.dubbo.api.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity, so a change to gitee.pulanos.pangu.showcases.dubbo.api.entity can break gitee.pulanos.pangu.showcases.dubbo.api.service, while a change to gitee.pulanos.pangu.showcases.dubbo.api.service can't break gitee.pulanos.pangu.showcases.dubbo.api.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.api.service uses a module listed above it, which is the healthy direction.
22→11 gitee.pulanos.pangu.showcases.seata.api.service uses gitee.pulanos.pangu.showcases.seata.api.dto✕
- Connections
- 3 pairs of types, where a type in gitee.pulanos.pangu.showcases.seata.api.service uses a type in gitee.pulanos.pangu.showcases.seata.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.seata.api.service.AccountService→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDtocom.gitee.pulanos.pangu.showcases.seata.api.service.OrderService→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDtocom.gitee.pulanos.pangu.showcases.seata.api.service.StockService→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDto
- Direction
- gitee.pulanos.pangu.showcases.seata.api.service uses gitee.pulanos.pangu.showcases.seata.api.dto, so a change to gitee.pulanos.pangu.showcases.seata.api.dto can break gitee.pulanos.pangu.showcases.seata.api.service, while a change to gitee.pulanos.pangu.showcases.seata.api.service can't break gitee.pulanos.pangu.showcases.seata.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.seata.api.service uses a module listed above it, which is the healthy direction.
23→12 gitee.pulanos.pangu.showcases.webapi.local.service uses gitee.pulanos.pangu.showcases.webapi.local.dao.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.local.service uses a type in gitee.pulanos.pangu.showcases.webapi.local.dao.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.local.service.DemoService→com.gitee.pulanos.pangu.showcases.webapi.local.dao.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.webapi.local.service uses gitee.pulanos.pangu.showcases.webapi.local.dao.entity, so a change to gitee.pulanos.pangu.showcases.webapi.local.dao.entity can break gitee.pulanos.pangu.showcases.webapi.local.service, while a change to gitee.pulanos.pangu.showcases.webapi.local.service can't break gitee.pulanos.pangu.showcases.webapi.local.dao.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.local.service uses a module listed above it, which is the healthy direction.
24→3 pulanit.pangu.admin.system.api.param uses gitee.pulanos.pangu.framework.sdk.dto.page✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.system.api.param uses a type in gitee.pulanos.pangu.framework.sdk.dto.page.
- The types involved
com.pulanit.pangu.admin.system.api.param.RoleIn→com.gitee.pulanos.pangu.framework.sdk.dto.page.Pagecom.pulanit.pangu.admin.system.api.param.UserPageIn→com.gitee.pulanos.pangu.framework.sdk.dto.page.Page
- Direction
- pulanit.pangu.admin.system.api.param uses gitee.pulanos.pangu.framework.sdk.dto.page, so a change to gitee.pulanos.pangu.framework.sdk.dto.page can break pulanit.pangu.admin.system.api.param, while a change to pulanit.pangu.admin.system.api.param can't break gitee.pulanos.pangu.framework.sdk.dto.page.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.param uses a module listed above it, which is the healthy direction.
24→13 pulanit.pangu.admin.system.api.param uses pulanit.pangu.admin.common.domain✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.api.param uses a type in pulanit.pangu.admin.common.domain.
- The types involved
com.pulanit.pangu.admin.system.api.param.LoginOut→com.pulanit.pangu.admin.common.domain.UserInfo
- Direction
- pulanit.pangu.admin.system.api.param uses pulanit.pangu.admin.common.domain, so a change to pulanit.pangu.admin.common.domain can break pulanit.pangu.admin.system.api.param, while a change to pulanit.pangu.admin.system.api.param can't break pulanit.pangu.admin.common.domain.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.param uses a module listed above it, which is the healthy direction.
24→14 pulanit.pangu.admin.system.api.param uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.api.param uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.system.api.param.UserOut→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.system.api.param uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.system.api.param, while a change to pulanit.pangu.admin.system.api.param can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.param uses a module listed above it, which is the healthy direction.
25→20 gitee.pulanos.pangu.showcases.crud.service uses gitee.pulanos.pangu.showcases.crud.dao.mapper✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.showcases.crud.service uses a type in gitee.pulanos.pangu.showcases.crud.dao.mapper.
- The types involved
com.gitee.pulanos.pangu.showcases.crud.service.CrudService→com.gitee.pulanos.pangu.showcases.crud.dao.mapper.CrudMappercom.gitee.pulanos.pangu.showcases.crud.service.CrudService→com.gitee.pulanos.pangu.showcases.crud.dao.mapper.UserMapper
- Direction
- gitee.pulanos.pangu.showcases.crud.service uses gitee.pulanos.pangu.showcases.crud.dao.mapper, so a change to gitee.pulanos.pangu.showcases.crud.dao.mapper can break gitee.pulanos.pangu.showcases.crud.service, while a change to gitee.pulanos.pangu.showcases.crud.service can't break gitee.pulanos.pangu.showcases.crud.dao.mapper.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.crud.service uses a module listed above it, which is the healthy direction.
26→8 gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.consumer.manager.UserAdminManager→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserInDto
- Direction
- gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.dubbo.consumer.manager, while a change to gitee.pulanos.pangu.showcases.dubbo.consumer.manager can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses a module listed above it, which is the healthy direction.
26→21 gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses gitee.pulanos.pangu.showcases.dubbo.api.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses a type in gitee.pulanos.pangu.showcases.dubbo.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.consumer.manager.UserAdminManager→com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService
- Direction
- gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses gitee.pulanos.pangu.showcases.dubbo.api.service, so a change to gitee.pulanos.pangu.showcases.dubbo.api.service can break gitee.pulanos.pangu.showcases.dubbo.consumer.manager, while a change to gitee.pulanos.pangu.showcases.dubbo.consumer.manager can't break gitee.pulanos.pangu.showcases.dubbo.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.consumer.manager uses a module listed above it, which is the healthy direction.
27→8 gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserInDtocom.gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserOutDto
- Direction
- gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a module listed above it, which is the healthy direction.
27→9 gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity, so a change to gitee.pulanos.pangu.showcases.dubbo.api.entity can break gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a module listed above it, which is the healthy direction.
27→21 gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService
- Direction
- gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.service, so a change to gitee.pulanos.pangu.showcases.dubbo.api.service can break gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.gateway.provider.service uses a module listed above it, which is the healthy direction.
28→8 gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.showcases.dubbo.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserInDtocom.gitee.pulanos.pangu.showcases.dubbo.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserOutDto
- Direction
- gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.dubbo.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.provider.service uses a module listed above it, which is the healthy direction.
28→9 gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.entity, so a change to gitee.pulanos.pangu.showcases.dubbo.api.entity can break gitee.pulanos.pangu.showcases.dubbo.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.provider.service uses a module listed above it, which is the healthy direction.
28→21 gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.dubbo.provider.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.dubbo.provider.service.UserServiceImpl→com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService
- Direction
- gitee.pulanos.pangu.showcases.dubbo.provider.service uses gitee.pulanos.pangu.showcases.dubbo.api.service, so a change to gitee.pulanos.pangu.showcases.dubbo.api.service can break gitee.pulanos.pangu.showcases.dubbo.provider.service, while a change to gitee.pulanos.pangu.showcases.dubbo.provider.service can't break gitee.pulanos.pangu.showcases.dubbo.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.dubbo.provider.service uses a module listed above it, which is the healthy direction.
29→11 gitee.pulanos.pangu.showcases.seata.at.service uses gitee.pulanos.pangu.showcases.seata.api.dto✕
- Connections
- 4 pairs of types, where a type in gitee.pulanos.pangu.showcases.seata.at.service uses a type in gitee.pulanos.pangu.showcases.seata.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.seata.at.service.AccountServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDtocom.gitee.pulanos.pangu.showcases.seata.at.service.MainBizService→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDtocom.gitee.pulanos.pangu.showcases.seata.at.service.OrderServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDtocom.gitee.pulanos.pangu.showcases.seata.at.service.StockServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.dto.BuyDto
- Direction
- gitee.pulanos.pangu.showcases.seata.at.service uses gitee.pulanos.pangu.showcases.seata.api.dto, so a change to gitee.pulanos.pangu.showcases.seata.api.dto can break gitee.pulanos.pangu.showcases.seata.at.service, while a change to gitee.pulanos.pangu.showcases.seata.at.service can't break gitee.pulanos.pangu.showcases.seata.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.seata.at.service uses a module listed above it, which is the healthy direction.
29→22 gitee.pulanos.pangu.showcases.seata.at.service uses gitee.pulanos.pangu.showcases.seata.api.service✕
- Connections
- 6 pairs of types, where a type in gitee.pulanos.pangu.showcases.seata.at.service uses a type in gitee.pulanos.pangu.showcases.seata.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.seata.at.service.AccountServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.service.AccountServicecom.gitee.pulanos.pangu.showcases.seata.at.service.MainBizService→com.gitee.pulanos.pangu.showcases.seata.api.service.AccountServicecom.gitee.pulanos.pangu.showcases.seata.at.service.MainBizService→com.gitee.pulanos.pangu.showcases.seata.api.service.OrderServicecom.gitee.pulanos.pangu.showcases.seata.at.service.MainBizService→com.gitee.pulanos.pangu.showcases.seata.api.service.StockServicecom.gitee.pulanos.pangu.showcases.seata.at.service.OrderServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.service.OrderServicecom.gitee.pulanos.pangu.showcases.seata.at.service.StockServiceImpl→com.gitee.pulanos.pangu.showcases.seata.api.service.StockService
- Direction
- gitee.pulanos.pangu.showcases.seata.at.service uses gitee.pulanos.pangu.showcases.seata.api.service, so a change to gitee.pulanos.pangu.showcases.seata.api.service can break gitee.pulanos.pangu.showcases.seata.at.service, while a change to gitee.pulanos.pangu.showcases.seata.at.service can't break gitee.pulanos.pangu.showcases.seata.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.seata.at.service uses a module listed above it, which is the healthy direction.
30→8 gitee.pulanos.pangu.showcases.webapi.dubbo.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 2 pairs of types, where a type in gitee.pulanos.pangu.showcases.webapi.dubbo.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.dubbo.service.DemoService→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserInDtocom.gitee.pulanos.pangu.showcases.webapi.dubbo.service.DemoService→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserOutDto
- Direction
- gitee.pulanos.pangu.showcases.webapi.dubbo.service uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.webapi.dubbo.service, while a change to gitee.pulanos.pangu.showcases.webapi.dubbo.service can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.dubbo.service uses a module listed above it, which is the healthy direction.
30→21 gitee.pulanos.pangu.showcases.webapi.dubbo.service uses gitee.pulanos.pangu.showcases.dubbo.api.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.dubbo.service uses a type in gitee.pulanos.pangu.showcases.dubbo.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.dubbo.service.DemoService→com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService
- Direction
- gitee.pulanos.pangu.showcases.webapi.dubbo.service uses gitee.pulanos.pangu.showcases.dubbo.api.service, so a change to gitee.pulanos.pangu.showcases.dubbo.api.service can break gitee.pulanos.pangu.showcases.webapi.dubbo.service, while a change to gitee.pulanos.pangu.showcases.webapi.dubbo.service can't break gitee.pulanos.pangu.showcases.dubbo.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.dubbo.service uses a module listed above it, which is the healthy direction.
31→12 gitee.pulanos.pangu.showcases.webapi.local.controller uses gitee.pulanos.pangu.showcases.webapi.local.dao.entity✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.local.controller uses a type in gitee.pulanos.pangu.showcases.webapi.local.dao.entity.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.local.controller.DemoController→com.gitee.pulanos.pangu.showcases.webapi.local.dao.entity.UserEntity
- Direction
- gitee.pulanos.pangu.showcases.webapi.local.controller uses gitee.pulanos.pangu.showcases.webapi.local.dao.entity, so a change to gitee.pulanos.pangu.showcases.webapi.local.dao.entity can break gitee.pulanos.pangu.showcases.webapi.local.controller, while a change to gitee.pulanos.pangu.showcases.webapi.local.controller can't break gitee.pulanos.pangu.showcases.webapi.local.dao.entity.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.local.controller uses a module listed above it, which is the healthy direction.
31→23 gitee.pulanos.pangu.showcases.webapi.local.controller uses gitee.pulanos.pangu.showcases.webapi.local.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.local.controller uses a type in gitee.pulanos.pangu.showcases.webapi.local.service.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.local.controller.DemoController→com.gitee.pulanos.pangu.showcases.webapi.local.service.DemoService
- Direction
- gitee.pulanos.pangu.showcases.webapi.local.controller uses gitee.pulanos.pangu.showcases.webapi.local.service, so a change to gitee.pulanos.pangu.showcases.webapi.local.service can break gitee.pulanos.pangu.showcases.webapi.local.controller, while a change to gitee.pulanos.pangu.showcases.webapi.local.controller can't break gitee.pulanos.pangu.showcases.webapi.local.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.local.controller uses a module listed above it, which is the healthy direction.
32→3 pulanit.pangu.admin.system.api.service uses gitee.pulanos.pangu.framework.sdk.dto.page✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.system.api.service uses a type in gitee.pulanos.pangu.framework.sdk.dto.page.
- The types involved
com.pulanit.pangu.admin.system.api.service.RoleService→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResultcom.pulanit.pangu.admin.system.api.service.UserService→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResult
- Direction
- pulanit.pangu.admin.system.api.service uses gitee.pulanos.pangu.framework.sdk.dto.page, so a change to gitee.pulanos.pangu.framework.sdk.dto.page can break pulanit.pangu.admin.system.api.service, while a change to pulanit.pangu.admin.system.api.service can't break gitee.pulanos.pangu.framework.sdk.dto.page.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.service uses a module listed above it, which is the healthy direction.
32→14 pulanit.pangu.admin.system.api.service uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 5 pairs of types, where a type in pulanit.pangu.admin.system.api.service uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.system.api.service.DeptService→com.pulanit.pangu.admin.system.api.entity.DeptEntitycom.pulanit.pangu.admin.system.api.service.ResourceService→com.pulanit.pangu.admin.system.api.entity.ResourceEntitycom.pulanit.pangu.admin.system.api.service.RoleService→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.system.api.service uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.system.api.service, while a change to pulanit.pangu.admin.system.api.service can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.service uses a module listed above it, which is the healthy direction.
32→24 pulanit.pangu.admin.system.api.service uses pulanit.pangu.admin.system.api.param✕
- Connections
- 9 pairs of types, where a type in pulanit.pangu.admin.system.api.service uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.system.api.service.DeptService→com.pulanit.pangu.admin.system.api.param.DeptIncom.pulanit.pangu.admin.system.api.service.LogService→com.pulanit.pangu.admin.system.api.param.LogIncom.pulanit.pangu.admin.system.api.service.ResourceService→com.pulanit.pangu.admin.system.api.param.ResourceForLoginOutcom.pulanit.pangu.admin.system.api.service.ResourceService→com.pulanit.pangu.admin.system.api.param.ResourceOutcom.pulanit.pangu.admin.system.api.service.RoleService→com.pulanit.pangu.admin.system.api.param.RoleIncom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.param.LoginIncom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.param.LoginOutcom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.param.UserOutcom.pulanit.pangu.admin.system.api.service.UserService→com.pulanit.pangu.admin.system.api.param.UserPageIn
- Direction
- pulanit.pangu.admin.system.api.service uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.system.api.service, while a change to pulanit.pangu.admin.system.api.service can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.system.api.service uses a module listed above it, which is the healthy direction.
33→14 pulanit.pangu.admin.system.dao.mapper2 uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.dao.mapper2 uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.system.dao.mapper2.CommonMapper→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.system.dao.mapper2 uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.system.dao.mapper2, while a change to pulanit.pangu.admin.system.dao.mapper2 can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.system.dao.mapper2 uses a module listed above it, which is the healthy direction.
33→24 pulanit.pangu.admin.system.dao.mapper2 uses pulanit.pangu.admin.system.api.param✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.dao.mapper2 uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.system.dao.mapper2.CommonMapper→com.pulanit.pangu.admin.system.api.param.UserPageIn
- Direction
- pulanit.pangu.admin.system.dao.mapper2 uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.system.dao.mapper2, while a change to pulanit.pangu.admin.system.dao.mapper2 can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.system.dao.mapper2 uses a module listed above it, which is the healthy direction.
34→14 pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 4 pairs of types, where a type in pulanit.pangu.admin.system.manager uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.system.manager.DeptManager→com.pulanit.pangu.admin.system.api.entity.DeptEntitycom.pulanit.pangu.admin.system.manager.ResourceManager→com.pulanit.pangu.admin.system.api.entity.ResourceEntitycom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.system.manager, while a change to pulanit.pangu.admin.system.manager can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.system.manager uses a module listed above it, which is the healthy direction.
34→15 pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.dao.mapper✕
- Connections
- 8 pairs of types, where a type in pulanit.pangu.admin.system.manager uses a type in pulanit.pangu.admin.system.dao.mapper.
- The types involved
com.pulanit.pangu.admin.system.manager.DeptManager→com.pulanit.pangu.admin.system.dao.mapper.DeptMappercom.pulanit.pangu.admin.system.manager.ResourceManager→com.pulanit.pangu.admin.system.dao.mapper.ResourceMappercom.pulanit.pangu.admin.system.manager.ResourceManager→com.pulanit.pangu.admin.system.dao.mapper.RoleResourceMappercom.pulanit.pangu.admin.system.manager.ResourceManager→com.pulanit.pangu.admin.system.dao.mapper.UserRoleMappercom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.dao.mapper.DeptMappercom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.dao.mapper.RoleMappercom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.dao.mapper.UserMappercom.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.dao.mapper.UserRoleMapper
- Direction
- pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.dao.mapper, so a change to pulanit.pangu.admin.system.dao.mapper can break pulanit.pangu.admin.system.manager, while a change to pulanit.pangu.admin.system.manager can't break pulanit.pangu.admin.system.dao.mapper.
- Position
- Below the diagonal: pulanit.pangu.admin.system.manager uses a module listed above it, which is the healthy direction.
34→24 pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.api.param✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.manager uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.system.manager.UserManager→com.pulanit.pangu.admin.system.api.param.UserOut
- Direction
- pulanit.pangu.admin.system.manager uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.system.manager, while a change to pulanit.pangu.admin.system.manager can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.system.manager uses a module listed above it, which is the healthy direction.
35→8 gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.dubbo.api.dto✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a type in gitee.pulanos.pangu.showcases.dubbo.api.dto.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.dubbo.controller.DemoController→com.gitee.pulanos.pangu.showcases.dubbo.api.dto.UserOutDto
- Direction
- gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.dubbo.api.dto, so a change to gitee.pulanos.pangu.showcases.dubbo.api.dto can break gitee.pulanos.pangu.showcases.webapi.dubbo.controller, while a change to gitee.pulanos.pangu.showcases.webapi.dubbo.controller can't break gitee.pulanos.pangu.showcases.dubbo.api.dto.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a module listed above it, which is the healthy direction.
35→21 gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.dubbo.api.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a type in gitee.pulanos.pangu.showcases.dubbo.api.service.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.dubbo.controller.DemoController→com.gitee.pulanos.pangu.showcases.dubbo.api.service.UserService
- Direction
- gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.dubbo.api.service, so a change to gitee.pulanos.pangu.showcases.dubbo.api.service can break gitee.pulanos.pangu.showcases.webapi.dubbo.controller, while a change to gitee.pulanos.pangu.showcases.webapi.dubbo.controller can't break gitee.pulanos.pangu.showcases.dubbo.api.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a module listed above it, which is the healthy direction.
35→30 gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.webapi.dubbo.service✕
- Connections
- 1 pair of types, where a type in gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a type in gitee.pulanos.pangu.showcases.webapi.dubbo.service.
- The types involved
com.gitee.pulanos.pangu.showcases.webapi.dubbo.controller.DemoController→com.gitee.pulanos.pangu.showcases.webapi.dubbo.service.DemoService
- Direction
- gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses gitee.pulanos.pangu.showcases.webapi.dubbo.service, so a change to gitee.pulanos.pangu.showcases.webapi.dubbo.service can break gitee.pulanos.pangu.showcases.webapi.dubbo.controller, while a change to gitee.pulanos.pangu.showcases.webapi.dubbo.controller can't break gitee.pulanos.pangu.showcases.webapi.dubbo.service.
- Position
- Below the diagonal: gitee.pulanos.pangu.showcases.webapi.dubbo.controller uses a module listed above it, which is the healthy direction.
36→3 pulanit.pangu.admin.system.service uses gitee.pulanos.pangu.framework.sdk.dto.page✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in gitee.pulanos.pangu.framework.sdk.dto.page.
- The types involved
com.pulanit.pangu.admin.system.service.RoleServiceImpl→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResultcom.pulanit.pangu.admin.system.service.UserServiceImpl→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResult
- Direction
- pulanit.pangu.admin.system.service uses gitee.pulanos.pangu.framework.sdk.dto.page, so a change to gitee.pulanos.pangu.framework.sdk.dto.page can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break gitee.pulanos.pangu.framework.sdk.dto.page.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→14 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 5 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.system.service.DeptServiceImpl→com.pulanit.pangu.admin.system.api.entity.DeptEntitycom.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.api.entity.ResourceEntitycom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→15 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.dao.mapper✕
- Connections
- 10 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.dao.mapper.
- The types involved
com.pulanit.pangu.admin.system.service.DeptServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.DeptMappercom.pulanit.pangu.admin.system.service.LogServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.LogFailMappercom.pulanit.pangu.admin.system.service.LogServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.LogSuccessMappercom.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.ResourceMappercom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.RoleMappercom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.RoleResourceMappercom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.UserRoleMappercom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.RoleMappercom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.UserMappercom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.dao.mapper.UserRoleMapper
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.dao.mapper, so a change to pulanit.pangu.admin.system.dao.mapper can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.dao.mapper.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→24 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.param✕
- Connections
- 9 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.system.service.DeptServiceImpl→com.pulanit.pangu.admin.system.api.param.DeptIncom.pulanit.pangu.admin.system.service.LogServiceImpl→com.pulanit.pangu.admin.system.api.param.LogIncom.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.api.param.ResourceForLoginOutcom.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.api.param.ResourceOutcom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.api.param.RoleIncom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.param.LoginIncom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.param.LoginOutcom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.param.UserOutcom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.param.UserPageIn
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→32 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.service✕
- Connections
- 5 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.api.service.
- The types involved
com.pulanit.pangu.admin.system.service.DeptServiceImpl→com.pulanit.pangu.admin.system.api.service.DeptServicecom.pulanit.pangu.admin.system.service.LogServiceImpl→com.pulanit.pangu.admin.system.api.service.LogServicecom.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.api.service.ResourceServicecom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.api.service.RoleServicecom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.api.service.UserService
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.api.service, so a change to pulanit.pangu.admin.system.api.service can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.api.service.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→33 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.dao.mapper2✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.dao.mapper2.
- The types involved
com.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.dao.mapper2.CommonMapper
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.dao.mapper2, so a change to pulanit.pangu.admin.system.dao.mapper2 can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.dao.mapper2.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
36→34 pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.manager✕
- Connections
- 4 pairs of types, where a type in pulanit.pangu.admin.system.service uses a type in pulanit.pangu.admin.system.manager.
- The types involved
com.pulanit.pangu.admin.system.service.ResourceServiceImpl→com.pulanit.pangu.admin.system.manager.ResourceManagercom.pulanit.pangu.admin.system.service.RoleServiceImpl→com.pulanit.pangu.admin.system.manager.UserManagercom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.manager.DeptManagercom.pulanit.pangu.admin.system.service.UserServiceImpl→com.pulanit.pangu.admin.system.manager.UserManager
- Direction
- pulanit.pangu.admin.system.service uses pulanit.pangu.admin.system.manager, so a change to pulanit.pangu.admin.system.manager can break pulanit.pangu.admin.system.service, while a change to pulanit.pangu.admin.system.service can't break pulanit.pangu.admin.system.manager.
- Position
- Below the diagonal: pulanit.pangu.admin.system.service uses a module listed above it, which is the healthy direction.
37→2 pulanit.pangu.admin.web.config uses gitee.pulanos.pangu.framework.sdk.dto✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.config uses a type in gitee.pulanos.pangu.framework.sdk.dto.
- The types involved
com.pulanit.pangu.admin.web.config.GlobalExceptionHandler→com.gitee.pulanos.pangu.framework.sdk.dto.Result
- Direction
- pulanit.pangu.admin.web.config uses gitee.pulanos.pangu.framework.sdk.dto, so a change to gitee.pulanos.pangu.framework.sdk.dto can break pulanit.pangu.admin.web.config, while a change to pulanit.pangu.admin.web.config can't break gitee.pulanos.pangu.framework.sdk.dto.
- Position
- Below the diagonal: pulanit.pangu.admin.web.config uses a module listed above it, which is the healthy direction.
37→4 pulanit.pangu.admin.web.config uses gitee.pulanos.pangu.framework.sdk.exception✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.config uses a type in gitee.pulanos.pangu.framework.sdk.exception.
- The types involved
com.pulanit.pangu.admin.web.config.GlobalExceptionHandler→com.gitee.pulanos.pangu.framework.sdk.exception.BizException
- Direction
- pulanit.pangu.admin.web.config uses gitee.pulanos.pangu.framework.sdk.exception, so a change to gitee.pulanos.pangu.framework.sdk.exception can break pulanit.pangu.admin.web.config, while a change to pulanit.pangu.admin.web.config can't break gitee.pulanos.pangu.framework.sdk.exception.
- Position
- Below the diagonal: pulanit.pangu.admin.web.config uses a module listed above it, which is the healthy direction.
37→24 pulanit.pangu.admin.web.config uses pulanit.pangu.admin.system.api.param✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.config uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.web.config.ControllerLogAspect→com.pulanit.pangu.admin.system.api.param.LogIn
- Direction
- pulanit.pangu.admin.web.config uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.web.config, while a change to pulanit.pangu.admin.web.config can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.web.config uses a module listed above it, which is the healthy direction.
37→32 pulanit.pangu.admin.web.config uses pulanit.pangu.admin.system.api.service✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.config uses a type in pulanit.pangu.admin.system.api.service.
- The types involved
com.pulanit.pangu.admin.web.config.GlobalExceptionHandler→com.pulanit.pangu.admin.system.api.service.LogService
- Direction
- pulanit.pangu.admin.web.config uses pulanit.pangu.admin.system.api.service, so a change to pulanit.pangu.admin.system.api.service can break pulanit.pangu.admin.web.config, while a change to pulanit.pangu.admin.web.config can't break pulanit.pangu.admin.system.api.service.
- Position
- Below the diagonal: pulanit.pangu.admin.web.config uses a module listed above it, which is the healthy direction.
38→2 pulanit.pangu.admin.web.controller.home uses gitee.pulanos.pangu.framework.sdk.dto✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.controller.home uses a type in gitee.pulanos.pangu.framework.sdk.dto.
- The types involved
com.pulanit.pangu.admin.web.controller.home.LoginController→com.gitee.pulanos.pangu.framework.sdk.dto.Result
- Direction
- pulanit.pangu.admin.web.controller.home uses gitee.pulanos.pangu.framework.sdk.dto, so a change to gitee.pulanos.pangu.framework.sdk.dto can break pulanit.pangu.admin.web.controller.home, while a change to pulanit.pangu.admin.web.controller.home can't break gitee.pulanos.pangu.framework.sdk.dto.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.home uses a module listed above it, which is the healthy direction.
38→13 pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.common.domain✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.controller.home uses a type in pulanit.pangu.admin.common.domain.
- The types involved
com.pulanit.pangu.admin.web.controller.home.LoginController→com.pulanit.pangu.admin.common.domain.UserInfo
- Direction
- pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.common.domain, so a change to pulanit.pangu.admin.common.domain can break pulanit.pangu.admin.web.controller.home, while a change to pulanit.pangu.admin.web.controller.home can't break pulanit.pangu.admin.common.domain.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.home uses a module listed above it, which is the healthy direction.
38→24 pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.system.api.param✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.web.controller.home uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.web.controller.home.LoginController→com.pulanit.pangu.admin.system.api.param.LoginIncom.pulanit.pangu.admin.web.controller.home.LoginController→com.pulanit.pangu.admin.system.api.param.LoginOut
- Direction
- pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.web.controller.home, while a change to pulanit.pangu.admin.web.controller.home can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.home uses a module listed above it, which is the healthy direction.
38→32 pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.system.api.service✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.controller.home uses a type in pulanit.pangu.admin.system.api.service.
- The types involved
com.pulanit.pangu.admin.web.controller.home.LoginController→com.pulanit.pangu.admin.system.api.service.UserService
- Direction
- pulanit.pangu.admin.web.controller.home uses pulanit.pangu.admin.system.api.service, so a change to pulanit.pangu.admin.system.api.service can break pulanit.pangu.admin.web.controller.home, while a change to pulanit.pangu.admin.web.controller.home can't break pulanit.pangu.admin.system.api.service.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.home uses a module listed above it, which is the healthy direction.
39→2 pulanit.pangu.admin.web.controller.permission uses gitee.pulanos.pangu.framework.sdk.dto✕
- Connections
- 4 pairs of types, where a type in pulanit.pangu.admin.web.controller.permission uses a type in gitee.pulanos.pangu.framework.sdk.dto.
- The types involved
com.pulanit.pangu.admin.web.controller.permission.DeptController→com.gitee.pulanos.pangu.framework.sdk.dto.Resultcom.pulanit.pangu.admin.web.controller.permission.ResourceController→com.gitee.pulanos.pangu.framework.sdk.dto.Resultcom.pulanit.pangu.admin.web.controller.permission.RoleController→com.gitee.pulanos.pangu.framework.sdk.dto.Resultcom.pulanit.pangu.admin.web.controller.permission.UserController→com.gitee.pulanos.pangu.framework.sdk.dto.Result
- Direction
- pulanit.pangu.admin.web.controller.permission uses gitee.pulanos.pangu.framework.sdk.dto, so a change to gitee.pulanos.pangu.framework.sdk.dto can break pulanit.pangu.admin.web.controller.permission, while a change to pulanit.pangu.admin.web.controller.permission can't break gitee.pulanos.pangu.framework.sdk.dto.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.permission uses a module listed above it, which is the healthy direction.
39→3 pulanit.pangu.admin.web.controller.permission uses gitee.pulanos.pangu.framework.sdk.dto.page✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.web.controller.permission uses a type in gitee.pulanos.pangu.framework.sdk.dto.page.
- The types involved
com.pulanit.pangu.admin.web.controller.permission.RoleController→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResultcom.pulanit.pangu.admin.web.controller.permission.UserController→com.gitee.pulanos.pangu.framework.sdk.dto.page.PageResult
- Direction
- pulanit.pangu.admin.web.controller.permission uses gitee.pulanos.pangu.framework.sdk.dto.page, so a change to gitee.pulanos.pangu.framework.sdk.dto.page can break pulanit.pangu.admin.web.controller.permission, while a change to pulanit.pangu.admin.web.controller.permission can't break gitee.pulanos.pangu.framework.sdk.dto.page.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.permission uses a module listed above it, which is the healthy direction.
39→14 pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.entity✕
- Connections
- 5 pairs of types, where a type in pulanit.pangu.admin.web.controller.permission uses a type in pulanit.pangu.admin.system.api.entity.
- The types involved
com.pulanit.pangu.admin.web.controller.permission.DeptController→com.pulanit.pangu.admin.system.api.entity.DeptEntitycom.pulanit.pangu.admin.web.controller.permission.ResourceController→com.pulanit.pangu.admin.system.api.entity.ResourceEntitycom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.web.controller.permission.UserController→com.pulanit.pangu.admin.system.api.entity.RoleEntitycom.pulanit.pangu.admin.web.controller.permission.UserController→com.pulanit.pangu.admin.system.api.entity.UserEntity
- Direction
- pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.entity, so a change to pulanit.pangu.admin.system.api.entity can break pulanit.pangu.admin.web.controller.permission, while a change to pulanit.pangu.admin.web.controller.permission can't break pulanit.pangu.admin.system.api.entity.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.permission uses a module listed above it, which is the healthy direction.
39→24 pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.param✕
- Connections
- 7 pairs of types, where a type in pulanit.pangu.admin.web.controller.permission uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.web.controller.permission.ResourceController→com.pulanit.pangu.admin.system.api.param.ResourceForLoginOutcom.pulanit.pangu.admin.web.controller.permission.ResourceController→com.pulanit.pangu.admin.system.api.param.ResourceOutcom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.param.RoleIncom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.param.UserOutcom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.param.UserPageIncom.pulanit.pangu.admin.web.controller.permission.UserController→com.pulanit.pangu.admin.system.api.param.UserOutcom.pulanit.pangu.admin.web.controller.permission.UserController→com.pulanit.pangu.admin.system.api.param.UserPageIn
- Direction
- pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.web.controller.permission, while a change to pulanit.pangu.admin.web.controller.permission can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.permission uses a module listed above it, which is the healthy direction.
39→32 pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.service✕
- Connections
- 5 pairs of types, where a type in pulanit.pangu.admin.web.controller.permission uses a type in pulanit.pangu.admin.system.api.service.
- The types involved
com.pulanit.pangu.admin.web.controller.permission.DeptController→com.pulanit.pangu.admin.system.api.service.DeptServicecom.pulanit.pangu.admin.web.controller.permission.ResourceController→com.pulanit.pangu.admin.system.api.service.ResourceServicecom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.service.RoleServicecom.pulanit.pangu.admin.web.controller.permission.RoleController→com.pulanit.pangu.admin.system.api.service.UserServicecom.pulanit.pangu.admin.web.controller.permission.UserController→com.pulanit.pangu.admin.system.api.service.UserService
- Direction
- pulanit.pangu.admin.web.controller.permission uses pulanit.pangu.admin.system.api.service, so a change to pulanit.pangu.admin.system.api.service can break pulanit.pangu.admin.web.controller.permission, while a change to pulanit.pangu.admin.web.controller.permission can't break pulanit.pangu.admin.system.api.service.
- Position
- Below the diagonal: pulanit.pangu.admin.web.controller.permission uses a module listed above it, which is the healthy direction.
40→24 pulanit.pangu.admin.web.log uses pulanit.pangu.admin.system.api.param✕
- Connections
- 1 pair of types, where a type in pulanit.pangu.admin.web.log uses a type in pulanit.pangu.admin.system.api.param.
- The types involved
com.pulanit.pangu.admin.web.log.LogQueue→com.pulanit.pangu.admin.system.api.param.LogIn
- Direction
- pulanit.pangu.admin.web.log uses pulanit.pangu.admin.system.api.param, so a change to pulanit.pangu.admin.system.api.param can break pulanit.pangu.admin.web.log, while a change to pulanit.pangu.admin.web.log can't break pulanit.pangu.admin.system.api.param.
- Position
- Below the diagonal: pulanit.pangu.admin.web.log uses a module listed above it, which is the healthy direction.
40→32 pulanit.pangu.admin.web.log uses pulanit.pangu.admin.system.api.service✕
- Connections
- 2 pairs of types, where a type in pulanit.pangu.admin.web.log uses a type in pulanit.pangu.admin.system.api.service.
- The types involved
com.pulanit.pangu.admin.web.log.LogQueueConsumer→com.pulanit.pangu.admin.system.api.service.LogServicecom.pulanit.pangu.admin.web.log.Task→com.pulanit.pangu.admin.system.api.service.LogService
- Direction
- pulanit.pangu.admin.web.log uses pulanit.pangu.admin.system.api.service, so a change to pulanit.pangu.admin.system.api.service can break pulanit.pangu.admin.web.log, while a change to pulanit.pangu.admin.web.log can't break pulanit.pangu.admin.system.api.service.
- Position
- Below the diagonal: pulanit.pangu.admin.web.log 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 123 | High / Critical |
| A07:2025 — Authentication Failures | 68 | High / Critical |
| A05:2025 — Injection | 29 | High / Critical |
Roadmap
Top priorities: Resolve the 262 Orphaned file finding(s) in Knowledge Freshness — start with index.vue (34), props.js (23), save.vue (8); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +1.6 pts | Low | REDACTED Scanning |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +1.6 pts | Medium | Keyboard semantics |
| Resolve the 66 REDACTED finding(s) in Secrets (history) — start with REDACTED (59), REDACTED (2), REDACTED (2). | +1.4 pts | Medium | Secrets (history) |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +1.4 pts | Medium | Type Safety |
| Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value. | +1.4 pts | Medium | Dead Code |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +1.3 pts | Medium | Text alternatives |
| 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). | +1.1 pts | Medium | Nullable reference types |
| 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. | +1.0 pts | Medium | Security & performance tooling |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.8 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.4 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Secrets (history): REDACTED: REDACTED |
| pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java | 5.1 | Mixed | Code Duplication: Edited copy of a member (17 corresponding lines) |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.1 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/RoleServiceImpl.java | 6.3 | Mixed | Code Duplication: Edited copy of a member (11 corresponding lines) |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/controller/permission/RoleController.java | 7.0 | Mixed | Code Duplication: Duplicated block (6 lines × 3) |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: 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 66 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 — 66 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, 896 of 1008 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D1 Cyclomatic Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .vue) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- D2 Cognitive Complexity — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Most of this repository's production source (.js, .vue) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
- 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Maven tree, and its score reflects currency alone.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (6 contributor(s) across 2022 commit(s) sampled, automation and bot accounts excluded). One of them holds 100% of the history; the other 5 hold 0% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- D20 ADR Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The ADR lexicon (adr-lexicon-1) covers de, en, it, nl. A record identified as another language, or whose language could not be identified (fewer than 25 words of prose, or no clear winner), is never read with English rules: its missing-section, status, consequence-cost and same-question rules abstain, and only the structural rules (title, single option, dangling link, enforcement field) run.
- 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.
- 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these 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 a COLLECTOR gap, not an environment fault: it declares a published package (pangu-spring-boot-starter/pom.xml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — 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. 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each 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.
- AC6 Visual & motion safety — 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. 67 further occurrence(s) are not listed individually; the score already reflects all 107.
- AXB2 Runtime readiness — 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. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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 DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Vue components is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 69 further occurrence(s) are not listed individually; the score already reflects all 109.
- R4 Test Coverage — 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. 359 further occurrence(s) are not listed individually; the score already reflects all 399.
- R7 Dead Code — 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. 330 further occurrence(s) are not listed individually; the score already reflects all 370.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X12 Unreachable branch — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 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.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- 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 Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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
D4 · Code Duplication
9 duplicated block group(s) detected. 0.5 % of the production lines (317 of 66,102) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 7 of the 19 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .vue, .js (82% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 3 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with UserManager.java, UserServiceImpl.java, CrudService.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 Edited copy of a member (7 corresponding lines) finding(s) in Code Duplication — start with UserManager.java, RoleServiceImpl.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with DeptServiceImpl.java, ResourceServiceImpl.java. — One of this dimension's main actionable groups (2 warning-level).
D5 · Coupling
9 production modules (Maven+npm+uni_modules), 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 6 of the 9 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
3 of 25 classes have LCOM4 above 3.
What to do
- Resolve the 3 Low cohesion finding(s) in Cohesion (LCOM4) — start with ResourceServiceImpl.java, RoleServiceImpl.java, GlobalExceptionHandler.java. — One of this dimension's main actionable groups (3 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D10 · Test Quality
0 skipped, 37 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 37 tests (5 harness-style project(s) excluded from the assertion penalty).
What to do
- Resolve the 34 No direct assertions finding(s) in Test Quality — start with CrudTest.java (8), AnnotationBasedDemoServiceTest.java (5), ShardingTablesTest.java (5). — One of this dimension's main actionable groups (34 recommendation-level).
- Resolve the 3 No assertions finding(s) in Test Quality — start with ApiBasedDemoServiceTest.java, MainBizServiceTest.java, SenderTest.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Test project verifies nothing finding(s) in Test Quality — start with ApiBasedDemoServiceTest.java, SenderTest.java, MainBizServiceTest.java. — One of this dimension's main actionable groups (3 warning-level).
D12 · Dependency Hygiene
98 outdated artifact(s) of 111 resolved by the build, graded against Maven Central. The poms themselves state a version for only 42 of 162 declaration(s) — the rest are parent- or BOM-managed, which is why this is read from the resolved graph rather than from the manifests. Whether any of these is DEPRECATED is not graded — Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Known CVEs in this graph are D30's question, read from the manifest there.
D13 · REDACTED Scanning
1 secret(s) detected. 15 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What to do
- 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
0 of 18 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 41 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. 120 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. 1 of them resolve to no licence at all on Central, even through their parent POMs; that is missing data, not a violation, and none of them is charged. A further 4 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 7882 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with LogLevelChangeEventListener.java. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 30 document(s) read across 5 unit(s).
D24 · Comment Value
0 of 43 judged comments only repeat the code they sit on (0.0 %). 1925 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 10 build units (Maven, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
85 % of calls cross a namespace and 36 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 High interface indirection finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
66 finding(s): 0 critical, 66 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 66 REDACTED finding(s) in Secrets (history) — start with REDACTED (59), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (66 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
31 finding(s): 0 critical, 4 high, 26 medium, 1 low. 4 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 2 file(s) — `pangu-admin/pangu-admin-frontend/public/index.html` (line 8, lines 15–16, line 30), `pangu-app-starter/template.h5.html` (line 9) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10). — One of this dimension's main actionable groups (10 warning-level).
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- No action in Static Analysis (SAST) — all 4 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 (4 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
119 finding(s): 9 critical, 71 high, 31 medium, 8 low.
What to do
- Resolve the 71 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (42), REDACTED (29). — One of this dimension's main actionable groups (71 issue-level).
- Resolve the 31 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED (10). — One of this dimension's main actionable groups (31 warning-level).
- Resolve the 9 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5), REDACTED (4). — One of this dimension's main actionable groups (9 issue-level).
D34 · Knowledge Freshness
265 of 265 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 265 of the 754 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 262 Orphaned file finding(s) in Knowledge Freshness — start with index.vue (34), props.js (23), save.vue (8). — One of this dimension's main actionable groups (262 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with REDACTED, parser.js, calendar.js. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: UserServiceImpl.java↔UserController.java 74%; ResourceServiceImpl.java↔ResourceController.java 60%; UserServiceImpl.java↔save.vue 58%
What to do
- Resolve the 5 Change coupling finding(s) in Change Coupling — start with ResourceServiceImpl.java (2), UserController.java, RoleController.java. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with UserServiceImpl.java. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 13 platform declaration(s) and 82 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.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×18) — pangu-admin/pangu-admin-frontend/public/index.html:27, pangu-admin/pangu-admin-frontend/src/components/scCropper/index.vue:14, pangu-admin/pangu-admin-frontend/src/components/scQrCode/index.vue:11, …
- Video with no captions <track> offers no captions. This player's source is set at runtime, so there is no caption file to author here: give the player a way to carry captions — accept a track/captions URL alongside the media and render a <track kind="captions"> when one is supplied — and capture that asset wherever the media enters the product (upload, import or generation). — pangu-app-starter/uni_modules/uview-ui/components/u-swiper/u-swiper.vue:56
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — pangu-admin/pangu-admin-frontend/src/components/scCodeEditor/index.vue:12, pangu-app-starter/uni_modules/uview-ui/components/u-code-input/u-code-input.vue:30, pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:33
- 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. (×4) — pangu-admin/pangu-admin-frontend/src/components/scSelectFilter/index.vue:16, pangu-admin/pangu-admin-frontend/src/layout/components/userbar.vue:59, pangu-admin/pangu-admin-frontend/src/views/login/components/commonPage.vue:7, …
- 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). — pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:3
- 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. (×3) — pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:20, pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:30, pangu-app-starter/uni_modules/uview-ui/components/u-textarea/u-textarea.vue:3
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
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×2) — pangu-admin/pangu-admin-frontend/public/index.html:2, pangu-app-starter/h5.html:3
- 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). — pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:32
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. (×8) — pangu-admin/pangu-admin-frontend/src/layout/components/iframeView.vue:12, pangu-admin/pangu-admin-frontend/src/utils/print.js:93, pangu-admin/pangu-admin-frontend/src/views/home/work/index.vue:13, …
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — pangu-admin/pangu-admin-frontend/src/views/login/index.vue:6, pangu-admin/pangu-admin-frontend/src/views/setting/task/index.vue:18
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — pangu-app-starter/h5.html:3
- user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×2) — pangu-app-starter/static/app-plus/mp-html/local.html:1, pangu-app-starter/template.h5.html:7
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="app">, so there is no content here to wrap — render the <main> from the component mounted into it. — pangu-app-starter/template.h5.html:2
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
- This <li> binds mouse-enter and mouse-leave and nothing else — no click, no key handler, no focus handler, and no tabindex="0", so it cannot even take focus. A keyboard user cannot hover, so whatever the pair reveals or highlights is reachable with a mouse only. Bind the same state to focus/blur as well, and add tabindex="0"="0" so the element can receive that focus. — pangu-admin/pangu-admin-frontend/src/components/scContextmenu/item.vue:12
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×26) — pangu-admin/pangu-admin-frontend/src/components/scFileSelect/index.vue:50, pangu-admin/pangu-admin-frontend/src/components/scIconSelect/index.vue:12, pangu-admin/pangu-admin-frontend/src/components/scIconSelect/index.vue:29, …
- A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — pangu-app-starter/static/app-plus/mp-html/local.html:1
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.app-loading__loader` moves (`animation: .5s loader 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. — pangu-admin/pangu-admin-frontend/public/index.html:36
- The inline foreground/background colours fall below the 4.5:1 WCAG AA minimum for normal text. Darken/lighten one of them. — pangu-admin/pangu-admin-frontend/src/views/setting/task/logs.vue:32
- `.xcbutton` sets color: #f4f4f5 on background-color: #25c2a0 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-website/src/pages/index.module.css:39
- `.xcbutton2` sets color: #f4f4f5 on background-color: #25c2a0 — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-website/src/pages/index.module.css:65
- `.code` sets color: #999 on background-color: #333 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/views/test/autocode/list.vue:219
- `.code` sets color: #fff on background-color: #848484 — 3.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/views/setting/log/info.vue:53
- `.contextmenu li:hover` sets color: #66b1ff on background-color: #ebf5ff — 2.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/style/fix.scss:76
- `.contextmenu li:hover` sets color: #66b1ff on background-color: #ecf5ff — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:294
- `.add-node-popover-body li i:hover` sets color: #fff on background-color: #3296fa — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/index.vue:134
- `.sc-user-select__toicon i` sets color: #fff on background-color: #ccc — 1.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/select.vue:250
- `.sc-filter-main table td .del` sets color: #999 on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:297
- `.sc-filter-main table td .del:hover` sets color: #fff on background-color: #F56C6C — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:298
- `.sc-filter-my-list li:hover` sets color: #409EFF on background-color: #ecf5ff — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scFilterBar/my.vue:102
- `.sc-filter-my-list li .del:hover` sets color: #fff on background-color: #F56C6C — 2.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scFilterBar/my.vue:106
- `.sc-contextmenu__menu > li:hover` sets color: #66b1ff on background-color: #ecf5ff — 2.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — pangu-admin/pangu-admin-frontend/src/components/scContextmenu/index.vue:95
- `a` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — pangu-admin/pangu-admin-frontend/src/style/app.scss:7
- `*` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — pangu-admin/pangu-admin-frontend/src/style/app.scss:8
- `.sc-dialog__headerbtn button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — pangu-admin/pangu-admin-frontend/src/components/scDialog/index.vue:78
- `.mce-content-body.mce-content-readonly *[contentEditable=true]:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.css:463, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.inline.css:482, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.css:482, …
- `.mce-content-body td[data-mce-selected] *` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×4) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.css:485, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.inline.css:504, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.css:504, …
- `.tox *:not(svg):not(rect)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:45, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:45
- `.tox-tinymce *:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:91, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:91
- `.tox .tox-button` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:253, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:253
- `.tox .tox-button--secondary` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:304, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:304
- `.tox .tox-swatches__picker-btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:896, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:896
- `.tox .tox-toolbar-textfield` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:1757, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:1757
- `.tox .tox-mbtn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. (×2) — pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:2115, pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:2115
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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `UserService` declares 16 abstract methods: `add`, `batchDelete`, `cancelRole`, `delete`, `grantSelectRole`, `list`, `listGrantedUsersByRoleId`, `listUnGrantedUsersByRoleId`, `login`, `queryGrantRolesByUserId`, `queryRolesByUserId`, `queryUserDetailInfoById`, `resetPassword`, `update`, `updatePassword`, `validateUserName`. 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. — pangu-admin/pangu-admin-backend/pangu-admin-system-api/src/main/java/com/pulanit/pangu/admin/system/api/service/UserService.java:18
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
M1 · Documentation (README)
- The root README is 20 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- 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
M3 · Folder & project structure
P1 · CI/CD gates
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P10 · Library API & versioning
P2 · Observability
- Only 29/32 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `pangu-examples/pangu-examples-shardingsphere-readwrite-splitting`, `pangu-examples/pangu-examples-shardingsphere-sharding`, `pangu-examples/pangu-examples-webapi-gateway-shenyu-based`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `pangu-admin/pangu-admin-frontend/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — pangu-admin/pangu-admin-frontend/package.json:10
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.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
- 0 typed · 588 plain JS — the untyped files are pangu-admin/pangu-admin-frontend/public/code/list/index.vue, pangu-admin/pangu-admin-frontend/public/code/list/save.vue, pangu-admin/pangu-admin-frontend/public/config.js, pangu-admin/pangu-admin-frontend/public/tinymce/langs/zh_CN.js, pangu-admin/pangu-admin-frontend/src/App.vue, pangu-admin/pangu-admin-frontend/src/api/index.js (+582 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- 24 duplicated blocks under pangu-app-starter/uni_modules/uview-ui/components/ have copies in at least two of the sibling directories u-avatar, u-avatar-group, u-calendar, u-car-keyboard, u-checkbox, u-checkbox-group (+33 more sibling(s) not listed) — 17 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 24 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 24 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 24 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:70
- 14 of the duplicated blocks reported below have copies in at least two of the sibling directories login, setting, template, userCenter under pangu-admin/pangu-admin-frontend/src/views/. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:46
- 14 duplicated blocks under pangu-admin/pangu-admin-frontend/src/views/setting/ have copies in at least two of the sibling directories client, dept, dic, resource, role, table (+2 more sibling(s) not listed) — 12 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:57
- 8 duplicated blocks under pangu-admin/pangu-admin-frontend/src/components/ have copies in at least two of the sibling directories scFileExport, scFileImport, scFileSelect, scTable, scUpload, scVideo — 3 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — pangu-admin/pangu-admin-frontend/src/components/scFileImport/index.vue:100
- 6 of the duplicated blocks reported below have copies in at least two of the sibling directories components, layout, views under pangu-admin/pangu-admin-frontend/src/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — pangu-admin/pangu-admin-frontend/src/layout/components/setting.vue:31
- pangu-admin/pangu-admin-frontend/src/components/scUpload/file.vue:35 · pangu-admin/pangu-admin-frontend/src/components/scUpload/multiple.vue:52 — the two spans are one implementation copied and then locally edited — 803 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-admin/pangu-admin-frontend/src/components/scUpload/file.vue:35
- pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:70 · pangu-app-starter/uni_modules/uview-ui/components/u-radio/u-radio.vue:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:70
- pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:137 · pangu-app-starter/uni_modules/uview-ui/components/u-textarea/u-textarea.vue:98 — the two spans are one implementation copied and then locally edited — 285 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:137
- pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:57 · pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:53 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:57
- pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:107 · pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/send.vue:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:107
- pangu-admin/pangu-admin-frontend/src/views/setting/role/index.vue:112 · pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue:171 — the two spans are one implementation copied and then locally edited — 351 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-admin/pangu-admin-frontend/src/views/setting/role/index.vue:112
- pangu-admin/pangu-admin-frontend/public/code/list/index.vue:110 · pangu-admin/pangu-admin-frontend/src/views/setting/dic/index.vue:224 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-admin/pangu-admin-frontend/public/code/list/index.vue:110
- pangu-admin/pangu-admin-frontend/src/layout/components/setting.vue:31 · pangu-admin/pangu-admin-frontend/src/views/userCenter/user/seting.vue:34 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-admin/pangu-admin-frontend/src/layout/components/setting.vue:31
- pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:105 · pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/promoter.vue:42 · pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/send.vue:46 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:105
- pangu-app-starter/uni_modules/uview-ui/components/u-dropdown-item/u-dropdown-item.vue:49 · pangu-app-starter/uni_modules/uview-ui/components/u-dropdown/u-dropdown.vue:49 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-app-starter/uni_modules/uview-ui/components/u-dropdown-item/u-dropdown-item.vue:49
- pangu-admin/pangu-admin-frontend/src/views/setting/dept/index.vue:95 · pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue:191 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/dept/index.vue:95
- pangu-admin/pangu-admin-frontend/src/views/setting/dic/dic.vue:57 · pangu-admin/pangu-admin-frontend/src/views/setting/dic/list.vue:67 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/dic/dic.vue:57
- pangu-app-starter/uni_modules/uview-ui/components/u-checkbox-group/u-checkbox-group.vue:36 · pangu-app-starter/uni_modules/uview-ui/components/u-radio-group/u-radio-group.vue:38 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — pangu-app-starter/uni_modules/uview-ui/components/u-checkbox-group/u-checkbox-group.vue:36
- pangu-admin/pangu-admin-frontend/src/views/setting/dept/save.vue:89 · pangu-admin/pangu-admin-frontend/src/views/setting/dic/dic.vue:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/dept/save.vue:89
- pangu-admin/pangu-admin-frontend/src/components/scFileImport/index.vue:100 · pangu-admin/pangu-admin-frontend/src/components/scUpload/index.vue:210 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-admin/pangu-admin-frontend/src/components/scFileImport/index.vue:100
- pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:46 · pangu-admin/pangu-admin-frontend/src/views/userCenter/user/password.vue:47 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:46
- pangu-admin/pangu-admin-frontend/src/views/setting/role/user.vue:154 · pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue:233 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/role/user.vue:154
- pangu-admin/pangu-admin-frontend/src/views/setting/user/save.vue:118 · pangu-admin/pangu-admin-frontend/src/views/userCenter/user/password.vue:46 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/user/save.vue:118
- pangu-admin/pangu-admin-frontend/src/api/model/system.js:47 · pangu-admin/pangu-admin-frontend/src/api/model/system.js:142 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/api/model/system.js:47
- pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:330 · pangu-app-starter/uni_modules/uview-ui/components/u-dropdown-item/u-dropdown-item.vue:82 · pangu-app-starter/uni_modules/uview-ui/components/u-dropdown/u-dropdown.vue:82 · pangu-app-starter/uni_modules/uview-ui/components/u-tooltip/u-tooltip.vue:217 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:330
- pangu-admin/pangu-admin-frontend/src/layout/components/sideM.vue:59 · pangu-admin/pangu-admin-frontend/src/layout/index.vue:277 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-admin/pangu-admin-frontend/src/layout/components/sideM.vue:59
- pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:47 · pangu-admin/pangu-admin-frontend/src/views/template/list/crud/index.vue:65 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:47
- pangu-app-starter/uni_modules/uview-ui/components/u-slider/nvue - 副本.js:20 · pangu-app-starter/uni_modules/uview-ui/components/u-slider/nvue.js:16 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-app-starter/uni_modules/uview-ui/components/u-slider/nvue - 副本.js:20
- pangu-admin/pangu-admin-frontend/src/api/model/system.js:128 · pangu-admin/pangu-admin-frontend/src/api/model/system.js:193 · pangu-admin/pangu-admin-frontend/src/api/model/system.js:230 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/api/model/system.js:128
- pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:48 · pangu-admin/pangu-admin-frontend/src/views/setting/task/index.vue:110 · pangu-admin/pangu-admin-frontend/src/views/template/list/crud/index.vue:66 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:48
- pangu-admin/pangu-admin-frontend/src/directives/auth.js:4 · pangu-admin/pangu-admin-frontend/src/directives/role.js:4 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — pangu-admin/pangu-admin-frontend/src/directives/auth.js:4
- pangu-admin/pangu-admin-frontend/src/views/setting/resource/save.vue:142 · pangu-admin/pangu-admin-frontend/src/views/template/list/crud/save.vue:65 — the two spans are one implementation copied and then locally edited — 80 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-admin/pangu-admin-frontend/src/views/setting/resource/save.vue:142
- pangu-admin/pangu-admin-frontend/src/views/login/components/phoneForm.vue:48 · pangu-admin/pangu-admin-frontend/src/views/login/resetPassword.vue:90 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-admin/pangu-admin-frontend/src/views/login/components/phoneForm.vue:48
- pangu-admin/pangu-admin-frontend/src/views/setting/client/save.vue:79 · pangu-admin/pangu-admin-frontend/src/views/setting/table/save.vue:143 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-admin/pangu-admin-frontend/src/views/setting/client/save.vue:79
- pangu-admin/pangu-admin-frontend/src/views/setting/user/info.vue:76 · pangu-admin/pangu-admin-frontend/src/views/userCenter/user/account.vue:52 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-admin/pangu-admin-frontend/src/views/setting/user/info.vue:76
- pangu-admin/pangu-admin-frontend/src/views/setting/user/role.vue:134 · pangu-admin/pangu-admin-frontend/src/views/setting/user/role.vue:151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — pangu-admin/pangu-admin-frontend/src/views/setting/user/role.vue:134
- pangu-admin/pangu-admin-frontend/src/views/vab/formtable.vue:96 · pangu-admin/pangu-admin-frontend/src/views/vab/iconselect.vue:47 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-admin/pangu-admin-frontend/src/views/vab/formtable.vue:96
- pangu-app-starter/uni_modules/uview-ui/components/u-col/u-col.vue:40 · pangu-app-starter/uni_modules/uview-ui/components/u-row/u-row.vue:35 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — pangu-app-starter/uni_modules/uview-ui/components/u-col/u-col.vue:40
- pangu-app-starter/uni_modules/uview-ui/components/u-index-anchor/u-index-anchor.vue:27 · pangu-app-starter/uni_modules/uview-ui/components/u-index-item/u-index-item.vue:18 — the two spans are one implementation copied and then locally edited — 74 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — pangu-app-starter/uni_modules/uview-ui/components/u-index-anchor/u-index-anchor.vue:27
- pangu-app-starter/uni_modules/uview-ui/components/u-scroll-list/u-scroll-list.vue:171 · pangu-app-starter/uni_modules/uview-ui/components/u-skeleton/u-skeleton.vue:164 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — pangu-app-starter/uni_modules/uview-ui/components/u-scroll-list/u-scroll-list.vue:171
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- pangu-admin/pangu-admin-frontend/src/locales/index.js:4 imports element-plus/lib/locale/lang/zh-cn, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — pangu-admin/pangu-admin-frontend/src/locales/index.js:4
- pangu-admin/pangu-admin-frontend/src/locales/index.js:5 imports element-plus/lib/locale/lang/en, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — pangu-admin/pangu-admin-frontend/src/locales/index.js:5
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- popNode has cyclomatic complexity 120 and cognitive complexity 277; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:488
- onOpenTag has cyclomatic complexity 85 and cognitive complexity 185; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:291
- viewStyle has cyclomatic complexity 58 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/mixin/style.js:214
- _clone has cyclomatic complexity 35 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:74
- solar2lunar has cyclomatic complexity 30 and cognitive complexity 31; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:383
- set has cyclomatic complexity 29 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:581
- parseStyle has cyclomatic complexity 27 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:192
- _loop has cyclomatic complexity 25 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/static/app-plus/mp-html/js/handler.js:63
- cb has cyclomatic complexity 22 and cognitive complexity 39; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1188
- text has cyclomatic complexity 21 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:929
- clickHandler has cyclomatic complexity 19 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:352
- _onMessage has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:264
- lunar2solar has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:502
- range has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:402
- traversal has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:167
- (anonymous) has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:102
- value has cyclomatic complexity 17 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-text/value.js:4
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/luch-request/core/mergeConfig.js:27
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1177
- startOf has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:140
- rowsArray has cyclomatic complexity 14 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-skeleton/u-skeleton.vue:89
- getHtml has cyclomatic complexity 13 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-admin/pangu-admin-frontend/src/utils/print.js:49
- timeFormat has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:281
- timeFrom has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:335
- screen has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:118
- empty has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/function/test.js:150
- (anonymous) has cyclomatic complexity 12 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:174
- toText has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:162
- queryParams has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:400
- onText has cyclomatic complexity 11 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:841
- touchend has cyclomatic complexity 11 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js:113
- getActiveIndex has cyclomatic complexity 11 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-rate/u-rate.vue:211
- touchmove has cyclomatic complexity 11 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js:72
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/components/u-upload/utils.js:73
- openPage has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/uni_modules/uview-ui/libs/util/route.js:85
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — pangu-app-starter/static/common/js/touch-emulator.js:128
R3 · Large Files
- REDACTED has 1114 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js has 888 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:1
- pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue has 725 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:1
- REDACTED has 666 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
- pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue has 557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue has 535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue:1
- pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js has 508 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:1
- pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue has 465 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue has 429 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue:1
- pangu-admin/pangu-admin-frontend/src/views/vab/form.vue has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-admin/pangu-admin-frontend/src/views/vab/form.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — REDACTED:1, pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:1, pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
- The package in `pangu-app-starter` declares the lint script `test` (`eslint . --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run test` in `pangu-app-starter` (or the workspace's task runner). — pangu-app-starter/package.json:4
- The package in `pangu-admin/pangu-admin-frontend` declares the lint script `lint` (`vue-cli-service lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `pangu-admin/pangu-admin-frontend` (or the workspace's task runner). — pangu-admin/pangu-admin-frontend/package.json:8
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 24 application, 4 tooling and 4 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u-form/u-form.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js, pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/views/setting/task/save.vue, pangu-admin/pangu-admin-frontend/src/views/vab/cron.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js, pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×24) — pangu-admin/pangu-admin-frontend/src/views/vab/form.vue, pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue, pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue, …
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/components/scIconSelect/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/config/iconSelect.js
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue, pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue, pangu-app-starter/uni_modules/uview-ui/components/u-datetime-picker/u-datetime-picker.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — REDACTED
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u--input/u--input.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/views/vab/fileselect.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/components/scFileSelect/index.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/views/setting/role/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/views/setting/role/user.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/components/scWorkflow/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/select.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/views/setting/user/save.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodeWrap.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/branch.vue
- no import path from any entry point (24 application, 4 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (pangu-app-starter/uni_modules/uview-ui/components/u-icon/u-icon.vue) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — pangu-app-starter/uni_modules/uview-ui/components/u-icon/icons.js
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. (×2) — pangu-website/sidebars.js:14, pangu-website/docusaurus.config.js:7
- Declared in pangu-admin/pangu-admin-frontend/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — pangu-admin/pangu-admin-frontend/package.json:15
- Declared in pangu-website/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — pangu-website/package.json:20
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `Time.getFormateTime(value)` 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) — pangu-admin/pangu-admin-frontend/src/directives/time.js:71, pangu-admin/pangu-admin-frontend/src/directives/time.js:73
- `tool.dateFormat(value,format)` 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. — pangu-admin/pangu-admin-frontend/src/directives/time.js:77
- `dom` 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. — pangu-admin/pangu-admin-frontend/src/utils/print.js:15
- `textareas[k2].value` 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. — pangu-admin/pangu-admin-frontend/src/utils/print.js:70
- `n.html` is text this program did not author, and it is written into the text of an element through Vue's `v-html` 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. — pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:25
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — pangu-app-starter/uni_modules/uview-ui/libs/luch-request/adapters/index.js:35, pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:165, pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:173
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×32) — pangu-app-starter/uni_modules/uview-ui/components/u-transition/transition.js:111, pangu-app-starter/uni_modules/uview-ui/components/u-transition/transition.js:141, pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:239, …
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
X5 · Nullable reference types
- 0/30 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 |
| AC5 · ARIA correctness | 4.1.2 | 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 | 32.4 | Weak — gated by R1, R7, X3, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 89.2 | Strong | Solid. |
| Maturity | 54.0 | Adequate — gated by D34, M1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 36.7 | Weak — gated by R4, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 33.9 | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 32.2 | Weak — gated by AC1, AC3, AC4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 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 — 56 check(s) not relevant to this codebase
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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.
- D1 Cyclomatic Complexity — cyclomatic complexity not measured — .js, .vue exposed no member bodies
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D2 Cognitive Complexity — cognitive complexity not measured — .js, .vue exposed no member bodies
- D20 ADR Quality — 1 ADR(s) are written in a language our ADR lexicon does not cover, or are too short to tell (undetermined); their sections and statuses were not judged.
- 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"]`.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D3 God Classes — Most of this repository's production source (.js, .vue) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 30 current-state document(s) make no claim of a kind M4 checks. 4 claim(s) of kinds M4 does not check were not checked (command argument 4); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/AdminWebApplication.java:11 (@SpringBootApplication))
- 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 tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, 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.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X13 Undrained process stream — 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
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Java 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
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X27 Collection changed while being enumerated — X27 reached only 18% of this repository's production lines — javascript (35,912 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 219 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
- <img> without a text alternative pangu-admin/pangu-admin-frontend/public/index.html:27
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/components/scCropper/index.vue:14
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/components/scQrCode/index.vue:11
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/layout/components/sideM.vue:7
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/layout/other/404.vue:4
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/views/home/widgets/components/ver.vue:4
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/views/home/widgets/components/welcome.vue:5
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/views/login/index.vue:46
- <img> without a text alternative pangu-admin/pangu-admin-frontend/src/views/vab/cropper.vue:42
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-album/u-album.vue:17
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-avatar/u-avatar.vue:40
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-empty/u-empty.vue:14
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-icon/u-icon.vue:7
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-image/u-image.vue:12
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-loading-page/u-loading-page.vue:17
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:6
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-swiper/u-swiper.vue:45
- <img> without a text alternative pangu-app-starter/uni_modules/uview-ui/components/u-tag/u-tag.vue:21
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scFileSelect/index.vue:50
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scIconSelect/index.vue:12
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:3
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/branch.vue:9
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/promoter.vue:3
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/send.vue:3
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/layout/components/sideM.vue:2
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/layout/components/userbar.vue:3
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/layout/components/userbar.vue:8
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/layout/index.vue:183
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/layout/index.vue:185
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/views/home/widgets/index.vue:40
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/views/home/widgets/index.vue:44
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/views/home/widgets/index.vue:51
- Click handler on a non-interactive <div> pangu-admin/pangu-admin-frontend/src/views/home/widgets/index.vue:58
- Click handler on a non-interactive <div> pangu-app-starter/static/app-plus/mp-html/local.html:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/layout/components/iframeView.vue:12
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/utils/print.js:93
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/views/home/work/index.vue:13
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/views/home/work/index.vue:18
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/views/home/work/index.vue:23
- <iframe> without a title pangu-admin/pangu-admin-frontend/src/views/home/work/index.vue:30
- <iframe> without a title pangu-app-starter/h5.html:12
- <iframe> without a title pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:31
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/components/scSelectFilter/index.vue:19
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/search.vue:11
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:23
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:25
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:26
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:28
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:29
- Click handler on a non-interactive <li> pangu-admin/pangu-admin-frontend/src/views/home/work/components/myapp.vue:14
- <label> that labels no control pangu-admin/pangu-admin-frontend/src/components/scSelectFilter/index.vue:16
- <label> that labels no control pangu-admin/pangu-admin-frontend/src/layout/components/userbar.vue:59
- <label> that labels no control pangu-admin/pangu-admin-frontend/src/views/login/components/commonPage.vue:7
- <label> that labels no control pangu-admin/pangu-admin-frontend/src/views/login/index.vue:47
- <input> without a programmatic label pangu-app-starter/uni_modules/uview-ui/components/u-code-input/u-code-input.vue:30
- <input> without a programmatic label pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:20
- <input> without a programmatic label pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:33
- <input> without a programmatic label pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <textarea> without a programmatic label pangu-admin/pangu-admin-frontend/src/components/scCodeEditor/index.vue:12
- <textarea> without a programmatic label pangu-app-starter/uni_modules/uview-ui/components/u-textarea/u-textarea.vue:3
- Viewport restricts zoom pangu-app-starter/static/app-plus/mp-html/local.html:1
- Viewport restricts zoom pangu-app-starter/template.h5.html:7
- Click handler on a non-interactive <span> pangu-admin/pangu-admin-frontend/src/components/scUpload/index.vue:18
- Click handler on a non-interactive <span> pangu-admin/pangu-admin-frontend/src/views/login/userRegister.vue:22
- <button> with no accessible text pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:3
- <html> without a lang pangu-app-starter/h5.html:3
- Hover-only interaction on <li> pangu-admin/pangu-admin-frontend/src/components/scContextmenu/item.vue:12
- Click handler on a non-interactive <ul> pangu-admin/pangu-admin-frontend/src/components/scIconSelect/index.vue:29
- REDACTED
Serious — 359 finding(s)
- No test reaches this file REDACTED:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:1
- No test reaches this file REDACTED:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:1
- No test reaches this file pangu-admin/pangu-admin-frontend/public/tinymce/langs/zh_CN.js:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/views/vab/form.vue:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/components/scTable/index.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue:1
- No test reaches this file pangu-app-starter/static/common/js/touch-emulator.js:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-datetime-picker/u-datetime-picker.vue:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/api/model/system.js:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/views/setting/dic/index.vue:1
- No test reaches this file REDACTED:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/utils/db.js:1
- No test reaches this file pangu-admin/pangu-admin-frontend/src/layout/index.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-tooltip/u-tooltip.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-tabs/u-tabs.vue:1
- No test reaches this file pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:1
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/libs/luch-request/adapters/index.js:35
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-transition/transition.js:111
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-transition/transition.js:141
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:165
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-search/u-search.vue:173
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:239
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:283
- Swallowed exception (empty catch) pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:269
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/userCenter/index.vue:95
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/userCenter/user/password.vue:96
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/userCenter/user/password.vue:100
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/template/list/crud/index.vue:126
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/template/list/crud/save.vue:79
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue:226
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:100
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/task/index.vue:136
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:96
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/role/index.vue:165
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/resource/index.vue:159
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/dic/index.vue:183
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/dic/index.vue:247
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/dept/index.vue:129
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:100
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/login/resetPassword.vue:91
- Swallowed exception (empty catch) pangu-admin/pangu-admin-frontend/src/views/login/resetPassword.vue:107
- 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
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/src/style/app.scss:7
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/src/style/app.scss:8
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/src/components/scDialog/index.vue:78
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.css:463
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.css:485
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.inline.css:482
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/content.inline.css:504
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:45
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:91
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:253
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:304
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:896
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:1757
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5-dark/skin.css:2115
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.css:482
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.css:504
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.inline.css:482
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/content.inline.css:504
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:45
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:91
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:253
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:304
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:896
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:1757
- Focus outline removed in CSS without a :focus replacement pangu-admin/pangu-admin-frontend/public/tinymce/skins/ui/tinymce-5/skin.css:2115
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (16 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/login/components/phoneForm.vue:48
- Duplicated block (16 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/client/save.vue:79
- Duplicated block (16 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/user/role.vue:134
- Duplicated block (16 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/vab/formtable.vue:96
- Duplicated block (16 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-col/u-col.vue:40
- Duplicated block (16 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-scroll-list/u-scroll-list.vue:171
- Untrusted text written into markup unescaped pangu-admin/pangu-admin-frontend/src/directives/time.js:71
- Untrusted text written into markup unescaped pangu-admin/pangu-admin-frontend/src/directives/time.js:73
- Untrusted text written into markup unescaped pangu-admin/pangu-admin-frontend/src/directives/time.js:77
- Untrusted text written into markup unescaped pangu-admin/pangu-admin-frontend/src/utils/print.js:15
- Untrusted text written into markup unescaped pangu-admin/pangu-admin-frontend/src/utils/print.js:70
- Untrusted text written into markup unescaped pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:25
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Change coupling: ResourceServiceImpl.java ↔ ResourceController.java pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java:1
- Change coupling: UserController.java ↔ system.js pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/controller/permission/UserController.java:1
- Change coupling: RoleController.java ↔ UserController.java pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/controller/permission/RoleController.java:1
- Change coupling: ResourceServiceImpl.java ↔ index.vue pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java:1
- Change coupling: ResourceController.java ↔ save.vue pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/controller/permission/ResourceController.java:1
- Low contrast colour pair in CSS (2.1:1) pangu-website/src/pages/index.module.css:39
- Low contrast colour pair in CSS (2.1:1) pangu-website/src/pages/index.module.css:65
- Low contrast colour pair in CSS (2.1:1) pangu-admin/pangu-admin-frontend/src/layout/components/tags.vue:294
- Low contrast colour pair in CSS (2.1:1) pangu-admin/pangu-admin-frontend/src/components/scContextmenu/index.vue:95
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Page without a main landmark pangu-admin/pangu-admin-frontend/public/index.html:2
- Page without a main landmark pangu-app-starter/h5.html:3
- Page without a main landmark pangu-app-starter/template.h5.html:2
- No assertions: testRedisCache pangu-examples/pangu-examples-cache-single/src/test/java/com/gitee/pulanos/pangu/showcases/cache/single/service/ApiBasedDemoServiceTest.java:17
- No assertions: buyItems pangu-examples/pangu-examples-seata-at/pangu-examples-seata-at-main/src/test/java/com/gitee/pulanos/pangu/showcases/seata/at/service/MainBizServiceTest.java:20
- No assertions: sendMsg pangu-examples/pangu-examples-mq-rabbitmq-sender/src/test/java/com/gitee/pulanos/pangu/examples/rabbitmq/SenderTest.java:38
- Test project verifies nothing: pangu-examples-cache-single pangu-examples/pangu-examples-cache-single/src/test/java/com/gitee/pulanos/pangu/showcases/cache/single/service/ApiBasedDemoServiceTest.java:17
- Test project verifies nothing: pangu-examples-mq-rabbitmq-sender pangu-examples/pangu-examples-mq-rabbitmq-sender/src/test/java/com/gitee/pulanos/pangu/examples/rabbitmq/SenderTest.java:38
- Test project verifies nothing: pangu-examples-seata-at-main pangu-examples/pangu-examples-seata-at/pangu-examples-seata-at-main/src/test/java/com/gitee/pulanos/pangu/showcases/seata/at/service/MainBizServiceTest.java:20
- Edited copy of a member (8 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/manager/UserManager.java:73
- Edited copy of a member (8 corresponding lines) pangu-examples/pangu-examples-dubbo-gateway-shenyu-service/src/main/java/com/gitee/pulanos/pangu/showcases/dubbo/gateway/provider/service/UserServiceImpl.java:52
- Edited copy of a member (8 corresponding lines) pangu-examples/pangu-examples-crud/src/main/java/com/gitee/pulanos/pangu/showcases/crud/service/CrudService.java:156
- Low cohesion: ResourceServiceImpl (LCOM4 4) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java:39
- Low cohesion: RoleServiceImpl (LCOM4 4) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/RoleServiceImpl.java:33
- Low cohesion: GlobalExceptionHandler (LCOM4 4) pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/config/GlobalExceptionHandler.java:20
- Duplicated block (20 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/layout/components/sideM.vue:59
- Duplicated block (20 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:47
- Duplicated block (20 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-slider/nvue - 副本.js:20
- Heading level jumps from h2 to h4 pangu-admin/pangu-admin-frontend/src/views/login/index.vue:6
- Heading level jumps from h2 to h4 pangu-admin/pangu-admin-frontend/src/views/setting/task/index.vue:18
- Low contrast colour pair in CSS (2.9:1) pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:298
- Low contrast colour pair in CSS (2.9:1) pangu-admin/pangu-admin-frontend/src/components/scFilterBar/my.vue:106
- Edited copy of a member (7 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/manager/UserManager.java:65
- Edited copy of a member (7 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/RoleServiceImpl.java:118
- Duplicated block (6 lines × 2) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/DeptServiceImpl.java:110
- Duplicated block (6 lines × 2) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java:153
- Duplicated block (7 lines × 2) pangu-examples/pangu-examples-dubbo-gateway-shenyu-service/src/main/java/com/gitee/pulanos/pangu/showcases/dubbo/gateway/provider/service/UserServiceImpl.java:53
- Duplicated block (7 lines × 2) pangu-examples/pangu-examples-dubbo-gateway-shenyu-service/src/main/java/com/gitee/pulanos/pangu/showcases/dubbo/gateway/provider/service/UserServiceImpl.java:42
- Duplicated block (42 lines × 2 locations) pangu-admin/pangu-admin-frontend/public/code/list/index.vue:110
- Duplicated block (42 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/layout/components/setting.vue:31
- Duplicated block (23 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/role/user.vue:154
- Duplicated block (23 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/user/save.vue:118
- Duplicated block (19 lines × 3 locations) pangu-admin/pangu-admin-frontend/src/api/model/system.js:128
- Duplicated block (19 lines × 3 locations) pangu-admin/pangu-admin-frontend/src/views/setting/table/index.vue:48
- Duplicated block with local edits (16 matched lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/user/info.vue:76
- Duplicated block with local edits (16 matched lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-index-anchor/u-index-anchor.vue:27
- Boundary violation [package:third-party-deep-import] pangu-admin/pangu-admin-frontend/src/locales/index.js:4
- Boundary violation [package:third-party-deep-import] pangu-admin/pangu-admin-frontend/src/locales/index.js:5
- This package's lint script runs in no CI job pangu-app-starter/package.json:4
- This package's lint script runs in no CI job pangu-admin/pangu-admin-frontend/package.json:8
- Dead file (~308 LoC) pangu-admin/pangu-admin-frontend/src/config/iconSelect.js
- Dead file (~308 LoC) REDACTED
- Dead file (~233 LoC) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/select.vue
- Dead file (~233 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-picker/u-picker.vue
- Dead file (~228 LoC) pangu-admin/pangu-admin-frontend/src/views/vab/chart.vue
- Dead file (~228 LoC) pangu-app-starter/uni_modules/uview-ui/libs/mixin/style.js
- <video> without a captions track pangu-app-starter/uni_modules/uview-ui/components/u-swiper/u-swiper.vue:56
- Data table has no header cells pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:32
- Animation without a prefers-reduced-motion guard pangu-admin/pangu-admin-frontend/public/index.html:36
- Low contrast colour pair (4.4:1) pangu-admin/pangu-admin-frontend/src/views/setting/task/logs.vue:32
- Low contrast colour pair in CSS (4.4:1) pangu-admin/pangu-admin-frontend/src/views/test/autocode/list.vue:219
- Low contrast colour pair in CSS (3.7:1) pangu-admin/pangu-admin-frontend/src/views/setting/log/info.vue:53
- Low contrast colour pair in CSS (2.0:1) pangu-admin/pangu-admin-frontend/src/style/fix.scss:76
- Low contrast colour pair in CSS (3.1:1) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/index.vue:134
- Low contrast colour pair in CSS (1.6:1) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/select.vue:250
- Low contrast colour pair in CSS (2.8:1) pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:297
- Low contrast colour pair in CSS (2.5:1) pangu-admin/pangu-admin-frontend/src/components/scFilterBar/my.vue:102
- TodoComment pangu-spring-boot-starter/src/main/java/com/gitee/pulanos/pangu/framework/starter/base/handler/LogLevelChangeEventListener.java:52
- Change-coupling hub: UserServiceImpl.java → UserController.java, index.vue, save.vue pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/UserServiceImpl.java
- REDACTED
- Edited copy of a member (17 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/ResourceServiceImpl.java:152
- Edited copy of a member (13 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/DeptServiceImpl.java:109
- Edited copy of a member (11 corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/RoleServiceImpl.java:105
- Edited copies of one member (3 members, 8+ corresponding lines) pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/DeptServiceImpl.java:47
- Duplicated block (10 lines × 2) pangu-generator-maven-plugin/src/main/java/com/gitee/pulanos/pangu/framework/generator/EntityGenerator.java:67
- Duplicated block (7 lines × 3) pangu-spring-boot-starter/src/main/java/com/gitee/pulanos/pangu/framework/starter/base/handler/ApplicationReadyEventListener.java:16
- Duplicated block (6 lines × 3) pangu-admin/pangu-admin-backend/pangu-admin-web/src/main/java/com/pulanit/pangu/admin/web/controller/permission/RoleController.java:115
- Members sharing a duplicated core (4 members, 50+ identical tokens) pangu-examples/pangu-examples-mq-rabbitmq-receiver/src/main/java/com/gitee/pulanos/pangu/examples/rabbitmq/listener/Queue1Listener.java:43
- Duplicated block (10 lines × 4) pangu-examples/pangu-examples-mq-rabbitmq-receiver/src/main/java/com/gitee/pulanos/pangu/examples/rabbitmq/listener/Queue1Listener.java:44
- Duplicated block (9 lines × 2) pangu-examples/pangu-examples-dubbo-triple/pangu-examples-dubbo-triple-provider/src/main/java/com/gitee/pulanos/pangu/showcases/dubbo/triple/provider/service/JobManager.java:16
- End-of-life framework: Spring Boot 2 pangu-dependencies/pom.xml:1
- Off the main sequence: pangu-spring-boot-starter
- Type Safety
- Duplication concentrated across 39 sibling directories (24 clone groups) pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:70
- Duplication concentrated across 4 sibling directories (14 clone groups) pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:46
- Duplication concentrated across 8 sibling directories (14 clone groups) pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:57
- Duplication concentrated across 6 sibling directories (8 clone groups) pangu-admin/pangu-admin-frontend/src/components/scFileImport/index.vue:100
- Duplication concentrated across 3 sibling directories (6 clone groups) pangu-admin/pangu-admin-frontend/src/layout/components/setting.vue:31
- Duplicated block with local edits (122 matched lines × 2 locations) pangu-admin/pangu-admin-frontend/src/components/scUpload/file.vue:35
- Duplicated block (95 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:70
- Duplicated block with local edits (59 matched lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:137
- Duplicated block (56 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/client/index.vue:57
- Duplicated block (50 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:107
- Duplicated block with local edits (50 matched lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/role/index.vue:112
- Duplicated block (41 lines × 3 locations) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:105
- Duplicated block (41 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-dropdown-item/u-dropdown-item.vue:49
- Duplicated block (39 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/dept/index.vue:95
- Duplicated block (33 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/dic/dic.vue:57
- Duplicated block (30 lines × 2 locations) pangu-app-starter/uni_modules/uview-ui/components/u-checkbox-group/u-checkbox-group.vue:36
- Duplicated block (28 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/dept/save.vue:89
- Duplicated block with local edits (27 matched lines × 2 locations) pangu-admin/pangu-admin-frontend/src/components/scFileImport/index.vue:100
- Duplicated block (27 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/user/reset.vue:46
- Duplicated block (21 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/api/model/system.js:47
- Duplicated block (21 lines × 4 locations) pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:330
- Duplicated block (18 lines × 2 locations) pangu-admin/pangu-admin-frontend/src/directives/auth.js:4
- Duplicated block with local edits (18 matched lines × 2 locations) pangu-admin/pangu-admin-frontend/src/views/setting/resource/save.vue:142
- Complex function popNode (cyclomatic 120, cognitive 277) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:488
- Complex function onOpenTag (cyclomatic 85, cognitive 185) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:291
- Complex function viewStyle (cyclomatic 58, cognitive 57) pangu-app-starter/uni_modules/uview-ui/libs/mixin/style.js:214
- Complex function _clone (cyclomatic 35, cognitive 51) REDACTED:74
- Complex function solar2lunar (cyclomatic 30, cognitive 31) pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:383
- Complex function set (cyclomatic 29, cognitive 35) pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:581
- Complex function parseStyle (cyclomatic 27, cognitive 35) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:192
- Complex function _loop (cyclomatic 25, cognitive 47) pangu-app-starter/static/app-plus/mp-html/js/handler.js:63
- Complex function cb (cyclomatic 22, cognitive 39) REDACTED:1188
- Complex function text (cyclomatic 21, cognitive 25) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:929
- Complex function clickHandler (cyclomatic 19, cognitive 44) pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:352
- Complex function _onMessage (cyclomatic 19, cognitive 25) pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:264
- Complex function lunar2solar (cyclomatic 19, cognitive 18) pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:502
- Complex function range (cyclomatic 19, cognitive 16) REDACTED:402
- Complex function traversal (cyclomatic 18, cognitive 20) pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:167
- Complex function (anonymous) (cyclomatic 18, cognitive 20) REDACTED:102
- Complex function value (cyclomatic 17, cognitive 24) pangu-app-starter/uni_modules/uview-ui/components/u-text/value.js:4
- Complex function (anonymous) (cyclomatic 16, cognitive 17) pangu-app-starter/uni_modules/uview-ui/libs/luch-request/core/mergeConfig.js:27
- Complex function (anonymous) (cyclomatic 16, cognitive 16) REDACTED:1177
- Complex function startOf (cyclomatic 16, cognitive 12) REDACTED:140
- Complex function rowsArray (cyclomatic 14, cognitive 21) pangu-app-starter/uni_modules/uview-ui/components/u-skeleton/u-skeleton.vue:89
- Complex function getHtml (cyclomatic 13, cognitive 29) pangu-admin/pangu-admin-frontend/src/utils/print.js:49
- Complex function timeFormat (cyclomatic 13, cognitive 15) REDACTED:281
- Complex function timeFrom (cyclomatic 13, cognitive 14) REDACTED:335
- Complex function screen (cyclomatic 13, cognitive 13) REDACTED:118
- Complex function empty (cyclomatic 13, cognitive 13) pangu-app-starter/uni_modules/uview-ui/libs/function/test.js:150
- Complex function (anonymous) (cyclomatic 12, cognitive 21) pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:174
- Complex function toText (cyclomatic 12, cognitive 16) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/approver.vue:162
- Complex function queryParams (cyclomatic 12, cognitive 16) REDACTED:400
- Complex function onText (cyclomatic 11, cognitive 22) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:841
- Complex function touchend (cyclomatic 11, cognitive 20) pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js:113
- Complex function getActiveIndex (cyclomatic 11, cognitive 18) pangu-app-starter/uni_modules/uview-ui/components/u-rate/u-rate.vue:211
- Complex function touchmove (cyclomatic 11, cognitive 15) pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js:72
- Complex function (anonymous) (cyclomatic 11, cognitive 13) pangu-app-starter/uni_modules/uview-ui/components/u-upload/utils.js:73
- Complex function openPage (cyclomatic 11, cognitive 10) pangu-app-starter/uni_modules/uview-ui/libs/util/route.js:85
- Complex function (anonymous) (cyclomatic 11, cognitive 9) pangu-app-starter/static/common/js/touch-emulator.js:128
- REDACTED: 1114 lines of code REDACTED:1
- pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js: 888 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:1
- pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue: 725 lines of code pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:1
- REDACTED: 666 lines of code REDACTED:1
- pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue: 557 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue: 535 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue:1
- pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js: 508 lines of code pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:1
- pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue: 465 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue: 460 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue: 429 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue:1
- pangu-admin/pangu-admin-frontend/src/views/vab/form.vue: 405 lines of code pangu-admin/pangu-admin-frontend/src/views/vab/form.vue:1
- pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue: 403 lines of code pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:1
- No typecheck script
- Dead file (~1342 LoC) REDACTED
- Dead file (~1075 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js
- Dead file (~722 LoC) pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue
- Dead file (~546 LoC) pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js
- Dead file (~452 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue
- Dead file (~406 LoC) pangu-admin/pangu-admin-frontend/src/views/vab/form.vue
- Dead file (~382 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue
- Dead file (~373 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue
- Dead file (~355 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-datetime-picker/u-datetime-picker.vue
- Dead file (~354 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue
- Dead file (~350 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue
- Dead file (~342 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue
- Dead file (~330 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue
- Dead file (~323 LoC) pangu-admin/pangu-admin-frontend/src/views/setting/dic/index.vue
- Dead file (~304 LoC) pangu-admin/pangu-admin-frontend/src/utils/db.js
- Dead file (~298 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-tooltip/u-tooltip.vue
- Dead file (~291 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-tabs/u-tabs.vue
- Dead file (~290 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue
- Dead file (~286 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue
- Dead file (~277 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-row-notice/u-row-notice.vue
- Dead file (~270 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js
- Dead file (~268 LoC) pangu-admin/pangu-admin-frontend/src/views/setting/user/index.vue
- Dead file (~264 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-rate/u-rate.vue
- Dead file (~242 LoC) pangu-admin/pangu-admin-frontend/src/components/scFileSelect/index.vue
- Dead file (~239 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue
- Dead file (~238 LoC) pangu-admin/pangu-admin-frontend/src/views/setting/role/user.vue
- Dead file (~235 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-radio/u-radio.vue
- Dead file (~232 LoC) pangu-admin/pangu-admin-frontend/src/views/setting/user/save.vue
- Dead file (~229 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-album/u-album.vue
- Dead file (~225 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-popup/u-popup.vue
- Dead file (~218 LoC) pangu-admin/pangu-admin-frontend/src/components/scWorkflow/nodes/branch.vue
- Dead file (~217 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-car-keyboard/u-car-keyboard.vue
- Dead file (~214 LoC) pangu-app-starter/uni_modules/uview-ui/components/u-icon/icons.js
- Unlisted import '@docusaurus/plugin-content-docs' pangu-website/sidebars.js:14
- Unlisted import '@docusaurus/types' pangu-website/docusaurus.config.js:7
- Unused dependency 'core-js' pangu-admin/pangu-admin-frontend/package.json:15
- Unused dependency '@mdx-js/react' pangu-website/package.json:20
- JavaScript dependencies are not locked pangu-admin/pangu-admin-frontend/package.json:10
Minor — 329 finding(s)
- Orphaned file pangu-app-starter/uni_modules/uview-ui/libs/config/props/noNetwork.js:1
- Orphaned file pangu-admin/pangu-admin-frontend/src/components/scCron/index.vue:1
- Orphaned file REDACTED:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-button/u-button.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-calendar/month.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-upload/u-upload.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-input/u-input.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-datetime-picker/u-datetime-picker.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-index-list/u-index-list.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-parse/node/node.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-number-box/u-number-box.vue:1
- Orphaned file pangu-admin/pangu-admin-frontend/src/components/scTable/index.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-calendar/u-calendar.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue - backup.js:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-checkbox/u-checkbox.vue:1
- Orphaned file pangu-admin/pangu-admin-backend/pangu-admin-system/src/main/java/com/pulanit/pangu/admin/system/service/UserServiceImpl.java:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-loading-icon/u-loading-icon.vue:1
- Orphaned file REDACTED:1
- Orphaned file pangu-app-starter/static/common/js/touch-emulator.js:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-radio/u-radio.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-parse/u-parse.vue:1
- Orphaned file pangu-admin/pangu-admin-frontend/src/components/scFileSelect/index.vue:1
- Orphaned file pangu-admin/pangu-admin-frontend/src/components/scFilterBar/index.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-tabs/u-tabs.vue:1
- Orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-tooltip/u-tooltip.vue:1
- No direct assertions: delAllUsers pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:40
- No direct assertions: delUser pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:35
- No direct assertions: getUser pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:21
- No direct assertions: getUser2 pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:45
- No direct assertions: saveUser pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:29
- No direct assertions: cache pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/ApiBasedDemoServiceTest.java:17
- No direct assertions: aDelete pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:45
- No direct assertions: aInsert pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:35
- No direct assertions: aSelect pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:50
- No direct assertions: aUpdate pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:40
- No direct assertions: bSelect pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:55
- No direct assertions: pageQuery pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:60
- No direct assertions: pageQuery2 pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:65
- No direct assertions: pageQuery3 pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:70
- No direct assertions: doBiz pangu-examples/pangu-examples-lock-redis-based/src/test/java/com/gitee/pulanos/pangu/showcases/lock/redis/service/AnnotationLockServiceTest.java:19
- No direct assertions: doBiz2 pangu-examples/pangu-examples-lock-redis-based/src/test/java/com/gitee/pulanos/pangu/showcases/lock/redis/service/AnnotationLockServiceTest.java:29
- No direct assertions: doBizAgain pangu-examples/pangu-examples-lock-redis-based/src/test/java/com/gitee/pulanos/pangu/showcases/lock/redis/service/AnnotationLockServiceTest.java:24
- No direct assertions: apiLock pangu-examples/pangu-examples-lock-redis-based/src/test/java/com/gitee/pulanos/pangu/showcases/lock/redis/service/ApiLockServiceTest.java:19
- No direct assertions: createOrder pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTablesTest.java:34
- No direct assertions: createUserNoSharding pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTablesTest.java:59
- No direct assertions: routingQuery pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTablesTest.java:46
- No direct assertions: createOrder pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTest.java:35
- No direct assertions: createUserNoSharding pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTest.java:60
- No direct assertions: mergeQuery pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTest.java:73
- No direct assertions: routingQuery pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTest.java:47
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test project verifies nothing: pangu-examples-cache-layering pangu-examples/pangu-examples-cache-layering/src/test/java/com/gitee/pulanos/pangu/showcases/cache/layering/service/AnnotationBasedDemoServiceTest.java:40
- Test project verifies nothing: pangu-examples-crud pangu-examples/pangu-examples-crud/src/test/java/com/gitee/pulanos/pangu/showcases/crud/CrudTest.java:45
- Test project verifies nothing: pangu-examples-lock-redis-based pangu-examples/pangu-examples-lock-redis-based/src/test/java/com/gitee/pulanos/pangu/showcases/lock/redis/service/AnnotationLockServiceTest.java:19
- Test project verifies nothing: pangu-examples-shardingsphere-readwrite-splitting pangu-examples/pangu-examples-shardingsphere-readwrite-splitting/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/ReadWriteSplittingTest.java:78
- Test project verifies nothing: pangu-examples-shardingsphere-sharding pangu-examples/pangu-examples-shardingsphere-sharding/src/test/java/com/gitee/pulanos/pangu/showcases/shardingsphere/sharding/ShardingDatabasesTablesTest.java:34
- Most significant orphaned file REDACTED:1
- Most significant orphaned file pangu-app-starter/uni_modules/uview-ui/components/u-parse/parser.js:1
- Most significant orphaned file pangu-app-starter/uni_modules/uview-ui/libs/util/calendar.js:1
- Duplicated predicate pangu-app-starter/uni_modules/uview-ui/components/u-swipe-action-item/nvue.js:56
- Duplicated predicate pangu-admin/pangu-admin-frontend/src/utils/template.js:10
- Fat interface: UserService (16 abstract methods) pangu-admin/pangu-admin-backend/pangu-admin-system-api/src/main/java/com/pulanit/pangu/admin/system/api/service/UserService.java:18
- Projects may be oversized for their cohesion pangu-app-starter/uni_modules/uview-ui/package.json:1
- High interface indirection
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- REDACTED
- REDACTED
- Thin README README.md:1
- Logging is not universal
- No SAST
- No dependency-update automation pangu-admin/pangu-admin-frontend/package.json:10
- Java packages are not null-marked everywhere
- Silent fallback default in catch REDACTED:78
Minor — 101 finding(s)
- Outdated (provided): org.springframework.boot:spring-boot-autoconfigure
- Outdated (provided): org.apache.tomcat.embed:tomcat-embed-el
- Outdated (provided): org.springframework.boot:spring-boot-starter-tomcat
- Outdated (provided): com.fasterxml.jackson.core:jackson-databind
- Outdated (provided): org.mybatis:mybatis
- Outdated (provided): com.alibaba.nacos:nacos-client
- Outdated (provided): org.slf4j:slf4j-api
- Outdated (provided): org.apache.tomcat.embed:tomcat-embed-websocket
- Outdated (provided): org.apache.commons:commons-lang3
- Outdated (provided): jakarta.annotation:jakarta.annotation-api
- Outdated (provided): com.baomidou:mybatis-plus-core
- Outdated (provided): org.springframework.boot:spring-boot-starter
- Outdated (provided): org.springframework:spring-context
- Outdated (provided): commons-codec:commons-codec
- Outdated (provided): com.baomidou:mybatis-plus-annotation
- Outdated (provided): org.springframework:spring-jdbc
- Outdated (provided): io.prometheus:simpleclient_tracer_otel
- Outdated (provided): org.springframework.boot:spring-boot-starter-jdbc
- Outdated (provided): org.springframework.boot:spring-boot-starter-json
- Outdated (provided): org.springframework:spring-expression
- Outdated (provided): com.fasterxml.jackson.datatype:jackson-datatype-jsr310
- Outdated (provided): org.mybatis:mybatis-spring
- Outdated (provided): org.apache.logging.log4j:log4j-api
- Outdated (provided): org.springframework:spring-jcl
- Outdated (provided): com.alibaba.nacos:nacos-auth-plugin
- Outdated (test): org.mockito:mockito-core
- Outdated (test): org.opentest4j:opentest4j
- Outdated (test): org.ow2.asm:asm
- Outdated (test): org.mockito:mockito-junit-jupiter
- Outdated (test): org.junit.jupiter:junit-jupiter-api
- Outdated (test): jakarta.activation:jakarta.activation-api
- Outdated (test): org.springframework.boot:spring-boot-test
- Outdated (test): org.assertj:assertj-core
- Outdated (test): org.junit.jupiter:junit-jupiter-params
- Outdated (test): com.jayway.jsonpath:json-path
- Outdated (test): org.xmlunit:xmlunit-core
- Outdated (test): org.junit.jupiter:junit-jupiter-engine
- Outdated (test): jakarta.xml.bind:jakarta.xml.bind-api
- Outdated (test): net.minidev:json-smart
- Outdated (test): org.springframework:spring-test
- Outdated (test): org.junit.platform:junit-platform-commons
- Outdated (test): org.springframework.boot:spring-boot-test-autoconfigure
- Outdated (test): org.junit.platform:junit-platform-engine
- Outdated (test): org.junit.jupiter:junit-jupiter
- Outdated (test): net.bytebuddy:byte-buddy
- Outdated (test): net.minidev:accessors-smart
- Outdated (test): org.springframework.boot:spring-boot-starter-test
- Outdated (test): org.hamcrest:hamcrest
- Outdated (test): org.objenesis:objenesis
- Outdated (test): org.skyscreamer:jsonassert
- Outdated (compile): cn.hutool:hutool-all
- Outdated (compile): org.springframework.boot:spring-boot-configuration-processor
- Outdated (compile): com.alibaba.fastjson2:fastjson2
- Outdated (compile): org.projectlombok:lombok
- Outdated (compile): ch.qos.logback:logback-classic
- Outdated (compile): org.eclipse.sisu:org.eclipse.sisu.plexus
- Outdated (compile): org.apache.maven:maven-artifact
- Outdated (compile): com.mysql:mysql-connector-j
- Outdated (compile): org.apache.maven:maven-model
- Outdated (compile): org.eclipse.sisu:org.eclipse.sisu.inject
- Outdated (compile): org.codehaus.plexus:plexus-utils
- Outdated (compile): org.apache.maven:maven-plugin-api
- Outdated (compile): org.codehaus.plexus:plexus-classworlds
- Outdated (compile): javax.enterprise:cdi-api
- Outdated (compile): org.codehaus.plexus:plexus-component-annotations
- doc comments repeat the names pangu-app-starter/static/common/js/touch-emulator.js:43
- doc comments repeat the names pangu-app-starter/uni_modules/uview-ui/libs/luch-request/core/buildFullPath.js:11
- Off the main sequence: pangu-admin-common
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-347ae0858fec41c69760a3df7f953e1b/history.json --exit-code 0 --source . | 4 | 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-347ae0858fec41c69760a3df7f953e1b/history-1.json --exit-code 0 --source . | 8 | 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=1022" --report-format json --report-path /tmp/watchdog-gitleaks-347ae0858fec41c69760a3df7f953e1b/history-2.json --exit-code 0 --source . | 3529 | artifacts/raw/gitleaks-history-2.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-347ae0858fec41c69760a3df7f953e1b/tree.json --exit-code 0 --source . | 2 | 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 . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 119 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |