Executive summary
pingapi/apigo falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 45.2 out of 100 and is rated Weak, and eight of its nine critical findings are security problems.
Production Readiness, at 26.5, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the package under a licence on your banned list, worth about 4.7 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 5.5 points. Raising Production Readiness to 70 would lift the score to about 60.5.
Four passwords or keys are open to anyone who can read the repository. Three settings leave the servers or containers unsafe, and one known security hole in a package the code depends on can be used by attackers. Replacing each exposed password or key, correcting the unsafe settings and updating the vulnerable packages would close these risks. The package under a licence on your banned list needs replacing, or clearing with your legal team.
The product code is 16,590 lines, about €17,000 to rebuild.
If Production Readiness rose from 26.5 to 70, the lowest score rated Strong, the score would rise from 45.2 to about 60.5.
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,700 to €29,000, for 95 to 300 hours of work, about 0.1 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 45. 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 | Small: 16,590 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 apigo-api.apigo-core.src.main.resources.static.assets | 2 cn.crabc.core.admin | 3 cn.crabc.core.admin.config | 4 cn.crabc.core.app.enums | 5 cn.crabc.core.app.mcp.auth | 6 cn.crabc.core.app.mcp.support | 7 cn.crabc.core.app.support | 8 cn.crabc.core.datasource.config | 9 cn.crabc.core.datasource.constant | 10 cn.crabc.core.datasource.enums | 11 cn.crabc.core.datasource.exception | 12 cn.crabc.core.datasource.interceptor | 13 cn.crabc.core.datasource.mapper | 14 cn.crabc.core.datasource.util | 15 cn.crabc.core.plugin | 16 cn.crabc.core.plugin.util | 17 cn.crabc.core.spi.bean | 18 cn.crabc.core.starter | 19 cn.crabc.core.app.entity | 20 cn.crabc.core.app.mcp.config | 21 cn.crabc.core.plugin.impl | 22 cn.crabc.core.spi | 23 cn.crabc.core.app.entity.dto | 24 cn.crabc.core.app.entity.param | 25 cn.crabc.core.app.entity.vo | 26 cn.crabc.core.datasource.driver | 27 cn.crabc.core.datasource.driver.jdbc | 28 cn.crabc.core.app.mapper | 29 cn.crabc.core.app.service.core | 30 cn.crabc.core.app.service.system | 31 cn.crabc.core.app.mcp.tools | 32 cn.crabc.core.app.service.core.impl | 33 cn.crabc.core.app.service.system.impl | 34 cn.crabc.core.app.filter | 35 cn.crabc.core.app.config | 36 cn.crabc.core.app.util | 37 cn.crabc.core.app.api | 38 cn.crabc.core.app.controller | 39 cn.crabc.core.app.exception |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 apigo-api.apigo-core.src.main.resources.static.assets | |||||||||||||||||||||||||||||||||||||||
| 2 cn.crabc.core.admin | |||||||||||||||||||||||||||||||||||||||
| 3 cn.crabc.core.admin.config | |||||||||||||||||||||||||||||||||||||||
| 4 cn.crabc.core.app.enums | |||||||||||||||||||||||||||||||||||||||
| 5 cn.crabc.core.app.mcp.auth | |||||||||||||||||||||||||||||||||||||||
| 6 cn.crabc.core.app.mcp.support | |||||||||||||||||||||||||||||||||||||||
| 7 cn.crabc.core.app.support | |||||||||||||||||||||||||||||||||||||||
| 8 cn.crabc.core.datasource.config | |||||||||||||||||||||||||||||||||||||||
| 9 cn.crabc.core.datasource.constant | |||||||||||||||||||||||||||||||||||||||
| 10 cn.crabc.core.datasource.enums | |||||||||||||||||||||||||||||||||||||||
| 11 cn.crabc.core.datasource.exception | |||||||||||||||||||||||||||||||||||||||
| 12 cn.crabc.core.datasource.interceptor | |||||||||||||||||||||||||||||||||||||||
| 13 cn.crabc.core.datasource.mapper | |||||||||||||||||||||||||||||||||||||||
| 14 cn.crabc.core.datasource.util | |||||||||||||||||||||||||||||||||||||||
| 15 cn.crabc.core.plugin | |||||||||||||||||||||||||||||||||||||||
| 16 cn.crabc.core.plugin.util | |||||||||||||||||||||||||||||||||||||||
| 17 cn.crabc.core.spi.bean | |||||||||||||||||||||||||||||||||||||||
| 18 cn.crabc.core.starter | |||||||||||||||||||||||||||||||||||||||
| 19 cn.crabc.core.app.entity | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 cn.crabc.core.app.mcp.config | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 cn.crabc.core.plugin.impl | 4 | ||||||||||||||||||||||||||||||||||||||
| 22 cn.crabc.core.spi | 4 | ||||||||||||||||||||||||||||||||||||||
| 23 cn.crabc.core.app.entity.dto | 3 | ||||||||||||||||||||||||||||||||||||||
| 24 cn.crabc.core.app.entity.param | 3 | ||||||||||||||||||||||||||||||||||||||
| 25 cn.crabc.core.app.entity.vo | 5 | ||||||||||||||||||||||||||||||||||||||
| 26 cn.crabc.core.datasource.driver | 1 | 3 | |||||||||||||||||||||||||||||||||||||
| 27 cn.crabc.core.datasource.driver.jdbc | 2 | 1 | 5 | 5 | |||||||||||||||||||||||||||||||||||
| 28 cn.crabc.core.app.mapper | 1 | 8 | 1 | 1 | 8 | ||||||||||||||||||||||||||||||||||
| 29 cn.crabc.core.app.service.core | 3 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 30 cn.crabc.core.app.service.system | 5 | 1 | 7 | 1 | 3 | 10 | |||||||||||||||||||||||||||||||||
| 31 cn.crabc.core.app.mcp.tools | 7 | 1 | 1 | 5 | 1 | 4 | 1 | 2 | 9 | ||||||||||||||||||||||||||||||
| 32 cn.crabc.core.app.service.core.impl | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 33 cn.crabc.core.app.service.system.impl | 1 | 5 | 1 | 2 | 8 | 4 | 3 | 12 | 1 | 11 | 1 | 7 | 4 | ||||||||||||||||||||||||||
| 34 cn.crabc.core.app.filter | 1 | 3 | 1 | 1 | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 35 cn.crabc.core.app.config | 1 | 1 | 1 | 1 | 1 | 1 | 4 | 1 | |||||||||||||||||||||||||||||||
| 36 cn.crabc.core.app.util | 4 | 2 | 1 | 4 | 1 | ||||||||||||||||||||||||||||||||||
| 37 cn.crabc.core.app.api | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 38 cn.crabc.core.app.controller | 1 | 5 | 5 | 2 | 2 | 10 | 12 | ||||||||||||||||||||||||||||||||
| 39 cn.crabc.core.app.exception | 1 | 1 | 1 | 1 |
19→17 cn.crabc.core.app.entity uses cn.crabc.core.spi.bean✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.entity uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.entity.BaseDatasource→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.app.entity uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.entity, while a change to cn.crabc.core.app.entity can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.entity uses a module listed above it, which is the healthy direction.
20→5 cn.crabc.core.app.mcp.config uses cn.crabc.core.app.mcp.auth✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mcp.config uses a type in cn.crabc.core.app.mcp.auth.
- The types involved
cn.crabc.core.app.mcp.config.McpConfig→cn.crabc.core.app.mcp.auth.McpTokenFilter
- Direction
- cn.crabc.core.app.mcp.config uses cn.crabc.core.app.mcp.auth, so a change to cn.crabc.core.app.mcp.auth can break cn.crabc.core.app.mcp.config, while a change to cn.crabc.core.app.mcp.config can't break cn.crabc.core.app.mcp.auth.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.config uses a module listed above it, which is the healthy direction.
21→15 cn.crabc.core.plugin.impl uses cn.crabc.core.plugin✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.plugin.impl uses a type in cn.crabc.core.plugin.
- The types involved
cn.crabc.core.plugin.impl.DataProcessPlugin→cn.crabc.core.plugin.DataPlugincn.crabc.core.plugin.impl.FieldMappingPlugin→cn.crabc.core.plugin.DataPlugincn.crabc.core.plugin.impl.SingleObjectPlugin→cn.crabc.core.plugin.DataPlugincn.crabc.core.plugin.impl.TreeTransformPlugin→cn.crabc.core.plugin.DataPlugin
- Direction
- cn.crabc.core.plugin.impl uses cn.crabc.core.plugin, so a change to cn.crabc.core.plugin can break cn.crabc.core.plugin.impl, while a change to cn.crabc.core.plugin.impl can't break cn.crabc.core.plugin.
- Position
- Below the diagonal: cn.crabc.core.plugin.impl uses a module listed above it, which is the healthy direction.
22→17 cn.crabc.core.spi uses cn.crabc.core.spi.bean✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.spi uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.spi.DataSourceDriver→cn.crabc.core.spi.bean.BaseDataSourcecn.crabc.core.spi.MetaDataMapper→cn.crabc.core.spi.bean.Columncn.crabc.core.spi.MetaDataMapper→cn.crabc.core.spi.bean.Schemacn.crabc.core.spi.MetaDataMapper→cn.crabc.core.spi.bean.Table
- Direction
- cn.crabc.core.spi uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.spi, while a change to cn.crabc.core.spi can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.spi uses a module listed above it, which is the healthy direction.
23→19 cn.crabc.core.app.entity.dto uses cn.crabc.core.app.entity✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.entity.dto uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.entity.dto.ApiInfoDTO→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.entity.dto.ApiInfoDTO→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.entity.dto.ApiInfoDTO→cn.crabc.core.app.entity.BaseApp
- Direction
- cn.crabc.core.app.entity.dto uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.entity.dto, while a change to cn.crabc.core.app.entity.dto can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.entity.dto uses a module listed above it, which is the healthy direction.
24→19 cn.crabc.core.app.entity.param uses cn.crabc.core.app.entity✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.entity.param uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.entity.param.ApiInfoParam→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.entity.param.ApiInfoParam→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.entity.param.ApiInfoParam→cn.crabc.core.app.entity.BaseApiSql
- Direction
- cn.crabc.core.app.entity.param uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.entity.param, while a change to cn.crabc.core.app.entity.param can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.entity.param uses a module listed above it, which is the healthy direction.
25→19 cn.crabc.core.app.entity.vo uses cn.crabc.core.app.entity✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.entity.vo uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.entity.vo.ApiInfoVO→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.entity.vo.ApiInfoVO→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.entity.vo.ApiInfoVO→cn.crabc.core.app.entity.BaseApiSqlcn.crabc.core.app.entity.vo.BaseApiInfoVO→cn.crabc.core.app.entity.BaseEntitycn.crabc.core.app.entity.vo.BaseGroupVO→cn.crabc.core.app.entity.BaseGroup
- Direction
- cn.crabc.core.app.entity.vo uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.entity.vo, while a change to cn.crabc.core.app.entity.vo can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.entity.vo uses a module listed above it, which is the healthy direction.
26→17 cn.crabc.core.datasource.driver uses cn.crabc.core.spi.bean✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.datasource.driver uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.datasource.driver.DataSourceManager→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.datasource.driver uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.datasource.driver, while a change to cn.crabc.core.datasource.driver can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver uses a module listed above it, which is the healthy direction.
26→22 cn.crabc.core.datasource.driver uses cn.crabc.core.spi✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.datasource.driver uses a type in cn.crabc.core.spi.
- The types involved
cn.crabc.core.datasource.driver.DataSourceManager→cn.crabc.core.spi.DataSourceDrivercn.crabc.core.datasource.driver.DataSourceManager→cn.crabc.core.spi.MetaDataMappercn.crabc.core.datasource.driver.DataSourceManager→cn.crabc.core.spi.StatementMapper
- Direction
- cn.crabc.core.datasource.driver uses cn.crabc.core.spi, so a change to cn.crabc.core.spi can break cn.crabc.core.datasource.driver, while a change to cn.crabc.core.datasource.driver can't break cn.crabc.core.spi.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver uses a module listed above it, which is the healthy direction.
27→13 cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.datasource.mapper✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.datasource.driver.jdbc uses a type in cn.crabc.core.datasource.mapper.
- The types involved
cn.crabc.core.datasource.driver.jdbc.JdbcDataSourceDriver→cn.crabc.core.datasource.mapper.BaseDataHandleMappercn.crabc.core.datasource.driver.jdbc.JdbcStatement→cn.crabc.core.datasource.mapper.BaseDataHandleMapper
- Direction
- cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.datasource.mapper, so a change to cn.crabc.core.datasource.mapper can break cn.crabc.core.datasource.driver.jdbc, while a change to cn.crabc.core.datasource.driver.jdbc can't break cn.crabc.core.datasource.mapper.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver.jdbc uses a module listed above it, which is the healthy direction.
27→14 cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.datasource.util✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.datasource.driver.jdbc uses a type in cn.crabc.core.datasource.util.
- The types involved
cn.crabc.core.datasource.driver.jdbc.JdbcStatement→cn.crabc.core.datasource.util.PageInfo
- Direction
- cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.datasource.util, so a change to cn.crabc.core.datasource.util can break cn.crabc.core.datasource.driver.jdbc, while a change to cn.crabc.core.datasource.driver.jdbc can't break cn.crabc.core.datasource.util.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver.jdbc uses a module listed above it, which is the healthy direction.
27→17 cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.spi.bean✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.datasource.driver.jdbc uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.datasource.driver.jdbc.DefaultDataSourceDriver→cn.crabc.core.spi.bean.BaseDataSourcecn.crabc.core.datasource.driver.jdbc.DuckDbDataSource→cn.crabc.core.spi.bean.BaseDataSourcecn.crabc.core.datasource.driver.jdbc.JdbcMetaData→cn.crabc.core.spi.bean.Columncn.crabc.core.datasource.driver.jdbc.JdbcMetaData→cn.crabc.core.spi.bean.Schemacn.crabc.core.datasource.driver.jdbc.JdbcMetaData→cn.crabc.core.spi.bean.Table
- Direction
- cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.datasource.driver.jdbc, while a change to cn.crabc.core.datasource.driver.jdbc can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver.jdbc uses a module listed above it, which is the healthy direction.
27→22 cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.spi✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.datasource.driver.jdbc uses a type in cn.crabc.core.spi.
- The types involved
cn.crabc.core.datasource.driver.jdbc.DefaultDataSourceDriver→cn.crabc.core.spi.DataSourceDrivercn.crabc.core.datasource.driver.jdbc.JdbcDataSourceDriver→cn.crabc.core.spi.MetaDataMappercn.crabc.core.datasource.driver.jdbc.JdbcDataSourceDriver→cn.crabc.core.spi.StatementMappercn.crabc.core.datasource.driver.jdbc.JdbcMetaData→cn.crabc.core.spi.MetaDataMappercn.crabc.core.datasource.driver.jdbc.JdbcStatement→cn.crabc.core.spi.StatementMapper
- Direction
- cn.crabc.core.datasource.driver.jdbc uses cn.crabc.core.spi, so a change to cn.crabc.core.spi can break cn.crabc.core.datasource.driver.jdbc, while a change to cn.crabc.core.datasource.driver.jdbc can't break cn.crabc.core.spi.
- Position
- Below the diagonal: cn.crabc.core.datasource.driver.jdbc uses a module listed above it, which is the healthy direction.
28→17 cn.crabc.core.app.mapper uses cn.crabc.core.spi.bean✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mapper uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.mapper.BaseDataSourceMapper→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.app.mapper uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.mapper, while a change to cn.crabc.core.app.mapper can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.mapper uses a module listed above it, which is the healthy direction.
28→19 cn.crabc.core.app.mapper uses cn.crabc.core.app.entity✕
- Connections
- 8 pairs of types, where a type in cn.crabc.core.app.mapper uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.mapper.BaseApiInfoMapper→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.mapper.BaseApiLogMapper→cn.crabc.core.app.entity.BaseApiLogcn.crabc.core.app.mapper.BaseApiParamMapper→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.mapper.BaseAppApiMapper→cn.crabc.core.app.entity.BaseAppApicn.crabc.core.app.mapper.BaseAppMapper→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.mapper.BaseDataSourceMapper→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.mapper.BaseGroupMapper→cn.crabc.core.app.entity.BaseGroupcn.crabc.core.app.mapper.BaseUserMapper→cn.crabc.core.app.entity.BaseUser
- Direction
- cn.crabc.core.app.mapper uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.mapper, while a change to cn.crabc.core.app.mapper can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.mapper uses a module listed above it, which is the healthy direction.
28→23 cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.dto✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mapper uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.mapper.BaseApiInfoMapper→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.mapper, while a change to cn.crabc.core.app.mapper can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.mapper uses a module listed above it, which is the healthy direction.
28→24 cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.param✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mapper uses a type in cn.crabc.core.app.entity.param.
- The types involved
cn.crabc.core.app.mapper.BaseApiLogMapper→cn.crabc.core.app.entity.param.ApiLogParam
- Direction
- cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.param, so a change to cn.crabc.core.app.entity.param can break cn.crabc.core.app.mapper, while a change to cn.crabc.core.app.mapper can't break cn.crabc.core.app.entity.param.
- Position
- Below the diagonal: cn.crabc.core.app.mapper uses a module listed above it, which is the healthy direction.
28→25 cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.vo✕
- Connections
- 8 pairs of types, where a type in cn.crabc.core.app.mapper uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.mapper.BaseApiInfoMapper→cn.crabc.core.app.entity.vo.ApiComboBoxVOcn.crabc.core.app.mapper.BaseApiInfoMapper→cn.crabc.core.app.entity.vo.BaseApiInfoVOcn.crabc.core.app.mapper.BaseApiLogMapper→cn.crabc.core.app.entity.vo.ApiLogDailyTrendVOcn.crabc.core.app.mapper.BaseApiLogMapper→cn.crabc.core.app.entity.vo.ApiLogGroupCountVOcn.crabc.core.app.mapper.BaseApiLogMapper→cn.crabc.core.app.entity.vo.ApiLogSummaryVOcn.crabc.core.app.mapper.BaseApiParamMapper→cn.crabc.core.app.entity.vo.RequestParamsVOcn.crabc.core.app.mapper.BaseGroupMapper→cn.crabc.core.app.entity.vo.BaseGroupVOcn.crabc.core.app.mapper.BaseGroupMapper→cn.crabc.core.app.entity.vo.GroupApiVO
- Direction
- cn.crabc.core.app.mapper uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.mapper, while a change to cn.crabc.core.app.mapper can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.mapper uses a module listed above it, which is the healthy direction.
29→17 cn.crabc.core.app.service.core uses cn.crabc.core.spi.bean✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.service.core uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.service.core.IBaseDataService→cn.crabc.core.spi.bean.BaseDataSourcecn.crabc.core.app.service.core.MetaDataQueryService→cn.crabc.core.spi.bean.Columncn.crabc.core.app.service.core.MetaDataQueryService→cn.crabc.core.spi.bean.Table
- Direction
- cn.crabc.core.app.service.core uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.service.core, while a change to cn.crabc.core.app.service.core can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.service.core uses a module listed above it, which is the healthy direction.
29→25 cn.crabc.core.app.service.core uses cn.crabc.core.app.entity.vo✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.service.core.IBaseDataService→cn.crabc.core.app.entity.vo.PreviewVO
- Direction
- cn.crabc.core.app.service.core uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.service.core, while a change to cn.crabc.core.app.service.core can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.service.core uses a module listed above it, which is the healthy direction.
29→26 cn.crabc.core.app.service.core uses cn.crabc.core.datasource.driver✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core uses a type in cn.crabc.core.datasource.driver.
- The types involved
cn.crabc.core.app.service.core.MetaDataQueryService→cn.crabc.core.datasource.driver.DataSourceManager
- Direction
- cn.crabc.core.app.service.core uses cn.crabc.core.datasource.driver, so a change to cn.crabc.core.datasource.driver can break cn.crabc.core.app.service.core, while a change to cn.crabc.core.app.service.core can't break cn.crabc.core.datasource.driver.
- Position
- Below the diagonal: cn.crabc.core.app.service.core uses a module listed above it, which is the healthy direction.
30→14 cn.crabc.core.app.service.system uses cn.crabc.core.datasource.util✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.datasource.util.
- The types involved
cn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.IBaseAppService→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.IBaseDataSourceService→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.IBaseUserService→cn.crabc.core.datasource.util.PageInfo
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.datasource.util, so a change to cn.crabc.core.datasource.util can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.datasource.util.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
30→17 cn.crabc.core.app.service.system uses cn.crabc.core.spi.bean✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.service.system.IBaseDataSourceService→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
30→19 cn.crabc.core.app.service.system uses cn.crabc.core.app.entity✕
- Connections
- 7 pairs of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.BaseAppApicn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.BaseApiLogcn.crabc.core.app.service.system.IBaseAppService→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.service.system.IBaseDataSourceService→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.service.system.IBaseGroupService→cn.crabc.core.app.entity.BaseGroupcn.crabc.core.app.service.system.IBaseUserService→cn.crabc.core.app.entity.BaseUser
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
30→23 cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.dto✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
30→24 cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.param✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.app.entity.param.
- The types involved
cn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.param.ApiInfoParamcn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.param.ApiRateLimitParamcn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.param.ApiLogParam
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.param, so a change to cn.crabc.core.app.entity.param can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.app.entity.param.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
30→25 cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.vo✕
- Connections
- 10 pairs of types, where a type in cn.crabc.core.app.service.system uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.vo.ApiComboBoxVOcn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.vo.ApiInfoVOcn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.vo.ApiRateLimitVOcn.crabc.core.app.service.system.IBaseApiInfoService→cn.crabc.core.app.entity.vo.BaseApiInfoVOcn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.vo.ApiLogDailyTrendVOcn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.vo.ApiLogGroupCountVOcn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.vo.ApiLogStatisticsVOcn.crabc.core.app.service.system.IBaseApiLogService→cn.crabc.core.app.entity.vo.ApiLogSummaryVOcn.crabc.core.app.service.system.IBaseApiParamService→cn.crabc.core.app.entity.vo.ApiParamsVOcn.crabc.core.app.service.system.IBaseGroupService→cn.crabc.core.app.entity.vo.BaseGroupVO
- Direction
- cn.crabc.core.app.service.system uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.service.system, while a change to cn.crabc.core.app.service.system can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.service.system uses a module listed above it, which is the healthy direction.
31→6 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.mcp.support✕
- Connections
- 7 pairs of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.mcp.support.
- The types involved
cn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.ApiOpsTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.AppTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.DataSourceTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.GroupTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.LogTools→cn.crabc.core.app.mcp.support.McpToolSupportcn.crabc.core.app.mcp.tools.MetaDataTools→cn.crabc.core.app.mcp.support.McpToolSupport
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.mcp.support, so a change to cn.crabc.core.app.mcp.support can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.mcp.support.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→7 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.support✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.support.
- The types involved
cn.crabc.core.app.mcp.tools.DataSourceTools→cn.crabc.core.app.support.DatasourceGuard
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.support, so a change to cn.crabc.core.app.support can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.support.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→14 cn.crabc.core.app.mcp.tools uses cn.crabc.core.datasource.util✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.datasource.util.
- The types involved
cn.crabc.core.app.mcp.tools.DataSourceTools→cn.crabc.core.datasource.util.PageInfo
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.datasource.util, so a change to cn.crabc.core.datasource.util can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.datasource.util.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→19 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.mcp.tools.DataSourceTools→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.mcp.tools.LogTools→cn.crabc.core.app.entity.BaseApiLog
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→24 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity.param✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.entity.param.
- The types involved
cn.crabc.core.app.mcp.tools.LogTools→cn.crabc.core.app.entity.param.ApiLogParam
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity.param, so a change to cn.crabc.core.app.entity.param can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.entity.param.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→25 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity.vo✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.entity.vo.ColumnParseVocn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.entity.vo.SqlParseVOcn.crabc.core.app.mcp.tools.ApiOpsTools→cn.crabc.core.app.entity.vo.ApiInfoVOcn.crabc.core.app.mcp.tools.GroupTools→cn.crabc.core.app.entity.vo.BaseGroupVO
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→26 cn.crabc.core.app.mcp.tools uses cn.crabc.core.datasource.driver✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.datasource.driver.
- The types involved
cn.crabc.core.app.mcp.tools.MetaDataTools→cn.crabc.core.datasource.driver.DataSourceManager
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.datasource.driver, so a change to cn.crabc.core.datasource.driver can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.datasource.driver.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→29 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.service.core✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.service.core.
- The types involved
cn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.service.core.IBaseDataServicecn.crabc.core.app.mcp.tools.ApiOpsTools→cn.crabc.core.app.service.core.IBaseDataService
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.service.core, so a change to cn.crabc.core.app.service.core can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.service.core.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
31→30 cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.service.system✕
- Connections
- 9 pairs of types, where a type in cn.crabc.core.app.mcp.tools uses a type in cn.crabc.core.app.service.system.
- The types involved
cn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.mcp.tools.ApiDevTools→cn.crabc.core.app.service.system.IBaseDataSourceServicecn.crabc.core.app.mcp.tools.ApiOpsTools→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.mcp.tools.AppTools→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.mcp.tools.AppTools→cn.crabc.core.app.service.system.IBaseAppServicecn.crabc.core.app.mcp.tools.DataSourceTools→cn.crabc.core.app.service.system.IBaseDataSourceServicecn.crabc.core.app.mcp.tools.GroupTools→cn.crabc.core.app.service.system.IBaseGroupServicecn.crabc.core.app.mcp.tools.LogTools→cn.crabc.core.app.service.system.IBaseApiLogServicecn.crabc.core.app.mcp.tools.MetaDataTools→cn.crabc.core.app.service.system.IBaseDataSourceService
- Direction
- cn.crabc.core.app.mcp.tools uses cn.crabc.core.app.service.system, so a change to cn.crabc.core.app.service.system can break cn.crabc.core.app.mcp.tools, while a change to cn.crabc.core.app.mcp.tools can't break cn.crabc.core.app.service.system.
- Position
- Below the diagonal: cn.crabc.core.app.mcp.tools uses a module listed above it, which is the healthy direction.
32→17 cn.crabc.core.app.service.core.impl uses cn.crabc.core.spi.bean✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core.impl uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.service.core.impl.BaseDataServiceImpl→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.app.service.core.impl uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.service.core.impl, while a change to cn.crabc.core.app.service.core.impl can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.service.core.impl uses a module listed above it, which is the healthy direction.
32→25 cn.crabc.core.app.service.core.impl uses cn.crabc.core.app.entity.vo✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core.impl uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.service.core.impl.BaseDataServiceImpl→cn.crabc.core.app.entity.vo.PreviewVO
- Direction
- cn.crabc.core.app.service.core.impl uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.service.core.impl, while a change to cn.crabc.core.app.service.core.impl can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.service.core.impl uses a module listed above it, which is the healthy direction.
32→26 cn.crabc.core.app.service.core.impl uses cn.crabc.core.datasource.driver✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core.impl uses a type in cn.crabc.core.datasource.driver.
- The types involved
cn.crabc.core.app.service.core.impl.BaseDataServiceImpl→cn.crabc.core.datasource.driver.DataSourceManager
- Direction
- cn.crabc.core.app.service.core.impl uses cn.crabc.core.datasource.driver, so a change to cn.crabc.core.datasource.driver can break cn.crabc.core.app.service.core.impl, while a change to cn.crabc.core.app.service.core.impl can't break cn.crabc.core.datasource.driver.
- Position
- Below the diagonal: cn.crabc.core.app.service.core.impl uses a module listed above it, which is the healthy direction.
32→29 cn.crabc.core.app.service.core.impl uses cn.crabc.core.app.service.core✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.core.impl uses a type in cn.crabc.core.app.service.core.
- The types involved
cn.crabc.core.app.service.core.impl.BaseDataServiceImpl→cn.crabc.core.app.service.core.IBaseDataService
- Direction
- cn.crabc.core.app.service.core.impl uses cn.crabc.core.app.service.core, so a change to cn.crabc.core.app.service.core can break cn.crabc.core.app.service.core.impl, while a change to cn.crabc.core.app.service.core.impl can't break cn.crabc.core.app.service.core.
- Position
- Below the diagonal: cn.crabc.core.app.service.core.impl uses a module listed above it, which is the healthy direction.
33→7 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.support✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.support.
- The types involved
cn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.support.DatasourceGuard
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.support, so a change to cn.crabc.core.app.support can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.support.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→14 cn.crabc.core.app.service.system.impl uses cn.crabc.core.datasource.util✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.datasource.util.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.impl.BaseUserServiceImpl→cn.crabc.core.datasource.util.PageInfocn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.datasource.util.PageInfo
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.datasource.util, so a change to cn.crabc.core.datasource.util can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.datasource.util.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→15 cn.crabc.core.app.service.system.impl uses cn.crabc.core.plugin✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.plugin.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.plugin.DataPluginConfigValidator
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.plugin, so a change to cn.crabc.core.plugin can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.plugin.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→17 cn.crabc.core.app.service.system.impl uses cn.crabc.core.spi.bean✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.spi.bean.
- The types involved
cn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.spi.bean.BaseDataSourcecn.crabc.core.app.service.system.impl.DataSourceIdentity→cn.crabc.core.spi.bean.BaseDataSource
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.spi.bean, so a change to cn.crabc.core.spi.bean can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.spi.bean.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→19 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity✕
- Connections
- 8 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.BaseApiParamcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.BaseAppApicn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.entity.BaseGroupcn.crabc.core.app.service.system.impl.BaseUserServiceImpl→cn.crabc.core.app.entity.BaseUsercn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.BaseApiLog
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→23 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.dto✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.service.system.impl.ApiRateLimitService→cn.crabc.core.app.entity.dto.ApiInfoDTOcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.dto.ApiInfoDTOcn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.app.entity.dto.ApiInfoDTOcn.crabc.core.app.service.system.impl.BucketEntry→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→24 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.param✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.entity.param.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.param.ApiInfoParamcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.param.ApiRateLimitParamcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.param.ApiLogParam
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.param, so a change to cn.crabc.core.app.entity.param can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.entity.param.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→25 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.vo✕
- Connections
- 12 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.vo.ApiComboBoxVOcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.vo.ApiInfoVOcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.vo.ApiRateLimitVOcn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.entity.vo.BaseApiInfoVOcn.crabc.core.app.service.system.impl.BaseApiParamServiceImpl→cn.crabc.core.app.entity.vo.ApiParamsVOcn.crabc.core.app.service.system.impl.BaseApiParamServiceImpl→cn.crabc.core.app.entity.vo.RequestParamsVOcn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.entity.vo.ApiComboBoxVOcn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.entity.vo.BaseGroupVOcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.vo.ApiLogDailyTrendVOcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.vo.ApiLogGroupCountVOcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.vo.ApiLogStatisticsVOcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.entity.vo.ApiLogSummaryVO
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→26 cn.crabc.core.app.service.system.impl uses cn.crabc.core.datasource.driver✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.datasource.driver.
- The types involved
cn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.datasource.driver.DataSourceManager
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.datasource.driver, so a change to cn.crabc.core.datasource.driver can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.datasource.driver.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→28 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.mapper✕
- Connections
- 11 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.mapper.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.mapper.BaseApiInfoMappercn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.mapper.BaseApiParamMappercn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.mapper.BaseAppApiMappercn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.mapper.BaseAppMappercn.crabc.core.app.service.system.impl.BaseApiParamServiceImpl→cn.crabc.core.app.mapper.BaseApiParamMappercn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.app.mapper.BaseAppMappercn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.mapper.BaseDataSourceMappercn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.mapper.BaseApiInfoMappercn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.mapper.BaseGroupMappercn.crabc.core.app.service.system.impl.BaseUserServiceImpl→cn.crabc.core.app.mapper.BaseUserMappercn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.mapper.BaseApiLogMapper
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.mapper, so a change to cn.crabc.core.app.mapper can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.mapper.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→29 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.service.core✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.service.core.
- The types involved
cn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.service.core.IBaseDataService
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.service.core, so a change to cn.crabc.core.app.service.core can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.service.core.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→30 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.service.system✕
- Connections
- 7 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.service.system.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.service.system.impl.BaseApiParamServiceImpl→cn.crabc.core.app.service.system.IBaseApiParamServicecn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.app.service.system.IBaseAppServicecn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.service.system.IBaseDataSourceServicecn.crabc.core.app.service.system.impl.BaseGroupServiceImpl→cn.crabc.core.app.service.system.IBaseGroupServicecn.crabc.core.app.service.system.impl.BaseUserServiceImpl→cn.crabc.core.app.service.system.IBaseUserServicecn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.service.system.IBaseApiLogService
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.service.system, so a change to cn.crabc.core.app.service.system can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.service.system.
- Position
- Below the diagonal: cn.crabc.core.app.service.system.impl uses a module listed above it, which is the healthy direction.
33→36 cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.util part of a loop✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.service.system.impl uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.service.system.impl.BaseApiInfoServiceImpl→cn.crabc.core.app.util.ResourceOwnerGuardcn.crabc.core.app.service.system.impl.BaseAppServiceImpl→cn.crabc.core.app.util.ResourceOwnerGuardcn.crabc.core.app.service.system.impl.BaseDataSourceServiceImpl→cn.crabc.core.app.util.ResourceOwnerGuardcn.crabc.core.app.service.system.impl.IBaseApiLogServiceImpl→cn.crabc.core.app.util.ResourceOwnerGuard
- Direction
- cn.crabc.core.app.service.system.impl uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.service.system.impl, while a change to cn.crabc.core.app.service.system.impl can't break cn.crabc.core.app.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
34→11 cn.crabc.core.app.filter uses cn.crabc.core.datasource.exception✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.datasource.exception.
- The types involved
cn.crabc.core.app.filter.JwtInterceptor→cn.crabc.core.datasource.exception.CustomException
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.datasource.exception, so a change to cn.crabc.core.datasource.exception can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.datasource.exception.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→19 cn.crabc.core.app.filter uses cn.crabc.core.app.entity✕
- Connections
- 3 pairs of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.entity.BaseApiLogcn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.filter.LogEntry→cn.crabc.core.app.entity.BaseApiLog
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→23 cn.crabc.core.app.filter uses cn.crabc.core.app.entity.dto✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→28 cn.crabc.core.app.filter uses cn.crabc.core.app.mapper✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.mapper.
- The types involved
cn.crabc.core.app.filter.JwtInterceptor→cn.crabc.core.app.mapper.BaseUserMapper
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.mapper, so a change to cn.crabc.core.app.mapper can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.mapper.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→30 cn.crabc.core.app.filter uses cn.crabc.core.app.service.system✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.service.system.
- The types involved
cn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.service.system.IBaseApiLogService
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.service.system, so a change to cn.crabc.core.app.service.system can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.service.system.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→33 cn.crabc.core.app.filter uses cn.crabc.core.app.service.system.impl✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.service.system.impl.
- The types involved
cn.crabc.core.app.filter.AuthInterceptor→cn.crabc.core.app.service.system.impl.ApiRateLimitService
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.service.system.impl, so a change to cn.crabc.core.app.service.system.impl can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.service.system.impl.
- Position
- Below the diagonal: cn.crabc.core.app.filter uses a module listed above it, which is the healthy direction.
34→36 cn.crabc.core.app.filter uses cn.crabc.core.app.util part of a loop✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.filter uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.filter.JwtInterceptor→cn.crabc.core.app.util.JwtUtil
- Direction
- cn.crabc.core.app.filter uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.filter, while a change to cn.crabc.core.app.filter can't break cn.crabc.core.app.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
35→8 cn.crabc.core.app.config uses cn.crabc.core.datasource.config✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.datasource.config.
- The types involved
cn.crabc.core.app.config.DataSourceConfig→cn.crabc.core.datasource.config.JdbcDataSourceRouter
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.datasource.config, so a change to cn.crabc.core.datasource.config can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.datasource.config.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→13 cn.crabc.core.app.config uses cn.crabc.core.datasource.mapper✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.datasource.mapper.
- The types involved
cn.crabc.core.app.config.DataSourceConfig→cn.crabc.core.datasource.mapper.BaseDataHandleMapper
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.datasource.mapper, so a change to cn.crabc.core.datasource.mapper can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.datasource.mapper.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→22 cn.crabc.core.app.config uses cn.crabc.core.spi✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.spi.
- The types involved
cn.crabc.core.app.config.DataSourceConfig→cn.crabc.core.spi.DataSourceDriver
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.spi, so a change to cn.crabc.core.spi can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.spi.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→23 cn.crabc.core.app.config uses cn.crabc.core.app.entity.dto✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.config.CacheConfig→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→26 cn.crabc.core.app.config uses cn.crabc.core.datasource.driver✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.datasource.driver.
- The types involved
cn.crabc.core.app.config.DataSourceConfig→cn.crabc.core.datasource.driver.DataSourceManager
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.datasource.driver, so a change to cn.crabc.core.datasource.driver can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.datasource.driver.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→28 cn.crabc.core.app.config uses cn.crabc.core.app.mapper✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.app.mapper.
- The types involved
cn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.mapper.BaseUserMapper
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.app.mapper, so a change to cn.crabc.core.app.mapper can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.app.mapper.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→34 cn.crabc.core.app.config uses cn.crabc.core.app.filter✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.app.filter.
- The types involved
cn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.filter.ApiFiltercn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.filter.AuthInterceptorcn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.filter.JwtInterceptorcn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.filter.UserContextFilter
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.app.filter, so a change to cn.crabc.core.app.filter can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.app.filter.
- Position
- Below the diagonal: cn.crabc.core.app.config uses a module listed above it, which is the healthy direction.
35→36 cn.crabc.core.app.config uses cn.crabc.core.app.util part of a loop✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.config uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.config.InterceptorConfig→cn.crabc.core.app.util.JwtUtil
- Direction
- cn.crabc.core.app.config uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.config, while a change to cn.crabc.core.app.config can't break cn.crabc.core.app.util.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36→19 cn.crabc.core.app.util uses cn.crabc.core.app.entity✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.util uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.entity.BaseDatasourcecn.crabc.core.app.util.SQLUtil→cn.crabc.core.app.entity.BaseApiParam
- Direction
- cn.crabc.core.app.util uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.util, while a change to cn.crabc.core.app.util can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.util uses a module listed above it, which is the healthy direction.
36→23 cn.crabc.core.app.util uses cn.crabc.core.app.entity.dto✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.util uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.util.ApiContext→cn.crabc.core.app.entity.dto.ApiInfoDTOcn.crabc.core.app.util.Slot→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.util uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.util, while a change to cn.crabc.core.app.util can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.util uses a module listed above it, which is the healthy direction.
36→25 cn.crabc.core.app.util uses cn.crabc.core.app.entity.vo✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.util uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.util.SQLUtil→cn.crabc.core.app.entity.vo.ColumnParseVo
- Direction
- cn.crabc.core.app.util uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.util, while a change to cn.crabc.core.app.util can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.util uses a module listed above it, which is the healthy direction.
36→28 cn.crabc.core.app.util uses cn.crabc.core.app.mapper✕
- Connections
- 4 pairs of types, where a type in cn.crabc.core.app.util uses a type in cn.crabc.core.app.mapper.
- The types involved
cn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.mapper.BaseApiInfoMappercn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.mapper.BaseAppMappercn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.mapper.BaseDataSourceMappercn.crabc.core.app.util.ResourceOwnerGuard→cn.crabc.core.app.mapper.BaseGroupMapper
- Direction
- cn.crabc.core.app.util uses cn.crabc.core.app.mapper, so a change to cn.crabc.core.app.mapper can break cn.crabc.core.app.util, while a change to cn.crabc.core.app.util can't break cn.crabc.core.app.mapper.
- Position
- Below the diagonal: cn.crabc.core.app.util uses a module listed above it, which is the healthy direction.
36→35 cn.crabc.core.app.util uses cn.crabc.core.app.config✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.util uses a type in cn.crabc.core.app.config.
- The types involved
cn.crabc.core.app.util.JwtUtil→cn.crabc.core.app.config.JwtProperties
- Direction
- cn.crabc.core.app.util uses cn.crabc.core.app.config, so a change to cn.crabc.core.app.config can break cn.crabc.core.app.util, while a change to cn.crabc.core.app.util can't break cn.crabc.core.app.config.
- Position
- Below the diagonal: cn.crabc.core.app.util uses a module listed above it, which is the healthy direction.
37→15 cn.crabc.core.app.api uses cn.crabc.core.plugin✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.api uses a type in cn.crabc.core.plugin.
- The types involved
cn.crabc.core.app.api.ApiServiceController→cn.crabc.core.plugin.DataPluginExecutor
- Direction
- cn.crabc.core.app.api uses cn.crabc.core.plugin, so a change to cn.crabc.core.plugin can break cn.crabc.core.app.api, while a change to cn.crabc.core.app.api can't break cn.crabc.core.plugin.
- Position
- Below the diagonal: cn.crabc.core.app.api uses a module listed above it, which is the healthy direction.
37→19 cn.crabc.core.app.api uses cn.crabc.core.app.entity✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.api uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.api.ApiServiceController→cn.crabc.core.app.entity.BaseApiParam
- Direction
- cn.crabc.core.app.api uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.api, while a change to cn.crabc.core.app.api can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.api uses a module listed above it, which is the healthy direction.
37→23 cn.crabc.core.app.api uses cn.crabc.core.app.entity.dto✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.api uses a type in cn.crabc.core.app.entity.dto.
- The types involved
cn.crabc.core.app.api.ApiServiceController→cn.crabc.core.app.entity.dto.ApiInfoDTO
- Direction
- cn.crabc.core.app.api uses cn.crabc.core.app.entity.dto, so a change to cn.crabc.core.app.entity.dto can break cn.crabc.core.app.api, while a change to cn.crabc.core.app.api can't break cn.crabc.core.app.entity.dto.
- Position
- Below the diagonal: cn.crabc.core.app.api uses a module listed above it, which is the healthy direction.
37→29 cn.crabc.core.app.api uses cn.crabc.core.app.service.core✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.api uses a type in cn.crabc.core.app.service.core.
- The types involved
cn.crabc.core.app.api.ApiServiceController→cn.crabc.core.app.service.core.IBaseDataService
- Direction
- cn.crabc.core.app.api uses cn.crabc.core.app.service.core, so a change to cn.crabc.core.app.service.core can break cn.crabc.core.app.api, while a change to cn.crabc.core.app.api can't break cn.crabc.core.app.service.core.
- Position
- Below the diagonal: cn.crabc.core.app.api uses a module listed above it, which is the healthy direction.
37→36 cn.crabc.core.app.api uses cn.crabc.core.app.util✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.api uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.api.ApiServiceController→cn.crabc.core.app.util.Result
- Direction
- cn.crabc.core.app.api uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.api, while a change to cn.crabc.core.app.api can't break cn.crabc.core.app.util.
- Position
- Below the diagonal: cn.crabc.core.app.api uses a module listed above it, which is the healthy direction.
38→15 cn.crabc.core.app.controller uses cn.crabc.core.plugin✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.plugin.
- The types involved
cn.crabc.core.app.controller.ApiTestController→cn.crabc.core.plugin.DataPluginExecutor
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.plugin, so a change to cn.crabc.core.plugin can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.plugin.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→19 cn.crabc.core.app.controller uses cn.crabc.core.app.entity✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.entity.
- The types involved
cn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.entity.BaseApiInfocn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.entity.BaseAppApicn.crabc.core.app.controller.BaseAppController→cn.crabc.core.app.entity.BaseAppcn.crabc.core.app.controller.BaseGroupController→cn.crabc.core.app.entity.BaseGroupcn.crabc.core.app.controller.DataSourceController→cn.crabc.core.app.entity.BaseDatasource
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.entity, so a change to cn.crabc.core.app.entity can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.entity.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→24 cn.crabc.core.app.controller uses cn.crabc.core.app.entity.param✕
- Connections
- 5 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.entity.param.
- The types involved
cn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.entity.param.ApiInfoParamcn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.entity.param.ApiRateLimitParamcn.crabc.core.app.controller.ApiLogController→cn.crabc.core.app.entity.param.ApiLogParamcn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.entity.param.ApiTestParamcn.crabc.core.app.controller.SysUserController→cn.crabc.core.app.entity.param.UserParam
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.entity.param, so a change to cn.crabc.core.app.entity.param can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.entity.param.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→25 cn.crabc.core.app.controller uses cn.crabc.core.app.entity.vo✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.entity.vo.
- The types involved
cn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.entity.vo.SqlParseVOcn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.entity.vo.PreviewVO
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.entity.vo, so a change to cn.crabc.core.app.entity.vo can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.entity.vo.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→29 cn.crabc.core.app.controller uses cn.crabc.core.app.service.core✕
- Connections
- 2 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.service.core.
- The types involved
cn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.service.core.IBaseDataServicecn.crabc.core.app.controller.MetaDataController→cn.crabc.core.app.service.core.MetaDataQueryService
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.service.core, so a change to cn.crabc.core.app.service.core can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.service.core.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→30 cn.crabc.core.app.controller uses cn.crabc.core.app.service.system✕
- Connections
- 10 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.service.system.
- The types involved
cn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.controller.ApiLogController→cn.crabc.core.app.service.system.IBaseApiLogServicecn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.controller.BaseAppController→cn.crabc.core.app.service.system.IBaseAppServicecn.crabc.core.app.controller.BaseGroupController→cn.crabc.core.app.service.system.IBaseGroupServicecn.crabc.core.app.controller.CommonController→cn.crabc.core.app.service.system.IBaseApiInfoServicecn.crabc.core.app.controller.CommonController→cn.crabc.core.app.service.system.IBaseApiParamServicecn.crabc.core.app.controller.DataSourceController→cn.crabc.core.app.service.system.IBaseDataSourceServicecn.crabc.core.app.controller.MetaDataController→cn.crabc.core.app.service.system.IBaseDataSourceServicecn.crabc.core.app.controller.SysUserController→cn.crabc.core.app.service.system.IBaseUserService
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.service.system, so a change to cn.crabc.core.app.service.system can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.service.system.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
38→36 cn.crabc.core.app.controller uses cn.crabc.core.app.util✕
- Connections
- 12 pairs of types, where a type in cn.crabc.core.app.controller uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.controller.ApiInfoController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.ApiLogController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.util.ResourceOwnerGuardcn.crabc.core.app.controller.ApiTestController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.BaseAppController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.BaseGroupController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.CommonController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.DataSourceController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.MetaDataController→cn.crabc.core.app.util.ResourceOwnerGuardcn.crabc.core.app.controller.MetaDataController→cn.crabc.core.app.util.Resultcn.crabc.core.app.controller.SysUserController→cn.crabc.core.app.util.JwtUtilcn.crabc.core.app.controller.SysUserController→cn.crabc.core.app.util.Result
- Direction
- cn.crabc.core.app.controller uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.controller, while a change to cn.crabc.core.app.controller can't break cn.crabc.core.app.util.
- Position
- Below the diagonal: cn.crabc.core.app.controller uses a module listed above it, which is the healthy direction.
39→11 cn.crabc.core.app.exception uses cn.crabc.core.datasource.exception✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.exception uses a type in cn.crabc.core.datasource.exception.
- The types involved
cn.crabc.core.app.exception.ExceptionHandler→cn.crabc.core.datasource.exception.CustomException
- Direction
- cn.crabc.core.app.exception uses cn.crabc.core.datasource.exception, so a change to cn.crabc.core.datasource.exception can break cn.crabc.core.app.exception, while a change to cn.crabc.core.app.exception can't break cn.crabc.core.datasource.exception.
- Position
- Below the diagonal: cn.crabc.core.app.exception uses a module listed above it, which is the healthy direction.
39→15 cn.crabc.core.app.exception uses cn.crabc.core.plugin✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.exception uses a type in cn.crabc.core.plugin.
- The types involved
cn.crabc.core.app.exception.ExceptionHandler→cn.crabc.core.plugin.DataPluginException
- Direction
- cn.crabc.core.app.exception uses cn.crabc.core.plugin, so a change to cn.crabc.core.plugin can break cn.crabc.core.app.exception, while a change to cn.crabc.core.app.exception can't break cn.crabc.core.plugin.
- Position
- Below the diagonal: cn.crabc.core.app.exception uses a module listed above it, which is the healthy direction.
39→22 cn.crabc.core.app.exception uses cn.crabc.core.spi✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.exception uses a type in cn.crabc.core.spi.
- The types involved
cn.crabc.core.app.exception.ExceptionHandler→cn.crabc.core.spi.PluginException
- Direction
- cn.crabc.core.app.exception uses cn.crabc.core.spi, so a change to cn.crabc.core.spi can break cn.crabc.core.app.exception, while a change to cn.crabc.core.app.exception can't break cn.crabc.core.spi.
- Position
- Below the diagonal: cn.crabc.core.app.exception uses a module listed above it, which is the healthy direction.
39→36 cn.crabc.core.app.exception uses cn.crabc.core.app.util✕
- Connections
- 1 pair of types, where a type in cn.crabc.core.app.exception uses a type in cn.crabc.core.app.util.
- The types involved
cn.crabc.core.app.exception.ExceptionHandler→cn.crabc.core.app.util.Result
- Direction
- cn.crabc.core.app.exception uses cn.crabc.core.app.util, so a change to cn.crabc.core.app.util can break cn.crabc.core.app.exception, while a change to cn.crabc.core.app.exception can't break cn.crabc.core.app.util.
- Position
- Below the diagonal: cn.crabc.core.app.exception uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A07:2025 — Authentication Failures | 5 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
| A05:2025 — Injection | 2 | Medium |
| A03:2025 — Software Supply Chain Failures | 1 | High / Critical |
Roadmap
Top priorities: Add a CI workflow that builds and runs the test suite on every push/PR; Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing; Add tests that import the unreached modules (directly or through their public entry).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Banned license finding(s) in License Compliance. | +4.7 pts | Low | License Compliance |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +4.2 pts | Low | ADR Quality |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +5.5 pts | Medium | CI/CD gates |
| Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing. | +5.5 pts | Medium | Security & performance tooling |
| Add tests that import the unreached modules (directly or through their public entry). | +5.5 pts | Medium | Test Coverage |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +4.0 pts | Medium | Architecture documentation |
| 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. | +3.7 pts | Medium | Type Safety |
| 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). | +2.9 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.8 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 5.8 | Mixed | IaC & Container Security: High IaC: REDACTED |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java | 5.9 | Mixed | Cognitive Complexity: ApiServiceController.checkParams (cognitive 23) |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java | 5.9 | Mixed | Code Duplication: Edited copy of a member (13 corresponding lines) |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java | 6.0 | Mixed | Explicit Debt: TodoComment |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java | 6.3 | Mixed | Code Duplication: Edited copy of a member (33 corresponding lines) |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java | 7.0 | Mixed | Cyclomatic Complexity: ApiDevTools.apiUpdate (cyclomatic 29) |
| apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java | 7.0 | Mixed | Cyclomatic Complexity: JdbcStatement.stripCommentsAndLiterals (cyclomatic 21) |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java | 7.2 | Mixed | God Classes: TooManyMethods: BaseApiInfoServiceImpl |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): High secret: REDACTED |
| REDACTED | 7.2 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java | 7.4 | Mixed | Cyclomatic Complexity: ApiTestController.buildParamsMap (cyclomatic 26) |
| apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java | 7.4 | Mixed | Cognitive Complexity: DataProcessPlugin.calculate (cognitive 23) |
| apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java | 7.8 | Mixed | Cyclomatic Complexity: PluginUtils.matches (cyclomatic 29) |
| apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java | 7.8 | Mixed | Cyclomatic Complexity: TreeTransformPlugin.apply (cyclomatic 23) |
| apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java | 7.8 | Mixed | Cyclomatic Complexity: RequestUtils.getIp (cyclomatic 19) |
| apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java | 7.8 | Mixed | Cyclomatic Complexity: DataPluginConfigValidator.validateDataProcess (cyclomatic 18) |
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 55 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 — 55 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, 130 of 144 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) and this repository declares a JVM test suite (repository root, Maven), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 28 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (7 contributor(s) across 501 commit(s) sampled, automation and bot accounts excluded). One of them holds 86% of the history; the other 6 hold 2.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (apigo-spring-boot-starter/pom.xml), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AC1 Text alternatives — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AC2 Forms & labels — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AC3 Page structure — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AC4 Keyboard semantics — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AC5 ARIA correctness — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AC6 Visual & motion safety — 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 repository builds its DOM through a hyperscript-style factory — 55 call(s) across 1 script file(s) — which the static markup model cannot read, so none of those elements entered the population the accessibility cards score. That is a gap in this analyzer's frontend coverage, not a finding about this repository.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.crabc-api.environment.[]: required variable JWT_SECRET is missing a value: 请先设置 JWT_SECRET 环境变量; runtime evidence skipped.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
10 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SQLUtil.splitSqlStatements at 37. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being McpToolSupport.buildJdbcUrl at 22 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java (McpToolSupport.buildJdbcUrl at 22), apigo-api/apigo-core/src/main/java/cn/crabc/core/app/support/DatasourceGuard.java (DatasourceGuard.defaultPort at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with SQLUtil.splitSqlStatements (cyclomatic 37). — Refactoring it lifts Cyclomatic Complexity from 8.3 to about 8.5/10.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was SQLUtil.splitSqlStatements at 64.
What to do
- Bring the 4 bodies over 30 down to 30 or less in Cognitive Complexity — start with SQLUtil.splitSqlStatements (cognitive 64), ApiTestController.buildParamsMap (cognitive 44), JdbcStatement.stripCommentsAndLiterals (cognitive 41). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 4 together lifts Cognitive Complexity from 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
D3 · God Classes
7 god class(es) detected.
What to do
- Resolve the 3 ClassTooLong finding(s) in God Classes — start with ApiDevTools.java, BaseApiInfoServiceImpl.java, SQLUtil.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with BaseApiInfoServiceImpl.java, BaseDataSource.java. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with ApiDevTools.java. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
27 duplicated block group(s) detected. 5.2 % of the production lines (867 of 16,590) are in a reported copy. A further 20 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with REDACTED (2), ApiDevTools.java (2), DataSourceTools.java. — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 4 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with DataProcessPlugin.java (2), BaseApiInfoServiceImpl.java, ApiTestController.java. — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SysUserController.java, SQLUtil.java, ResultTypeEnum.java. — One of this dimension's main actionable groups (3 warning-level).
D5 · Coupling
6 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 45 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with McpToolSupport.java. — One of this dimension's main actionable groups (1 warning-level).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 155 tests.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
1 of 11 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 8 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. 28 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. A further 1 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.
What to do
- Resolve the 1 Banned license finding(s) in License Compliance. — One of this dimension's main actionable groups (1 issue-level).
D15 · Churn × Complexity Hotspots
Top hotspots: apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java (4×21=84); apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java (3×16=48)
What to do
- Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with JdbcStatement.java, AuthInterceptor.java. — One of this dimension's main actionable groups (2 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 16590 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 SQLUtil.java. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D21 · Naming Consistency
2 naming inconsistencies among 36 declarations measured against a convention their peers follow.
What to do
- Resolve the 1 `ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO` finding(s) in Naming Consistency — start with ColumnParseVo.java. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 `analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql` finding(s) in Naming Consistency — start with SQLUtil.java. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 6 build units (Maven) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
75 % of calls cross a namespace and 13 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
4 finding(s): 0 critical, 4 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 3 High secret finding(s) in Secrets (history) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep hit a parse error in 3 file(s) — `apigo-api/apigo-core/src/main/resources/static/assets/develop-cFFR-jwR.js`, `apigo-api/apigo-core/src/main/resources/static/assets/index-Bq7GivHf.js`, `apigo-api/apigo-core/src/main/resources/static/assets/index-CvHUAiMZ.js` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 1 high, 0 medium, 0 low.
What to do
- Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 3 high, 1 medium, 1 low.
What to do
- Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 Medium IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
6 of 71 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 71 of the 152 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: BaseApiInfoMapper.java↔IBaseApiInfoService.java 91%; DataSourceManager.java↔DefaultDataSourceDriver.java 75%; ApiServiceController.java↔ApiTestController.java 59%
What to do
- Resolve the 6 Change coupling finding(s) in Change Coupling — start with BaseDataServiceImpl.java (2), BaseApiInfoMapper.java, DataSourceManager.java. — One of this dimension's main actionable groups (6 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 15 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
- `BaseApiInfoMapper` declares 16 abstract methods: `checkApiPath`, `countApi`, `countOwnedReleasedApis`, `deleteApiInfo`, `getApiDetail`, `insertApiInfo`, `selectApiApp`, `selectApiById`, `selectApiDetail`, `selectApiGroup`, `selectBaseApi`, `selectList`, `updateApiInfo`, `updateApiState`, `updateDraftContent`, `updateRateLimit`. 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. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:18
- `IBaseApiInfoService` declares 20 abstract methods: `addApiInfo`, `addChooseApi`, `apiPublish`, `checkApiPath`, `deleteApi`, `destroyApiInfo`, `getApiCache`, `getApiDetail`, `getApiInfo`, `getApiInfoCache`, `getApiList`, `getApiListGroup`, `getApiListUser`, `getApiPage`, `getChooseApi`, `getNotChooseApi`, `getRateLimit`, `saveRateLimit`, `updateApiInfo`, `updateApiState`. 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. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java:22
What to do
- Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apigo-api/apigo-admin`.
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) — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `REDACTED` 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`. — REDACTED:38
What to do
- Run what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add 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
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
R1 · Type Safety
- 0 typed · 6 plain JS — the untyped files are apigo-api/apigo-core/src/main/resources/static/assets/403-D4TW9di3.js, apigo-api/apigo-core/src/main/resources/static/assets/BlankLayout-CMEBJCoa.js, apigo-api/apigo-core/src/main/resources/static/assets/UserLayout-BcViDKRQ.js, apigo-api/apigo-core/src/main/resources/static/assets/_plugin-vue_export-helper-DlAUqK2U.js, apigo-api/apigo-core/src/main/resources/static/assets/logo-BsuGIj-2.js, apigo-api/apigo-core/src/main/resources/static/assets/rangeDate-BTmavQEu.js.
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
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- 0% of 6 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R7 · Dead Code
R9 · Circular Imports
X16 · Unfloored truncation loop
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
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. (×2) — apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:78, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:683
- `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60, apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:268
- `catch (RuntimeException)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:153
What to do
- Swallowed exception (empty catch)
X4 · Structured logging
X5 · Nullable reference types
- 0/38 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
- Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 50.9 | Adequate — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 94.7 | Exemplary | Strongest area. |
| Maturity | 59.7 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 26.5 | Weak — gated by R4, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 84.7 | Checked 4 of 10 | Solid. |
Unscored — 3 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X6 Hand-rolled structured-format parsing — 1 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 — 66 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AC2 Forms & labels — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AC3 Page structure — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AC4 Keyboard semantics — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AC5 ARIA correctness — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AC6 Visual & motion safety — Frontend markup is constructed programmatically — 55 DOM factory call(s) across 1 script file(s), which the static markup model cannot read — so accessibility is NOT MEASURED. Only 22 statically-readable DOM element(s) were found; this is a blind spot in the scan, not a small frontend.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — error while interpolating services.crabc-api.environment.[]: required variable JWT_SECRET is missing a value: 请先设置 JWT_SECRET 环境变量; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
- D12 Dependency Hygiene — Not scored — 8 Maven/Gradle manifest(s) were read, stating a version for 12 dependency(ies) and leaving 28 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
- D16 Bus Factor — 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.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .java source were not judged.
- D25 ADR Conformance — no ADRs to check
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (9 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — no CI workflow found
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JVM, JavaScript/TypeScript source (service entry point: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:26 (@RestController))
- 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.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Banned license: com.mysql:mysql-connector-j
- REDACTED
- REDACTED
Serious — 107 finding(s)
- Change coupling: BaseApiInfoMapper.java ↔ IBaseApiInfoService.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:1
- Change coupling: DataSourceManager.java ↔ DefaultDataSourceDriver.java apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/DataSourceManager.java:1
- Change coupling: ApiServiceController.java ↔ ApiTestController.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:1
- Change coupling: ApiInfoController.java ↔ BaseApiInfoMapper.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:1
- Change coupling: BaseDataServiceImpl.java ↔ JdbcStatement.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java:1
- Change coupling: BaseDataServiceImpl.java ↔ JdbcDataSourceRouter.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/core/impl/BaseDataServiceImpl.java:1
- Duplicated block (5 lines × 2) REDACTED:25
- Duplicated block (5 lines × 2) REDACTED:44
- Duplicated block (5 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:212
- Duplicated block (5 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:344
- Duplicated block (5 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:147
- Duplicated block (7 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:259
- Duplicated block (7 lines × 2) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:45
- Duplicated block (7 lines × 2) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:37
- Duplicated block (7 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:166
- ClassTooLong: ApiDevTools apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:44
- ClassTooLong: BaseApiInfoServiceImpl apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:47
- ClassTooLong: SQLUtil apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:40
- Duplicated block (8 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/SysUserController.java:43
- Duplicated block (8 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:713
- Duplicated block (8 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ResultTypeEnum.java:26
- Duplicated block (6 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:198
- Duplicated block (6 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:45
- Duplicated block (6 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiLogController.java:129
- Swallowed exception (caught, then discarded) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60
- Swallowed exception (caught, then discarded) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:153
- Swallowed exception (caught, then discarded) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:268
- Hotspot: apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586
- Hotspot: apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:342
- TooManyMethods: BaseApiInfoServiceImpl apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:47
- TooManyMethods: BaseDataSource apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/BaseDataSource.java:25
- Edited copy of a member (7 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:222
- Edited copy of a member (7 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ApiContext.java:55
- Swallowed exception (empty catch) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:78
- Swallowed exception (empty catch) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:683
- SQLUtil.splitSqlStatements (cyclomatic 37) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263
- ApiDevTools.apiUpdate (cyclomatic 29) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324
- PluginUtils.matches (cyclomatic 29) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java:76
- ApiTestController.buildParamsMap (cyclomatic 26) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215
- TreeTransformPlugin.apply (cyclomatic 23) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38
- JdbcStatement.stripCommentsAndLiterals (cyclomatic 21) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586
- RequestUtils.getIp (cyclomatic 19) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java:85
- PluginUtils.mask (cyclomatic 19) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/util/PluginUtils.java:162
- DataPluginConfigValidator.validateDataProcess (cyclomatic 18) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:96
- AuthInterceptor.preHandle (cyclomatic 16) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:342
- TodoComment apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:480
- SQLUtil.splitSqlStatements (cognitive 64) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:263
- ApiTestController.buildParamsMap (cognitive 44) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiTestController.java:215
- JdbcStatement.stripCommentsAndLiterals (cognitive 41) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:586
- ApiDevTools.apiUpdate (cognitive 36) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324
- TreeTransformPlugin.apply (cognitive 28) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/TreeTransformPlugin.java:38
- DataPluginConfigValidator.validateDataProcess (cognitive 26) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:96
- SqlExceptionUtils.isTimeout (cognitive 25) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/util/SqlExceptionUtils.java:63
- MetaDataTools.schemas (cognitive 24) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:64
- ApiServiceController.checkParams (cognitive 23) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:125
- DataProcessPlugin.calculate (cognitive 23) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/DataProcessPlugin.java:172
- JdbcStatement.selectPage (cognitive 21) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:117
- FieldMappingPlugin.apply (cognitive 21) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/FieldMappingPlugin.java:32
- DefaultDataSourceDriver.createHikariDataSource (cognitive 20) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/DefaultDataSourceDriver.java:126
- RequestUtils.getIp (cognitive 19) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/RequestUtils.java:85
- SingleObjectPlugin.apply (cognitive 18) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/impl/SingleObjectPlugin.java:36
- SqlPreviewGuard.lineCommentIndex (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/SqlPreviewGuard.java:222
- DataSourceTools.datasourceUpdate (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/DataSourceTools.java:166
- SQLUtil.analyzeSQL (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:113
- SQLUtil.findXmlTagEnd (cognitive 17) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:588
- DataPluginExecutor.execute (cognitive 17) apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginExecutor.java:68
- AppTools.currentAuthorized (cognitive 16) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/AppTools.java:221
- REDACTED
- REDACTED
- FileTooLong: tools/ApiDevTools.java apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java
- MethodTooLong: ApiDevTools.apiUpdate apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:324
- REDACTED
- Members sharing a duplicated core (4 members, 50+ identical tokens) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:181
- Edited copy of a member (28 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:165
- Edited copy of a member (26 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/MetaDataTools.java:112
- Edited copy of a member (33 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:141
- Edited copy of a member (16 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:405
- Edited copy of a member (23 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/api/ApiServiceController.java:56
- Edited copy of a member (14 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiOpsTools.java:209
- Edited copy of a member (19 corresponding lines) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:19
- Edited copy of a member (12 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/filter/AuthInterceptor.java:602
- Edited copy of a member (10 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseGroupServiceImpl.java:43
- Edited copies of one member (4 members, 10+ corresponding lines) REDACTED:24
- Edited copies of one member (3 members, 11+ corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/ResourceOwnerGuard.java:73
- Edited copy of a member (13 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:277
- Edited copies of one member (3 members, 9+ corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:242
- Edited copy of a member (9 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:196
- Edited copies of one member (3 members, 7+ corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:699
- Edited copy of a member (5 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/impl/BaseApiInfoServiceImpl.java:147
- Edited copy of a member (6 corresponding lines) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:209
- Duplicated block (13–22 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:146
- Duplicated block (12 lines × 3) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:191
- Duplicated block (12 lines × 2) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcMetaData.java:23
- Duplicated block (11 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:182
- Duplicated block (9–10 lines × 4) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:193
- Duplicated block (10 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:293
- Duplicated block (8 lines × 3) apigo-api/apigo-datasource/src/main/java/cn/crabc/core/datasource/driver/jdbc/JdbcStatement.java:182
- Duplicated block (6–7 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:185
- Duplicated block (3–6 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:407
- Duplicated block (20 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/enums/ApiAuthEnum.java:16
- Duplicated block (24 lines × 2) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/PageInfo.java:16
- Duplicated block (5 lines × 3) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:174
- Off the main sequence: apigo-plugin
- Low cohesion: McpToolSupport (LCOM4 6) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpToolSupport.java:33
- No CI pipeline
- Type Safety
- Test Coverage
Minor — 28 finding(s)
- Orphaned file REDACTED:1
- Orphaned file apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/Result.java:1
- Orphaned file apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Table.java:1
- Orphaned file apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/DataSourceController.java:1
- Orphaned file apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/StatementMapper.java:1
- Orphaned file apigo-api/apigo-spi/src/main/java/cn/crabc/core/spi/bean/Column.java:1
- Duplicated predicate apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/tools/ApiDevTools.java:205
- Duplicated predicate apigo-api/apigo-plugin/src/main/java/cn/crabc/core/plugin/DataPluginConfigValidator.java:236
- Duplicated predicate apigo-api/apigo-core/src/main/java/cn/crabc/core/app/controller/ApiInfoController.java:159
- Fat interface: BaseApiInfoMapper (16 abstract methods) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mapper/BaseApiInfoMapper.java:18
- Fat interface: IBaseApiInfoService (20 abstract methods) apigo-api/apigo-core/src/main/java/cn/crabc/core/app/service/system/IBaseApiInfoService.java:22
- No ADRs found apigo-api/apigo-admin/pom.xml:28
- `ColumnParseVo` spells `Vo` where 18 names in the project spell it `VO` apigo-api/apigo-core/src/main/java/cn/crabc/core/app/entity/vo/ColumnParseVo.java:8
- `analyzeSQL` spells `SQL` where 16 names in the project spell it `Sql` apigo-api/apigo-core/src/main/java/cn/crabc/core/app/util/SQLUtil.java:113
- Projects may be oversized for their cohesion apigo-api/apigo-core/pom.xml:1
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- No ADRs
- No architecture diagram/doc
- Logging is not universal
- No SAST
- No dependency-update automation REDACTED:38
- No rollback/health safety
- No changelog
- Java packages are not null-marked everywhere
- Hand-rolled JSON/XML parsing via regex apigo-api/apigo-core/src/main/resources/static/assets/develop-cFFR-jwR.js:42
- Silent fallback default in catch apigo-api/apigo-core/src/main/java/cn/crabc/core/app/mcp/support/McpAuditRecorder.java:60
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-d01f8760fb3446f9952eae486e8351ba/history.json --exit-code 0 --source . | 11 | 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=172" --report-format json --report-path /tmp/watchdog-gitleaks-d01f8760fb3446f9952eae486e8351ba/history-1.json --exit-code 0 --source . | 0 | 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=372 --max-count=134" --report-format json --report-path /tmp/watchdog-gitleaks-d01f8760fb3446f9952eae486e8351ba/history-2.json --exit-code 0 --source . | 0 | 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-d01f8760fb3446f9952eae486e8351ba/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 . | 2 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 1 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |