Executive summary
followarcane/WowProgressDataCrawler falls short of our standard for production, in part because we found no automated security scanning of the code, its secrets or its dependencies. It scores 46.9 out of 100 and is rated Weak, and 22 of its 23 critical findings are security problems in the build pipeline.
Production Readiness, at 31.3, is the weakest lens and counts most in the score. The best first step is adding tests for untested code, worth about 7.2 points. Adding automated security scanning would lift Production Readiness itself, worth about 5.3 points. Raising Production Readiness to 70 would lift the score to about 60.4.
Fifteen secrets can leak from the build pipeline. Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Limiting each secret to its own step and pinning each tool to an exact version would close both risks. The test that checks nothing needs to check the result it produces.
The product code is 3,304 lines, about €4,400 to rebuild.
If Production Readiness rose from 31.3 to 70, the lowest score rated Strong, the score would rise from 46.9 to about 60.4.
Rebuild cost: about €4,400 · Estimate
| Cost to rebuild | €1,500 to €7,300, for 24 to 77 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | High, 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 47. 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: 3,304 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 wowdatacrawler | 2 wowdatacrawler.api.v1.error | 3 wowdatacrawler.api.v1.responses | 4 wowdatacrawler.domain.model | 5 wowdatacrawler.domain.model.wcl | 6 wowdatacrawler.infrastructure.config | 7 wowdatacrawler.infrastructure.service.version | 8 wowdatacrawler.infrastructure.utils | 9 wowdatacrawler.security.logger | 10 wowdatacrawler.api.v1.requests | 11 wowdatacrawler.domain.converter | 12 wowdatacrawler.infrastructure.repository | 13 wowdatacrawler.infrastructure.service.lfg | 14 wowdatacrawler.security | 15 wowdatacrawler.infrastructure.persistence | 16 wowdatacrawler.infrastructure.service.repoService | 17 wowdatacrawler.security.service | 18 wowdatacrawler.infrastructure.service | 19 wowdatacrawler.api.v1.controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 wowdatacrawler | |||||||||||||||||||
| 2 wowdatacrawler.api.v1.error | |||||||||||||||||||
| 3 wowdatacrawler.api.v1.responses | |||||||||||||||||||
| 4 wowdatacrawler.domain.model | |||||||||||||||||||
| 5 wowdatacrawler.domain.model.wcl | |||||||||||||||||||
| 6 wowdatacrawler.infrastructure.config | |||||||||||||||||||
| 7 wowdatacrawler.infrastructure.service.version | |||||||||||||||||||
| 8 wowdatacrawler.infrastructure.utils | |||||||||||||||||||
| 9 wowdatacrawler.security.logger | |||||||||||||||||||
| 10 wowdatacrawler.api.v1.requests | 1 | ||||||||||||||||||
| 11 wowdatacrawler.domain.converter | 7 | 6 | |||||||||||||||||
| 12 wowdatacrawler.infrastructure.repository | 2 | ||||||||||||||||||
| 13 wowdatacrawler.infrastructure.service.lfg | 11 | ||||||||||||||||||
| 14 wowdatacrawler.security | 1 | ||||||||||||||||||
| 15 wowdatacrawler.infrastructure.persistence | 1 | ||||||||||||||||||
| 16 wowdatacrawler.infrastructure.service.repoService | 2 | 2 | |||||||||||||||||
| 17 wowdatacrawler.security.service | 1 | ||||||||||||||||||
| 18 wowdatacrawler.infrastructure.service | 8 | 1 | 2 | 3 | 5 | 1 | |||||||||||||
| 19 wowdatacrawler.api.v1.controller | 2 | 2 | 2 | 1 | 1 |
10→8 wowdatacrawler.api.v1.requests uses wowdatacrawler.infrastructure.utils✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.api.v1.requests uses a type in wowdatacrawler.infrastructure.utils.
- The types involved
followarcane.wowdatacrawler.api.v1.requests.UserCommand→followarcane.wowdatacrawler.infrastructure.utils.Authorities
- Direction
- wowdatacrawler.api.v1.requests uses wowdatacrawler.infrastructure.utils, so a change to wowdatacrawler.infrastructure.utils can break wowdatacrawler.api.v1.requests, while a change to wowdatacrawler.api.v1.requests can't break wowdatacrawler.infrastructure.utils.
- Position
- Below the diagonal: wowdatacrawler.api.v1.requests uses a module listed above it, which is the healthy direction.
11→3 wowdatacrawler.domain.converter uses wowdatacrawler.api.v1.responses✕
- Connections
- 7 pairs of types, where a type in wowdatacrawler.domain.converter uses a type in wowdatacrawler.api.v1.responses.
- The types involved
followarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.BossRankResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.CharacterInfoResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.RaidProgressionResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.RaidScheduleDayResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.RaiderIODataResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.UserResponsefollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.api.v1.responses.WarcraftLogsDataResponse
- Direction
- wowdatacrawler.domain.converter uses wowdatacrawler.api.v1.responses, so a change to wowdatacrawler.api.v1.responses can break wowdatacrawler.domain.converter, while a change to wowdatacrawler.domain.converter can't break wowdatacrawler.api.v1.responses.
- Position
- Below the diagonal: wowdatacrawler.domain.converter uses a module listed above it, which is the healthy direction.
11→4 wowdatacrawler.domain.converter uses wowdatacrawler.domain.model✕
- Connections
- 6 pairs of types, where a type in wowdatacrawler.domain.converter uses a type in wowdatacrawler.domain.model.
- The types involved
followarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.BossRankfollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.RaidProgressionfollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.RaiderIODatafollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.Userfollowarcane.wowdatacrawler.domain.converter.ResponseConverter→followarcane.wowdatacrawler.domain.model.WarcraftLogsData
- Direction
- wowdatacrawler.domain.converter uses wowdatacrawler.domain.model, so a change to wowdatacrawler.domain.model can break wowdatacrawler.domain.converter, while a change to wowdatacrawler.domain.converter can't break wowdatacrawler.domain.model.
- Position
- Below the diagonal: wowdatacrawler.domain.converter uses a module listed above it, which is the healthy direction.
12→4 wowdatacrawler.infrastructure.repository uses wowdatacrawler.domain.model✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.infrastructure.repository uses a type in wowdatacrawler.domain.model.
- The types involved
followarcane.wowdatacrawler.infrastructure.repository.CharacterInfoRepository→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.repository.UserRepository→followarcane.wowdatacrawler.domain.model.User
- Direction
- wowdatacrawler.infrastructure.repository uses wowdatacrawler.domain.model, so a change to wowdatacrawler.domain.model can break wowdatacrawler.infrastructure.repository, while a change to wowdatacrawler.infrastructure.repository can't break wowdatacrawler.domain.model.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.repository uses a module listed above it, which is the healthy direction.
13→4 wowdatacrawler.infrastructure.service.lfg uses wowdatacrawler.domain.model✕
- Connections
- 11 pairs of types, where a type in wowdatacrawler.infrastructure.service.lfg uses a type in wowdatacrawler.domain.model.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.lfg.LfgFetchResult→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgFetchResult→followarcane.wowdatacrawler.domain.model.LfgSourcefollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgFetcher→followarcane.wowdatacrawler.domain.model.LfgSourcefollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgMergeService→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgMergeService→followarcane.wowdatacrawler.domain.model.LfgSourcefollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgSourceSupport→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.lfg.LfgSourceSupport→followarcane.wowdatacrawler.domain.model.LfgSourcefollowarcane.wowdatacrawler.infrastructure.service.lfg.RaiderIoLfgFetcher→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.lfg.RaiderIoLfgFetcher→followarcane.wowdatacrawler.domain.model.LfgSourcefollowarcane.wowdatacrawler.infrastructure.service.lfg.WowProgressLfgFetcher→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.lfg.WowProgressLfgFetcher→followarcane.wowdatacrawler.domain.model.LfgSource
- Direction
- wowdatacrawler.infrastructure.service.lfg uses wowdatacrawler.domain.model, so a change to wowdatacrawler.domain.model can break wowdatacrawler.infrastructure.service.lfg, while a change to wowdatacrawler.infrastructure.service.lfg can't break wowdatacrawler.domain.model.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service.lfg uses a module listed above it, which is the healthy direction.
14→9 wowdatacrawler.security uses wowdatacrawler.security.logger✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.security uses a type in wowdatacrawler.security.logger.
- The types involved
followarcane.wowdatacrawler.security.SecurityConfig→followarcane.wowdatacrawler.security.logger.RequestResponseLoggingFilter
- Direction
- wowdatacrawler.security uses wowdatacrawler.security.logger, so a change to wowdatacrawler.security.logger can break wowdatacrawler.security, while a change to wowdatacrawler.security can't break wowdatacrawler.security.logger.
- Position
- Below the diagonal: wowdatacrawler.security uses a module listed above it, which is the healthy direction.
15→12 wowdatacrawler.infrastructure.persistence uses wowdatacrawler.infrastructure.repository✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.infrastructure.persistence uses a type in wowdatacrawler.infrastructure.repository.
- The types involved
followarcane.wowdatacrawler.infrastructure.persistence.DatabaseSeeder→followarcane.wowdatacrawler.infrastructure.repository.UserRepository
- Direction
- wowdatacrawler.infrastructure.persistence uses wowdatacrawler.infrastructure.repository, so a change to wowdatacrawler.infrastructure.repository can break wowdatacrawler.infrastructure.persistence, while a change to wowdatacrawler.infrastructure.persistence can't break wowdatacrawler.infrastructure.repository.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.persistence uses a module listed above it, which is the healthy direction.
16→4 wowdatacrawler.infrastructure.service.repoService uses wowdatacrawler.domain.model✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.infrastructure.service.repoService uses a type in wowdatacrawler.domain.model.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.repoService.CharacterInfoService→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.repoService.WarcraftLogsDataService→followarcane.wowdatacrawler.domain.model.WarcraftLogsData
- Direction
- wowdatacrawler.infrastructure.service.repoService uses wowdatacrawler.domain.model, so a change to wowdatacrawler.domain.model can break wowdatacrawler.infrastructure.service.repoService, while a change to wowdatacrawler.infrastructure.service.repoService can't break wowdatacrawler.domain.model.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service.repoService uses a module listed above it, which is the healthy direction.
16→12 wowdatacrawler.infrastructure.service.repoService uses wowdatacrawler.infrastructure.repository✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.infrastructure.service.repoService uses a type in wowdatacrawler.infrastructure.repository.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.repoService.CharacterInfoService→followarcane.wowdatacrawler.infrastructure.repository.CharacterInfoRepositoryfollowarcane.wowdatacrawler.infrastructure.service.repoService.WarcraftLogsDataService→followarcane.wowdatacrawler.infrastructure.repository.WarcraftLogsRepository
- Direction
- wowdatacrawler.infrastructure.service.repoService uses wowdatacrawler.infrastructure.repository, so a change to wowdatacrawler.infrastructure.repository can break wowdatacrawler.infrastructure.service.repoService, while a change to wowdatacrawler.infrastructure.service.repoService can't break wowdatacrawler.infrastructure.repository.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service.repoService uses a module listed above it, which is the healthy direction.
17→12 wowdatacrawler.security.service uses wowdatacrawler.infrastructure.repository✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.security.service uses a type in wowdatacrawler.infrastructure.repository.
- The types involved
followarcane.wowdatacrawler.security.service.UserDetailsServiceImpl→followarcane.wowdatacrawler.infrastructure.repository.UserRepository
- Direction
- wowdatacrawler.security.service uses wowdatacrawler.infrastructure.repository, so a change to wowdatacrawler.infrastructure.repository can break wowdatacrawler.security.service, while a change to wowdatacrawler.security.service can't break wowdatacrawler.infrastructure.repository.
- Position
- Below the diagonal: wowdatacrawler.security.service uses a module listed above it, which is the healthy direction.
18→4 wowdatacrawler.infrastructure.service uses wowdatacrawler.domain.model✕
- Connections
- 8 pairs of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.domain.model.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.DiffSnapshot→followarcane.wowdatacrawler.domain.model.BossRankfollowarcane.wowdatacrawler.infrastructure.service.RaiderIOService→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.RaiderIOService→followarcane.wowdatacrawler.domain.model.RaiderIODatafollowarcane.wowdatacrawler.infrastructure.service.UserService→followarcane.wowdatacrawler.domain.model.Userfollowarcane.wowdatacrawler.infrastructure.service.WarcraftLogsService→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.WarcraftLogsService→followarcane.wowdatacrawler.domain.model.WarcraftLogsDatafollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.domain.model.CharacterInfofollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.domain.model.LfgSource
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.domain.model, so a change to wowdatacrawler.domain.model can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.domain.model.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
18→7 wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.version✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.infrastructure.service.version.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.version.VersionNotifierService
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.version, so a change to wowdatacrawler.infrastructure.service.version can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.infrastructure.service.version.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
18→10 wowdatacrawler.infrastructure.service uses wowdatacrawler.api.v1.requests✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.api.v1.requests.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.UserService→followarcane.wowdatacrawler.api.v1.requests.CreateUserCommandfollowarcane.wowdatacrawler.infrastructure.service.UserService→followarcane.wowdatacrawler.api.v1.requests.UpdateUserCommand
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.api.v1.requests, so a change to wowdatacrawler.api.v1.requests can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.api.v1.requests.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
18→12 wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.repository✕
- Connections
- 3 pairs of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.infrastructure.repository.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.RaiderIOService→followarcane.wowdatacrawler.infrastructure.repository.RaiderIODataRepositoryfollowarcane.wowdatacrawler.infrastructure.service.UserService→followarcane.wowdatacrawler.infrastructure.repository.UserRepositoryfollowarcane.wowdatacrawler.infrastructure.service.WarcraftLogsService→followarcane.wowdatacrawler.infrastructure.repository.WarcraftLogsRepository
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.repository, so a change to wowdatacrawler.infrastructure.repository can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.infrastructure.repository.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
18→13 wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.lfg✕
- Connections
- 5 pairs of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.infrastructure.service.lfg.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.lfg.LfgFetchResultfollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.lfg.LfgFetcherfollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.lfg.LfgMergeServicefollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.lfg.WowProgressLfgFetcherfollowarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.lfg.WowProgressPageEnrich
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.lfg, so a change to wowdatacrawler.infrastructure.service.lfg can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.infrastructure.service.lfg.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
18→16 wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.repoService✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.infrastructure.service uses a type in wowdatacrawler.infrastructure.service.repoService.
- The types involved
followarcane.wowdatacrawler.infrastructure.service.WowDataCrawlerService→followarcane.wowdatacrawler.infrastructure.service.repoService.CharacterInfoService
- Direction
- wowdatacrawler.infrastructure.service uses wowdatacrawler.infrastructure.service.repoService, so a change to wowdatacrawler.infrastructure.service.repoService can break wowdatacrawler.infrastructure.service, while a change to wowdatacrawler.infrastructure.service can't break wowdatacrawler.infrastructure.service.repoService.
- Position
- Below the diagonal: wowdatacrawler.infrastructure.service uses a module listed above it, which is the healthy direction.
19→3 wowdatacrawler.api.v1.controller uses wowdatacrawler.api.v1.responses✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.api.v1.controller uses a type in wowdatacrawler.api.v1.responses.
- The types involved
followarcane.wowdatacrawler.api.v1.controller.AdminController→followarcane.wowdatacrawler.api.v1.responses.UserResponsefollowarcane.wowdatacrawler.api.v1.controller.WowDataCrawlerController→followarcane.wowdatacrawler.api.v1.responses.CharacterInfoResponse
- Direction
- wowdatacrawler.api.v1.controller uses wowdatacrawler.api.v1.responses, so a change to wowdatacrawler.api.v1.responses can break wowdatacrawler.api.v1.controller, while a change to wowdatacrawler.api.v1.controller can't break wowdatacrawler.api.v1.responses.
- Position
- Below the diagonal: wowdatacrawler.api.v1.controller uses a module listed above it, which is the healthy direction.
19→10 wowdatacrawler.api.v1.controller uses wowdatacrawler.api.v1.requests✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.api.v1.controller uses a type in wowdatacrawler.api.v1.requests.
- The types involved
followarcane.wowdatacrawler.api.v1.controller.AdminController→followarcane.wowdatacrawler.api.v1.requests.CreateUserCommandfollowarcane.wowdatacrawler.api.v1.controller.AdminController→followarcane.wowdatacrawler.api.v1.requests.UpdateUserCommand
- Direction
- wowdatacrawler.api.v1.controller uses wowdatacrawler.api.v1.requests, so a change to wowdatacrawler.api.v1.requests can break wowdatacrawler.api.v1.controller, while a change to wowdatacrawler.api.v1.controller can't break wowdatacrawler.api.v1.requests.
- Position
- Below the diagonal: wowdatacrawler.api.v1.controller uses a module listed above it, which is the healthy direction.
19→11 wowdatacrawler.api.v1.controller uses wowdatacrawler.domain.converter✕
- Connections
- 2 pairs of types, where a type in wowdatacrawler.api.v1.controller uses a type in wowdatacrawler.domain.converter.
- The types involved
followarcane.wowdatacrawler.api.v1.controller.AdminController→followarcane.wowdatacrawler.domain.converter.ResponseConverterfollowarcane.wowdatacrawler.api.v1.controller.WowDataCrawlerController→followarcane.wowdatacrawler.domain.converter.ResponseConverter
- Direction
- wowdatacrawler.api.v1.controller uses wowdatacrawler.domain.converter, so a change to wowdatacrawler.domain.converter can break wowdatacrawler.api.v1.controller, while a change to wowdatacrawler.api.v1.controller can't break wowdatacrawler.domain.converter.
- Position
- Below the diagonal: wowdatacrawler.api.v1.controller uses a module listed above it, which is the healthy direction.
19→16 wowdatacrawler.api.v1.controller uses wowdatacrawler.infrastructure.service.repoService✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.api.v1.controller uses a type in wowdatacrawler.infrastructure.service.repoService.
- The types involved
followarcane.wowdatacrawler.api.v1.controller.WowDataCrawlerController→followarcane.wowdatacrawler.infrastructure.service.repoService.CharacterInfoService
- Direction
- wowdatacrawler.api.v1.controller uses wowdatacrawler.infrastructure.service.repoService, so a change to wowdatacrawler.infrastructure.service.repoService can break wowdatacrawler.api.v1.controller, while a change to wowdatacrawler.api.v1.controller can't break wowdatacrawler.infrastructure.service.repoService.
- Position
- Below the diagonal: wowdatacrawler.api.v1.controller uses a module listed above it, which is the healthy direction.
19→18 wowdatacrawler.api.v1.controller uses wowdatacrawler.infrastructure.service✕
- Connections
- 1 pair of types, where a type in wowdatacrawler.api.v1.controller uses a type in wowdatacrawler.infrastructure.service.
- The types involved
followarcane.wowdatacrawler.api.v1.controller.AdminController→followarcane.wowdatacrawler.infrastructure.service.UserService
- Direction
- wowdatacrawler.api.v1.controller uses wowdatacrawler.infrastructure.service, so a change to wowdatacrawler.infrastructure.service can break wowdatacrawler.api.v1.controller, while a change to wowdatacrawler.api.v1.controller can't break wowdatacrawler.infrastructure.service.
- Position
- Below the diagonal: wowdatacrawler.api.v1.controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 23 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
| A02:2025 — Security Misconfiguration | 4 | Medium |
Roadmap
Top priorities: Resolve the 30 Low coverage finding(s) in Code Coverage — start with WowDataCrawlerApplication.java, AdminController.java, HealthController.java; Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing; Resolve the 1 finding(s) in DR & Backup.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 30 Low coverage finding(s) in Code Coverage — start with WowDataCrawlerApplication.java, AdminController.java, HealthController.java. | +7.2 pts | Medium | Code Coverage |
| Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with WowDataCrawlerApplicationTests.java. | +4.2 pts | Low | Test Quality |
| Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing. | +5.3 pts | Medium | Security & performance tooling |
| Resolve the 1 finding(s) in DR & Backup. | +5.3 pts | Medium | DR & Backup |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. | +2.3 pts | Low | ADR Quality |
| Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most. | +4.3 pts | Medium | Domain vs controller coverage |
| Resolve the 1 Off-boarding risk finding(s) in Bus Factor. | +1.5 pts | Low | Bus Factor |
| 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. | +2.0 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java | 5.5 | Mixed | Cyclomatic Complexity: RaiderIoLfgFetcher.mapCharacterProfile (cyclomatic 20) |
| REDACTED | 6.2 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java | 6.3 | Mixed | Cyclomatic Complexity: WowDataCrawlerService.runCrawl (cyclomatic 17) |
| src/main/java/followarcane/wowdatacrawler/api/v1/error/GlobalExceptionHandler.java | 6.3 | Mixed | Code Duplication: Edited copy of a member (9 corresponding lines) |
| REDACTED | 6.4 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/WowProgressLfgFetcher.java | 7.0 | Mixed | Cognitive Complexity: WowProgressLfgFetcher.fetchCharacterPageEnrich (cognitive 23) |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionNotifierService.java | 7.0 | Mixed | Code Duplication: Duplicated block (10 lines × 2) |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java | 7.4 | Mixed | Cyclomatic Complexity: LfgSourceSupport.mergeSourceOnto (cyclomatic 21) |
| build.gradle | 7.4 | Mixed | Platform End-of-Life: End-of-life framework: Spring Boot 2 |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/RaiderIOService.java | 7.8 | Mixed | Code Duplication: Duplicated block (8 lines × 2) |
| REDACTED | 7.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/test/java/followarcane/wowdatacrawler/WowDataCrawlerApplicationTests.java | 8.0 | Near-clean | Test Quality: No assertions (empty test): contextLoads |
| src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgLanguageMapper.java | 8.5 | Near-clean | Code Duplication: Edited copy of a member (9 corresponding lines) |
| src/main/java/followarcane/wowdatacrawler/WowDataCrawlerApplication.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/WowDataCrawlerApplication.java |
| src/main/java/followarcane/wowdatacrawler/api/v1/controller/AdminController.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/AdminController.java |
| src/main/java/followarcane/wowdatacrawler/api/v1/controller/HealthController.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/HealthController.java |
| src/main/java/followarcane/wowdatacrawler/api/v1/controller/WowDataCrawlerController.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/WowDataCrawlerController.java |
| src/main/java/followarcane/wowdatacrawler/api/v1/error/UserAlreadyExistsException.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/error/UserAlreadyExistsException.java |
| src/main/java/followarcane/wowdatacrawler/api/v1/error/UserNotFoundException.java | 8.5 | Near-clean | Code Coverage: Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/error/UserNotFoundException.java |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 61 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 61 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 94 of 206 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
- D12 Dependency Hygiene — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
- DM9 Scattered domain decisions — 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. Arm one resolves each comparison operand to the domain member it judges, and that binding exists only in a Roslyn compilation, which this run did not load. Arm two ran over the neutral model because this repository's frontend declares whether each construction is produced or passed. A rule decided in two places would not appear above.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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").
- 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.
- 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.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- 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".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was LfgSourceSupport.mergeSourceOnto at 21.
What to do
- Bring the 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with LfgSourceSupport.mergeSourceOnto (cyclomatic 21), RaiderIoLfgFetcher.mapCharacterProfile (cyclomatic 20), WowDataCrawlerService.runCrawl (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.4 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was WowProgressLfgFetcher.fetchCharacterPageEnrich at 23.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with WowProgressLfgFetcher.fetchCharacterPageEnrich (cognitive 23), LfgSourceSupport.mergeSourceOnto (cognitive 20), RaiderIoLfgFetcher.mapCharacterProfile (cognitive 20). — 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 6 together lifts Cognitive Complexity from 9.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
7 duplicated block group(s) detected. 4.5 % of the production lines (150 of 3,304) are in a reported copy. A further 3 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 3 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with GlobalExceptionHandler.java, LfgSourceSupport.java, LfgLanguageMapper.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with RaiderIOService.java, RaiderIoLfgFetcher.java, GlobalExceptionHandler.java. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with VersionNotifierService.java. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 14 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 23.5% — 30 file(s) below 50%. Measured from the Java/Kotlin suite (repository root, Gradle: the JaCoCo agent on the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 30 Low coverage finding(s) in Code Coverage — start with WowDataCrawlerApplication.java, AdminController.java, HealthController.java. — One of this dimension's main actionable groups (30 warning-level).
D10 · Test Quality
0 skipped, 1 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 11 tests.
What to do
- Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with WowDataCrawlerApplicationTests.java. — One of this dimension's main actionable groups (1 issue-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Java/Kotlin (repository root, Gradle): measured (0 flaky).
D12 · Dependency Hygiene
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 102 artifact(s) resolved, 102 of them gradable against Maven Central, and 99 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 5 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 1 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.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java (7×21=147); src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java (8×17=136); src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java (4×20=80)
What to do
- Resolve the 3 Hotspot finding(s) in Churn × Complexity Hotspots — start with LfgSourceSupport.java, WowDataCrawlerService.java, RaiderIoLfgFetcher.java. — One of this dimension's main actionable groups (3 warning-level).
D16 · Bus Factor
11 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java. Counted over 12 of the 62 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 3304 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 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 build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
33 % of calls cross a namespace and 2 % 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)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
23 finding(s): 0 critical, 22 high, 1 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 178) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 15 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (15). — One of this dimension's main actionable groups (15 issue-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).
- No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 3 medium, 1 low.
What to do
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 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
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 12 of the 62 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 1 end-of-life framework(s), read from 1 platform declaration(s) and 8 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with build.gradle. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX1 · Captive dependencies
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM12 · Ambient inputs in the domain
DM4 · Rich vs anemic model
- `BossRank` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/main/java/followarcane/wowdatacrawler/domain/model/BossRank.java:9
- `CharacterInfo` is an aggregate/entity with 27 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/main/java/followarcane/wowdatacrawler/domain/model/CharacterInfo.java:18
- `RaidProgression` is an aggregate/entity with 4 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/main/java/followarcane/wowdatacrawler/domain/model/RaidProgression.java:9
- `User` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/main/java/followarcane/wowdatacrawler/domain/model/User.java:15
- `WarcraftLogsData` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/main/java/followarcane/wowdatacrawler/domain/model/WarcraftLogsData.java:9
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
DM6 · Domain ↔ infrastructure boundary
DM7 · Repository granularity
- `CharacterInfoRepository` is a repository over `CharacterInfo`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `CharacterInfo` through its owning aggregate instead. — src/main/java/followarcane/wowdatacrawler/infrastructure/repository/CharacterInfoRepository.java:10
- `RaidProgressionRepository` is a repository over `RaidProgression`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `RaidProgression` through its owning aggregate instead. — src/main/java/followarcane/wowdatacrawler/infrastructure/repository/RaidProgressionRepository.java:6
- `UserRepository` is a repository over `User`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `User` through its owning aggregate instead. — src/main/java/followarcane/wowdatacrawler/infrastructure/repository/UserRepository.java:6
- `WarcraftLogsRepository` is a repository over `WarcraftLogsData`, which is an entity but not an aggregate root. Repositories should be per aggregate ROOT — loading/saving a child entity independently lets callers bypass the root's invariants. Access `WarcraftLogsData` through its owning aggregate instead. — src/main/java/followarcane/wowdatacrawler/infrastructure/repository/WarcraftLogsRepository.java:8
What to do
- Define repositories per aggregate root and keep the query handle inside them; reach child entities through their root so invariants can't be bypassed.
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- 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
What to do
- Run the test suite in CI via an explicit runner step for your stack, and gate merges on it.
P2 · Observability
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `build.gradle` 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`. — build.gradle:18
What to do
- Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P7 · Outbound HTTP resilience
P8 · Schema migrations
P9 · Domain vs controller coverage
- Domain coverage is 2%, against a bar of 50% for this row — the layer carrying the business rules is the least covered part of the codebase that matters most. Measured over the types this analyzer classifies as domain (aggregates, value objects, domain services), so code the classifier does not place in the domain is neither counted for nor against this figure.
What to do
- Raise unit-test coverage of the domain (aggregates, value objects, domain services) — that's where correctness matters most.
X12 · Unreachable branch
X23 · Unguarded diagnostic materialisation
X27 · Collection changed while being enumerated
X3 · Exception handling
- `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) — src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgOpenedAtParser.java:60, src/main/java/followarcane/wowdatacrawler/domain/converter/ResponseConverter.java:103
What to do
- Swallowed exception (caught, then discarded)
X4 · Structured logging
X5 · Nullable reference types
- 0/19 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 | 65.2 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 82.6 | Strong | Strongest area. |
| Maturity | 57.4 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 31.3 | Weak — gated by P3, P5, P9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 57.8 | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 65.6 | Adequate — gated by DM7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Not evidenced — 3 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.
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- 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 — docker build failed (exit 1) — ------ REDACTED:11 -------------------- 9 | 10 | COPY src ./src 11 | >>> RUN ./gradlew clean bootJar -x test --no-daemon 12 | 13 | FROM eclipse-temurin:17-jre-jammy AS runtime -------------------- ERROR: failed to solve: process "/bin/sh -c ./gradlew clean bootJar -x test --no-daemon" did not complete successfully: exit code: 1; likely cause (the repository): a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c ./gradlew clean bootJar -x test --no-daemon`): the build's own command failed, for example a compile or test error; runtime evidence skipped The cause is in the repository, not in our sandbox: a RUN step of the repository's REDACTED exited with code 1 (`/bin/sh -c ./gradlew clean bootJar -x test --no-daemon`): the build's own command failed, for example a compile or test error. 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (385 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (domain), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3304 LoC, 66 module-visible types across 19 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
- D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X16 Unfloored truncation loop — 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.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 23 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): contextLoads src/test/java/followarcane/wowdatacrawler/WowDataCrawlerApplicationTests.java:10
Serious — 71 finding(s)
- Low coverage: src/main/java/followarcane/wowdatacrawler/WowDataCrawlerApplication.java src/main/java/followarcane/wowdatacrawler/WowDataCrawlerApplication.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/AdminController.java src/main/java/followarcane/wowdatacrawler/api/v1/controller/AdminController.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/HealthController.java src/main/java/followarcane/wowdatacrawler/api/v1/controller/HealthController.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/controller/WowDataCrawlerController.java src/main/java/followarcane/wowdatacrawler/api/v1/controller/WowDataCrawlerController.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/error/GlobalExceptionHandler.java src/main/java/followarcane/wowdatacrawler/api/v1/error/GlobalExceptionHandler.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/error/UserAlreadyExistsException.java src/main/java/followarcane/wowdatacrawler/api/v1/error/UserAlreadyExistsException.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/api/v1/error/UserNotFoundException.java src/main/java/followarcane/wowdatacrawler/api/v1/error/UserNotFoundException.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/domain/converter/ResponseConverter.java src/main/java/followarcane/wowdatacrawler/domain/converter/ResponseConverter.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/domain/model/RaiderIOData.java src/main/java/followarcane/wowdatacrawler/domain/model/RaiderIOData.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/config/RestTemplateConfig.java src/main/java/followarcane/wowdatacrawler/infrastructure/config/RestTemplateConfig.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/persistence/DatabaseSeeder.java src/main/java/followarcane/wowdatacrawler/infrastructure/persistence/DatabaseSeeder.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/repository/WarcraftLogsRepository.java src/main/java/followarcane/wowdatacrawler/infrastructure/repository/WarcraftLogsRepository.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/UserService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/UserService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/WarcraftLogsService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/WarcraftLogsService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgFetchResult.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgFetchResult.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgOpenedAtParser.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgOpenedAtParser.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/WowProgressLfgFetcher.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/WowProgressLfgFetcher.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/repoService/CharacterInfoService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/repoService/CharacterInfoService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/repoService/WarcraftLogsDataService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/repoService/WarcraftLogsDataService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionNotifierService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionNotifierService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionStorageService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionStorageService.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/utils/Authorities.java src/main/java/followarcane/wowdatacrawler/infrastructure/utils/Authorities.java:1
- Low coverage: src/main/java/followarcane/wowdatacrawler/infrastructure/utils/Regions.java src/main/java/followarcane/wowdatacrawler/infrastructure/utils/Regions.java:1
- Anemic entity: BossRank src/main/java/followarcane/wowdatacrawler/domain/model/BossRank.java:9
- Anemic entity: CharacterInfo src/main/java/followarcane/wowdatacrawler/domain/model/CharacterInfo.java:18
- Anemic entity: RaidProgression src/main/java/followarcane/wowdatacrawler/domain/model/RaidProgression.java:9
- Anemic entity: User src/main/java/followarcane/wowdatacrawler/domain/model/User.java:15
- Anemic entity: WarcraftLogsData src/main/java/followarcane/wowdatacrawler/domain/model/WarcraftLogsData.java:9
- Repository for a non-root entity: CharacterInfoRepository → CharacterInfo src/main/java/followarcane/wowdatacrawler/infrastructure/repository/CharacterInfoRepository.java:10
- Repository for a non-root entity: RaidProgressionRepository → RaidProgression src/main/java/followarcane/wowdatacrawler/infrastructure/repository/RaidProgressionRepository.java:6
- Repository for a non-root entity: UserRepository → User src/main/java/followarcane/wowdatacrawler/infrastructure/repository/UserRepository.java:6
- Repository for a non-root entity: WarcraftLogsRepository → WarcraftLogsData src/main/java/followarcane/wowdatacrawler/infrastructure/repository/WarcraftLogsRepository.java:8
- Hotspot: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java:91
- Hotspot: src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java:58
- Hotspot: src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:146
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (9 corresponding lines) src/main/java/followarcane/wowdatacrawler/api/v1/error/GlobalExceptionHandler.java:16
- Edited copy of a member (9 corresponding lines) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java:204
- Edited copy of a member (9 corresponding lines) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgLanguageMapper.java:131
- Duplicated block (8 lines × 2) src/main/java/followarcane/wowdatacrawler/infrastructure/service/RaiderIOService.java:145
- Duplicated block (8 lines × 2) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:297
- Duplicated block (8 lines × 2) src/main/java/followarcane/wowdatacrawler/api/v1/error/GlobalExceptionHandler.java:17
- Swallowed exception (caught, then discarded) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgOpenedAtParser.java:60
- Swallowed exception (caught, then discarded) src/main/java/followarcane/wowdatacrawler/domain/converter/ResponseConverter.java:103
- LfgSourceSupport.mergeSourceOnto (cyclomatic 21) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java:91
- RaiderIoLfgFetcher.mapCharacterProfile (cyclomatic 20) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:146
- WowDataCrawlerService.runCrawl (cyclomatic 17) src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java:58
- WowProgressLfgFetcher.fetchCharacterPageEnrich (cognitive 23) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/WowProgressLfgFetcher.java:102
- LfgSourceSupport.mergeSourceOnto (cognitive 20) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/LfgSourceSupport.java:91
- RaiderIoLfgFetcher.mapCharacterProfile (cognitive 20) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:146
- RaiderIoLfgFetcher.boolOrNull (cognitive 19) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:323
- WowDataCrawlerService.runCrawl (cognitive 19) src/main/java/followarcane/wowdatacrawler/infrastructure/service/WowDataCrawlerService.java:58
- RaiderIoLfgFetcher.intOrNull (cognitive 16) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:296
- REDACTED
- REDACTED
- Duplicated block (10 lines × 2) src/main/java/followarcane/wowdatacrawler/infrastructure/service/version/VersionNotifierService.java:72
- Duplicated block (6 lines × 2) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:358
- Duplicated block (5 lines × 3) src/main/java/followarcane/wowdatacrawler/infrastructure/service/lfg/RaiderIoLfgFetcher.java:349
- Duplicated block (10 lines × 3) src/main/java/followarcane/wowdatacrawler/infrastructure/service/RaiderIOService.java:207
- End-of-life framework: Spring Boot 2 build.gradle:1
- No DR/backup evidence
- Low domain coverage
Minor — 13 finding(s)
- Off-boarding risk: anonymized user #1
- No ADRs found build.gradle:3
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation build.gradle:18
- No changelog
- Java packages are not null-marked everywhere
Minor — 99 finding(s)
- Outdated (compile): org.projectlombok:lombok
- Outdated (compile): org.springframework.boot:spring-boot-starter-web
- Outdated (compile): org.springframework.boot:spring-boot-starter
- Outdated (compile): org.springframework.boot:spring-boot
- Outdated (compile): org.springframework:spring-core
- Outdated (compile): org.springframework:spring-jcl
- Outdated (compile): org.springframework:spring-context
- Outdated (compile): org.springframework:spring-aop
- Outdated (compile): org.springframework:spring-beans
- Outdated (compile): org.springframework:spring-expression
- Outdated (compile): org.springframework.boot:spring-boot-autoconfigure
- Outdated (compile): org.springframework.boot:spring-boot-starter-logging
- Outdated (compile): ch.qos.logback:logback-classic
- Outdated (compile): ch.qos.logback:logback-core
- Outdated (compile): org.slf4j:slf4j-api
- Outdated (compile): org.apache.logging.log4j:log4j-to-slf4j
- Outdated (compile): org.apache.logging.log4j:log4j-api
- Outdated (compile): org.slf4j:jul-to-slf4j
- Outdated (compile): jakarta.annotation:jakarta.annotation-api
- Outdated (compile): org.yaml:snakeyaml
- Outdated (compile): org.springframework.boot:spring-boot-starter-json
- Outdated (compile): org.springframework:spring-web
- Outdated (compile): com.fasterxml.jackson.core:jackson-databind
- Outdated (compile): com.fasterxml.jackson.core:jackson-annotations
- Outdated (compile): com.fasterxml.jackson:jackson-bom
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2f223550a4fc478b8455acb7be299dc5/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-2f223550a4fc478b8455acb7be299dc5/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 23 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet). | 0 | — |