Executive summary
epi052/feroxbuster falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 62 out of 100 and is rated Adequate, and all 65 of its critical findings are security problems.
Maturity, at 55, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 7 points. Having someone learn and document the 29 files no active contributor knows is another step, worth about 5 points. Raising Maturity to 70 would lift the score to about 67.
Fifty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and four pipeline steps run downloads nobody checks. Pinning each tool to an exact version, limiting each secret to its own step and checking each download against a checksum would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once.
The product code is 21,691 lines, about €31,000 to rebuild.
If Maturity rose from 55 to 70, the lowest score rated Strong, the score would rise from 62 to about 67.
New since the last survey: 10 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 1 finding
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €31,000 · Estimate
| Cost to rebuild | €10,000 to €52,000, for 173 to 550 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 62. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Medium: 21,691 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 event_handlers.command | 2 nlp.term | 3 scan_manager.order | 4 scanner.utils | 5 sync.dynamic_semaphore | 6 config.utils | 7 event_handlers.outputs | 8 filters.container | 9 nlp.document | 10 scan_manager.menu | 11 statistics.container | 12 event_handlers.filters | 13 event_handlers.statistics | 14 scan_manager.scan | 15 scanner.policy_data | 16 scan_manager.scan_container | 17 event_handlers.scans | 18 event_handlers.container | 19 response | 20 scanner.requester | 21 extractor.builder | 22 heuristics | 23 scan_manager.response_container | 24 scanner.ferox_scanner | 25 traits | 26 config.container | 27 extractor.container | 28 filters.empty | 29 filters.lines | 30 filters.regex | 31 filters.similarity | 32 filters.size | 33 filters.status_code | 34 filters.wildcard | 35 filters.words | 36 banner.container | 37 main | 38 scan_manager.state | 39 scan_manager.utils | 40 utils |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 event_handlers.command | ||||||||||||||||||||||||||||||||||||||||
| 2 nlp.term | ||||||||||||||||||||||||||||||||||||||||
| 3 scan_manager.order | ||||||||||||||||||||||||||||||||||||||||
| 4 scanner.utils | ||||||||||||||||||||||||||||||||||||||||
| 5 sync.dynamic_semaphore | ||||||||||||||||||||||||||||||||||||||||
| 6 config.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 7 event_handlers.outputs | 1 | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||||
| 8 filters.container | 1 | |||||||||||||||||||||||||||||||||||||||
| 9 nlp.document | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 scan_manager.menu | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 statistics.container | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 event_handlers.filters | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 13 event_handlers.statistics | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||||||
| 14 scan_manager.scan | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 scanner.policy_data | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 scan_manager.scan_container | 1 | 1 | 1 | 2 | 2 | 1 | ||||||||||||||||||||||||||||||||||
| 17 event_handlers.scans | 1 | 1 | 1 | 1 | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 18 event_handlers.container | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 19 response | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 scanner.requester | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 extractor.builder | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 heuristics | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 scan_manager.response_container | 1 | |||||||||||||||||||||||||||||||||||||||
| 24 scanner.ferox_scanner | 1 | 2 | 2 | 2 | 1 | |||||||||||||||||||||||||||||||||||
| 25 traits | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 config.container | 3 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 extractor.container | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 28 filters.empty | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 filters.lines | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 filters.regex | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 filters.similarity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 filters.size | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 filters.status_code | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 filters.wildcard | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 filters.words | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 36 banner.container | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 37 main | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 scan_manager.state | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 39 scan_manager.utils | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 utils | 1 | 1 | 1 | 1 |
6→26 config.utils uses config.container part of a loop✕
- Connections
- 1 pair of types, where a type in config.utils uses a type in config.container.
- The types involved
feroxbuster.config.utils.utils$module→feroxbuster.config.container.Configuration
- Direction
- config.utils uses config.container, so a change to config.container can break config.utils, while a change to config.utils can't break config.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→1 event_handlers.outputs uses event_handlers.command✕
- Connections
- 1 pair of types, where a type in event_handlers.outputs uses a type in event_handlers.command.
- The types involved
feroxbuster.event_handlers.outputs.TermOutHandle→feroxbuster.event_handlers.command.Command
- Direction
- event_handlers.outputs uses event_handlers.command, so a change to event_handlers.command can break event_handlers.outputs, while a change to event_handlers.outputs can't break event_handlers.command.
- Position
- Below the diagonal: event_handlers.outputs uses a module listed above it, which is the healthy direction.
7→18 event_handlers.outputs uses event_handlers.container part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.outputs uses a type in event_handlers.container.
- The types involved
feroxbuster.event_handlers.outputs.TermOutHandler→feroxbuster.event_handlers.container.Handles
- Direction
- event_handlers.outputs uses event_handlers.container, so a change to event_handlers.container can break event_handlers.outputs, while a change to event_handlers.outputs can't break event_handlers.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→19 event_handlers.outputs uses response part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.outputs uses a type in response.
- The types involved
feroxbuster.event_handlers.outputs.TermOutHandler→feroxbuster.response.FeroxResponse
- Direction
- event_handlers.outputs uses response, so a change to response can break event_handlers.outputs, while a change to event_handlers.outputs can't break response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
7→26 event_handlers.outputs uses config.container part of a loop✕
- Connections
- 2 pairs of types, where a type in event_handlers.outputs uses a type in config.container.
- The types involved
feroxbuster.event_handlers.outputs.FileOutHandler→feroxbuster.config.container.Configurationferoxbuster.event_handlers.outputs.TermOutHandler→feroxbuster.config.container.Configuration
- Direction
- event_handlers.outputs uses config.container, so a change to config.container can break event_handlers.outputs, while a change to event_handlers.outputs can't break config.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→19 filters.container uses response part of a loop✕
- Connections
- 1 pair of types, where a type in filters.container uses a type in response.
- The types involved
feroxbuster.filters.container.FeroxFilters→feroxbuster.response.FeroxResponse
- Direction
- filters.container uses response, so a change to response can break filters.container, while a change to filters.container can't break response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→2 nlp.document uses nlp.term✕
- Connections
- 1 pair of types, where a type in nlp.document uses a type in nlp.term.
- The types involved
feroxbuster.nlp.document.Document→feroxbuster.nlp.term.Term
- Direction
- nlp.document uses nlp.term, so a change to nlp.term can break nlp.document, while a change to nlp.document can't break nlp.term.
- Position
- Below the diagonal: nlp.document uses a module listed above it, which is the healthy direction.
10→2 scan_manager.menu uses nlp.term✕
- Connections
- 1 pair of types, where a type in scan_manager.menu uses a type in nlp.term.
- The types involved
feroxbuster.scan_manager.menu.Menu→feroxbuster.nlp.term.Term
- Direction
- scan_manager.menu uses nlp.term, so a change to nlp.term can break scan_manager.menu, while a change to scan_manager.menu can't break nlp.term.
- Position
- Below the diagonal: scan_manager.menu uses a module listed above it, which is the healthy direction.
10→5 scan_manager.menu uses sync.dynamic_semaphore✕
- Connections
- 1 pair of types, where a type in scan_manager.menu uses a type in sync.dynamic_semaphore.
- The types involved
feroxbuster.scan_manager.menu.Menu→feroxbuster.sync.dynamic_semaphore.DynamicSemaphore
- Direction
- scan_manager.menu uses sync.dynamic_semaphore, so a change to sync.dynamic_semaphore can break scan_manager.menu, while a change to scan_manager.menu can't break sync.dynamic_semaphore.
- Position
- Below the diagonal: scan_manager.menu uses a module listed above it, which is the healthy direction.
11→25 statistics.container uses traits part of a loop✕
- Connections
- 1 pair of types, where a type in statistics.container uses a type in traits.
- The types involved
feroxbuster.statistics.container.Stats→feroxbuster.traits.FeroxSerialize
- Direction
- statistics.container uses traits, so a change to traits can break statistics.container, while a change to statistics.container can't break traits.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→1 event_handlers.filters uses event_handlers.command✕
- Connections
- 1 pair of types, where a type in event_handlers.filters uses a type in event_handlers.command.
- The types involved
feroxbuster.event_handlers.filters.FiltersHandle→feroxbuster.event_handlers.command.Command
- Direction
- event_handlers.filters uses event_handlers.command, so a change to event_handlers.command can break event_handlers.filters, while a change to event_handlers.filters can't break event_handlers.command.
- Position
- Below the diagonal: event_handlers.filters uses a module listed above it, which is the healthy direction.
12→8 event_handlers.filters uses filters.container✕
- Connections
- 2 pairs of types, where a type in event_handlers.filters uses a type in filters.container.
- The types involved
feroxbuster.event_handlers.filters.FiltersHandle→feroxbuster.filters.container.FeroxFiltersferoxbuster.event_handlers.filters.FiltersHandler→feroxbuster.filters.container.FeroxFilters
- Direction
- event_handlers.filters uses filters.container, so a change to filters.container can break event_handlers.filters, while a change to event_handlers.filters can't break filters.container.
- Position
- Below the diagonal: event_handlers.filters uses a module listed above it, which is the healthy direction.
13→1 event_handlers.statistics uses event_handlers.command✕
- Connections
- 1 pair of types, where a type in event_handlers.statistics uses a type in event_handlers.command.
- The types involved
feroxbuster.event_handlers.statistics.StatsHandle→feroxbuster.event_handlers.command.Command
- Direction
- event_handlers.statistics uses event_handlers.command, so a change to event_handlers.command can break event_handlers.statistics, while a change to event_handlers.statistics can't break event_handlers.command.
- Position
- Below the diagonal: event_handlers.statistics uses a module listed above it, which is the healthy direction.
13→11 event_handlers.statistics uses statistics.container✕
- Connections
- 2 pairs of types, where a type in event_handlers.statistics uses a type in statistics.container.
- The types involved
feroxbuster.event_handlers.statistics.StatsHandle→feroxbuster.statistics.container.Statsferoxbuster.event_handlers.statistics.StatsHandler→feroxbuster.statistics.container.Stats
- Direction
- event_handlers.statistics uses statistics.container, so a change to statistics.container can break event_handlers.statistics, while a change to event_handlers.statistics can't break statistics.container.
- Position
- Below the diagonal: event_handlers.statistics uses a module listed above it, which is the healthy direction.
13→26 event_handlers.statistics uses config.container part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.statistics uses a type in config.container.
- The types involved
feroxbuster.event_handlers.statistics.StatsHandler→feroxbuster.config.container.Configuration
- Direction
- event_handlers.statistics uses config.container, so a change to config.container can break event_handlers.statistics, while a change to event_handlers.statistics can't break config.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→3 scan_manager.scan uses scan_manager.order✕
- Connections
- 1 pair of types, where a type in scan_manager.scan uses a type in scan_manager.order.
- The types involved
feroxbuster.scan_manager.scan.FeroxScan→feroxbuster.scan_manager.order.ScanOrder
- Direction
- scan_manager.scan uses scan_manager.order, so a change to scan_manager.order can break scan_manager.scan, while a change to scan_manager.scan can't break scan_manager.order.
- Position
- Below the diagonal: scan_manager.scan uses a module listed above it, which is the healthy direction.
14→4 scan_manager.scan uses scanner.utils✕
- Connections
- 1 pair of types, where a type in scan_manager.scan uses a type in scanner.utils.
- The types involved
feroxbuster.scan_manager.scan.FeroxScan→feroxbuster.scanner.utils.PolicyTrigger
- Direction
- scan_manager.scan uses scanner.utils, so a change to scanner.utils can break scan_manager.scan, while a change to scan_manager.scan can't break scanner.utils.
- Position
- Below the diagonal: scan_manager.scan uses a module listed above it, which is the healthy direction.
14→6 scan_manager.scan uses config.utils✕
- Connections
- 1 pair of types, where a type in scan_manager.scan uses a type in config.utils.
- The types involved
feroxbuster.scan_manager.scan.FeroxScan→feroxbuster.config.utils.OutputLevel
- Direction
- scan_manager.scan uses config.utils, so a change to config.utils can break scan_manager.scan, while a change to scan_manager.scan can't break config.utils.
- Position
- Below the diagonal: scan_manager.scan uses a module listed above it, which is the healthy direction.
14→18 scan_manager.scan uses event_handlers.container part of a loop✕
- Connections
- 1 pair of types, where a type in scan_manager.scan uses a type in event_handlers.container.
- The types involved
feroxbuster.scan_manager.scan.FeroxScan→feroxbuster.event_handlers.container.Handles
- Direction
- scan_manager.scan uses event_handlers.container, so a change to event_handlers.container can break scan_manager.scan, while a change to scan_manager.scan can't break event_handlers.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→4 scanner.policy_data uses scanner.utils✕
- Connections
- 1 pair of types, where a type in scanner.policy_data uses a type in scanner.utils.
- The types involved
feroxbuster.scanner.policy_data.PolicyData→feroxbuster.scanner.utils.PolicyTrigger
- Direction
- scanner.policy_data uses scanner.utils, so a change to scanner.utils can break scanner.policy_data, while a change to scanner.policy_data can't break scanner.utils.
- Position
- Below the diagonal: scanner.policy_data uses a module listed above it, which is the healthy direction.
15→6 scanner.policy_data uses config.utils✕
- Connections
- 1 pair of types, where a type in scanner.policy_data uses a type in config.utils.
- The types involved
feroxbuster.scanner.policy_data.PolicyData→feroxbuster.config.utils.RequesterPolicy
- Direction
- scanner.policy_data uses config.utils, so a change to config.utils can break scanner.policy_data, while a change to scanner.policy_data can't break config.utils.
- Position
- Below the diagonal: scanner.policy_data uses a module listed above it, which is the healthy direction.
16→3 scan_manager.scan_container uses scan_manager.order✕
- Connections
- 1 pair of types, where a type in scan_manager.scan_container uses a type in scan_manager.order.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.scan_manager.order.ScanOrder
- Direction
- scan_manager.scan_container uses scan_manager.order, so a change to scan_manager.order can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break scan_manager.order.
- Position
- Below the diagonal: scan_manager.scan_container uses a module listed above it, which is the healthy direction.
16→5 scan_manager.scan_container uses sync.dynamic_semaphore✕
- Connections
- 1 pair of types, where a type in scan_manager.scan_container uses a type in sync.dynamic_semaphore.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.sync.dynamic_semaphore.DynamicSemaphore
- Direction
- scan_manager.scan_container uses sync.dynamic_semaphore, so a change to sync.dynamic_semaphore can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break sync.dynamic_semaphore.
- Position
- Below the diagonal: scan_manager.scan_container uses a module listed above it, which is the healthy direction.
16→6 scan_manager.scan_container uses config.utils✕
- Connections
- 1 pair of types, where a type in scan_manager.scan_container uses a type in config.utils.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.config.utils.OutputLevel
- Direction
- scan_manager.scan_container uses config.utils, so a change to config.utils can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break config.utils.
- Position
- Below the diagonal: scan_manager.scan_container uses a module listed above it, which is the healthy direction.
16→10 scan_manager.scan_container uses scan_manager.menu✕
- Connections
- 2 pairs of types, where a type in scan_manager.scan_container uses a type in scan_manager.menu.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.scan_manager.menu.Menuferoxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.scan_manager.menu.MenuCmdResult
- Direction
- scan_manager.scan_container uses scan_manager.menu, so a change to scan_manager.menu can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break scan_manager.menu.
- Position
- Below the diagonal: scan_manager.scan_container uses a module listed above it, which is the healthy direction.
16→14 scan_manager.scan_container uses scan_manager.scan✕
- Connections
- 2 pairs of types, where a type in scan_manager.scan_container uses a type in scan_manager.scan.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.scan_manager.scan.FeroxScanferoxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.scan_manager.scan.ScanType
- Direction
- scan_manager.scan_container uses scan_manager.scan, so a change to scan_manager.scan can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break scan_manager.scan.
- Position
- Below the diagonal: scan_manager.scan_container uses a module listed above it, which is the healthy direction.
16→18 scan_manager.scan_container uses event_handlers.container part of a loop✕
- Connections
- 1 pair of types, where a type in scan_manager.scan_container uses a type in event_handlers.container.
- The types involved
feroxbuster.scan_manager.scan_container.FeroxScans→feroxbuster.event_handlers.container.Handles
- Direction
- scan_manager.scan_container uses event_handlers.container, so a change to event_handlers.container can break scan_manager.scan_container, while a change to scan_manager.scan_container can't break event_handlers.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→1 event_handlers.scans uses event_handlers.command✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in event_handlers.command.
- The types involved
feroxbuster.event_handlers.scans.ScanHandle→feroxbuster.event_handlers.command.Command
- Direction
- event_handlers.scans uses event_handlers.command, so a change to event_handlers.command can break event_handlers.scans, while a change to event_handlers.scans can't break event_handlers.command.
- Position
- Below the diagonal: event_handlers.scans uses a module listed above it, which is the healthy direction.
17→3 event_handlers.scans uses scan_manager.order✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in scan_manager.order.
- The types involved
feroxbuster.event_handlers.scans.ScanHandler→feroxbuster.scan_manager.order.ScanOrder
- Direction
- event_handlers.scans uses scan_manager.order, so a change to scan_manager.order can break event_handlers.scans, while a change to event_handlers.scans can't break scan_manager.order.
- Position
- Below the diagonal: event_handlers.scans uses a module listed above it, which is the healthy direction.
17→5 event_handlers.scans uses sync.dynamic_semaphore✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in sync.dynamic_semaphore.
- The types involved
feroxbuster.event_handlers.scans.ScanHandler→feroxbuster.sync.dynamic_semaphore.DynamicSemaphore
- Direction
- event_handlers.scans uses sync.dynamic_semaphore, so a change to sync.dynamic_semaphore can break event_handlers.scans, while a change to event_handlers.scans can't break sync.dynamic_semaphore.
- Position
- Below the diagonal: event_handlers.scans uses a module listed above it, which is the healthy direction.
17→14 event_handlers.scans uses scan_manager.scan✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in scan_manager.scan.
- The types involved
feroxbuster.event_handlers.scans.ScanHandler→feroxbuster.scan_manager.scan.FeroxScan
- Direction
- event_handlers.scans uses scan_manager.scan, so a change to scan_manager.scan can break event_handlers.scans, while a change to event_handlers.scans can't break scan_manager.scan.
- Position
- Below the diagonal: event_handlers.scans uses a module listed above it, which is the healthy direction.
17→16 event_handlers.scans uses scan_manager.scan_container✕
- Connections
- 2 pairs of types, where a type in event_handlers.scans uses a type in scan_manager.scan_container.
- The types involved
feroxbuster.event_handlers.scans.ScanHandle→feroxbuster.scan_manager.scan_container.FeroxScansferoxbuster.event_handlers.scans.ScanHandler→feroxbuster.scan_manager.scan_container.FeroxScans
- Direction
- event_handlers.scans uses scan_manager.scan_container, so a change to scan_manager.scan_container can break event_handlers.scans, while a change to event_handlers.scans can't break scan_manager.scan_container.
- Position
- Below the diagonal: event_handlers.scans uses a module listed above it, which is the healthy direction.
17→18 event_handlers.scans uses event_handlers.container part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in event_handlers.container.
- The types involved
feroxbuster.event_handlers.scans.ScanHandler→feroxbuster.event_handlers.container.Handles
- Direction
- event_handlers.scans uses event_handlers.container, so a change to event_handlers.container can break event_handlers.scans, while a change to event_handlers.scans can't break event_handlers.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→19 event_handlers.scans uses response part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.scans uses a type in response.
- The types involved
feroxbuster.event_handlers.scans.ScanHandler→feroxbuster.response.FeroxResponse
- Direction
- event_handlers.scans uses response, so a change to response can break event_handlers.scans, while a change to event_handlers.scans can't break response.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→1 event_handlers.container uses event_handlers.command✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in event_handlers.command.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.event_handlers.command.Command
- Direction
- event_handlers.container uses event_handlers.command, so a change to event_handlers.command can break event_handlers.container, while a change to event_handlers.container can't break event_handlers.command.
- Position
- Below the diagonal: event_handlers.container uses a module listed above it, which is the healthy direction.
18→7 event_handlers.container uses event_handlers.outputs✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in event_handlers.outputs.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.event_handlers.outputs.TermOutHandle
- Direction
- event_handlers.container uses event_handlers.outputs, so a change to event_handlers.outputs can break event_handlers.container, while a change to event_handlers.container can't break event_handlers.outputs.
- Position
- Below the diagonal: event_handlers.container uses a module listed above it, which is the healthy direction.
18→12 event_handlers.container uses event_handlers.filters✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in event_handlers.filters.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.event_handlers.filters.FiltersHandle
- Direction
- event_handlers.container uses event_handlers.filters, so a change to event_handlers.filters can break event_handlers.container, while a change to event_handlers.container can't break event_handlers.filters.
- Position
- Below the diagonal: event_handlers.container uses a module listed above it, which is the healthy direction.
18→13 event_handlers.container uses event_handlers.statistics✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in event_handlers.statistics.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.event_handlers.statistics.StatsHandle
- Direction
- event_handlers.container uses event_handlers.statistics, so a change to event_handlers.statistics can break event_handlers.container, while a change to event_handlers.container can't break event_handlers.statistics.
- Position
- Below the diagonal: event_handlers.container uses a module listed above it, which is the healthy direction.
18→17 event_handlers.container uses event_handlers.scans✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in event_handlers.scans.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.event_handlers.scans.ScanHandle
- Direction
- event_handlers.container uses event_handlers.scans, so a change to event_handlers.scans can break event_handlers.container, while a change to event_handlers.container can't break event_handlers.scans.
- Position
- Below the diagonal: event_handlers.container uses a module listed above it, which is the healthy direction.
18→26 event_handlers.container uses config.container part of a loop✕
- Connections
- 1 pair of types, where a type in event_handlers.container uses a type in config.container.
- The types involved
feroxbuster.event_handlers.container.Handles→feroxbuster.config.container.Configuration
- Direction
- event_handlers.container uses config.container, so a change to config.container can break event_handlers.container, while a change to event_handlers.container can't break config.container.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→6 response uses config.utils✕
- Connections
- 1 pair of types, where a type in response uses a type in config.utils.
- The types involved
feroxbuster.response.FeroxResponse→feroxbuster.config.utils.OutputLevel
- Direction
- response uses config.utils, so a change to config.utils can break response, while a change to response can't break config.utils.
- Position
- Below the diagonal: response uses a module listed above it, which is the healthy direction.
19→18 response uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in response uses a type in event_handlers.container.
- The types involved
feroxbuster.response.FeroxResponse→feroxbuster.event_handlers.container.Handles
- Direction
- response uses event_handlers.container, so a change to event_handlers.container can break response, while a change to response can't break event_handlers.container.
- Position
- Below the diagonal: response uses a module listed above it, which is the healthy direction.
19→25 response uses traits part of a loop✕
- Connections
- 1 pair of types, where a type in response uses a type in traits.
- The types involved
feroxbuster.response.FeroxResponse→feroxbuster.traits.FeroxSerialize
- Direction
- response uses traits, so a change to traits can break response, while a change to response can't break traits.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→4 scanner.requester uses scanner.utils✕
- Connections
- 1 pair of types, where a type in scanner.requester uses a type in scanner.utils.
- The types involved
feroxbuster.scanner.requester.Requester→feroxbuster.scanner.utils.PolicyTrigger
- Direction
- scanner.requester uses scanner.utils, so a change to scanner.utils can break scanner.requester, while a change to scanner.requester can't break scanner.utils.
- Position
- Below the diagonal: scanner.requester uses a module listed above it, which is the healthy direction.
20→14 scanner.requester uses scan_manager.scan✕
- Connections
- 1 pair of types, where a type in scanner.requester uses a type in scan_manager.scan.
- The types involved
feroxbuster.scanner.requester.Requester→feroxbuster.scan_manager.scan.FeroxScan
- Direction
- scanner.requester uses scan_manager.scan, so a change to scan_manager.scan can break scanner.requester, while a change to scanner.requester can't break scan_manager.scan.
- Position
- Below the diagonal: scanner.requester uses a module listed above it, which is the healthy direction.
20→15 scanner.requester uses scanner.policy_data✕
- Connections
- 1 pair of types, where a type in scanner.requester uses a type in scanner.policy_data.
- The types involved
feroxbuster.scanner.requester.Requester→feroxbuster.scanner.policy_data.PolicyData
- Direction
- scanner.requester uses scanner.policy_data, so a change to scanner.policy_data can break scanner.requester, while a change to scanner.requester can't break scanner.policy_data.
- Position
- Below the diagonal: scanner.requester uses a module listed above it, which is the healthy direction.
20→18 scanner.requester uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in scanner.requester uses a type in event_handlers.container.
- The types involved
feroxbuster.scanner.requester.Requester→feroxbuster.event_handlers.container.Handles
- Direction
- scanner.requester uses event_handlers.container, so a change to event_handlers.container can break scanner.requester, while a change to scanner.requester can't break event_handlers.container.
- Position
- Below the diagonal: scanner.requester uses a module listed above it, which is the healthy direction.
20→24 scanner.requester uses scanner.ferox_scanner part of a loop✕
- Connections
- 1 pair of types, where a type in scanner.requester uses a type in scanner.ferox_scanner.
- The types involved
feroxbuster.scanner.requester.Requester→feroxbuster.scanner.ferox_scanner.FeroxScanner
- Direction
- scanner.requester uses scanner.ferox_scanner, so a change to scanner.ferox_scanner can break scanner.requester, while a change to scanner.requester can't break scanner.ferox_scanner.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→18 extractor.builder uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in extractor.builder uses a type in event_handlers.container.
- The types involved
feroxbuster.extractor.builder.ExtractorBuilder→feroxbuster.event_handlers.container.Handles
- Direction
- extractor.builder uses event_handlers.container, so a change to event_handlers.container can break extractor.builder, while a change to extractor.builder can't break event_handlers.container.
- Position
- Below the diagonal: extractor.builder uses a module listed above it, which is the healthy direction.
21→19 extractor.builder uses response✕
- Connections
- 1 pair of types, where a type in extractor.builder uses a type in response.
- The types involved
feroxbuster.extractor.builder.ExtractorBuilder→feroxbuster.response.FeroxResponse
- Direction
- extractor.builder uses response, so a change to response can break extractor.builder, while a change to extractor.builder can't break response.
- Position
- Below the diagonal: extractor.builder uses a module listed above it, which is the healthy direction.
22→18 heuristics uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in heuristics uses a type in event_handlers.container.
- The types involved
feroxbuster.heuristics.HeuristicTests→feroxbuster.event_handlers.container.Handles
- Direction
- heuristics uses event_handlers.container, so a change to event_handlers.container can break heuristics, while a change to heuristics can't break event_handlers.container.
- Position
- Below the diagonal: heuristics uses a module listed above it, which is the healthy direction.
22→19 heuristics uses response✕
- Connections
- 1 pair of types, where a type in heuristics uses a type in response.
- The types involved
feroxbuster.heuristics.DirListingResult→feroxbuster.response.FeroxResponse
- Direction
- heuristics uses response, so a change to response can break heuristics, while a change to heuristics can't break response.
- Position
- Below the diagonal: heuristics uses a module listed above it, which is the healthy direction.
23→19 scan_manager.response_container uses response✕
- Connections
- 1 pair of types, where a type in scan_manager.response_container uses a type in response.
- The types involved
feroxbuster.scan_manager.response_container.FeroxResponses→feroxbuster.response.FeroxResponse
- Direction
- scan_manager.response_container uses response, so a change to response can break scan_manager.response_container, while a change to scan_manager.response_container can't break response.
- Position
- Below the diagonal: scan_manager.response_container uses a module listed above it, which is the healthy direction.
24→3 scanner.ferox_scanner uses scan_manager.order✕
- Connections
- 1 pair of types, where a type in scanner.ferox_scanner uses a type in scan_manager.order.
- The types involved
feroxbuster.scanner.ferox_scanner.FeroxScanner→feroxbuster.scan_manager.order.ScanOrder
- Direction
- scanner.ferox_scanner uses scan_manager.order, so a change to scan_manager.order can break scanner.ferox_scanner, while a change to scanner.ferox_scanner can't break scan_manager.order.
- Position
- Below the diagonal: scanner.ferox_scanner uses a module listed above it, which is the healthy direction.
24→5 scanner.ferox_scanner uses sync.dynamic_semaphore✕
- Connections
- 2 pairs of types, where a type in scanner.ferox_scanner uses a type in sync.dynamic_semaphore.
- The types involved
feroxbuster.scanner.ferox_scanner.FeroxScanner→feroxbuster.sync.dynamic_semaphore.DynamicSemaphoreferoxbuster.scanner.ferox_scanner.ferox_scanner$module→feroxbuster.sync.dynamic_semaphore.DynamicSemaphore
- Direction
- scanner.ferox_scanner uses sync.dynamic_semaphore, so a change to sync.dynamic_semaphore can break scanner.ferox_scanner, while a change to scanner.ferox_scanner can't break sync.dynamic_semaphore.
- Position
- Below the diagonal: scanner.ferox_scanner uses a module listed above it, which is the healthy direction.
24→16 scanner.ferox_scanner uses scan_manager.scan_container✕
- Connections
- 2 pairs of types, where a type in scanner.ferox_scanner uses a type in scan_manager.scan_container.
- The types involved
feroxbuster.scanner.ferox_scanner.FeroxScanner→feroxbuster.scan_manager.scan_container.FeroxScansferoxbuster.scanner.ferox_scanner.ferox_scanner$module→feroxbuster.scan_manager.scan_container.FeroxScans
- Direction
- scanner.ferox_scanner uses scan_manager.scan_container, so a change to scan_manager.scan_container can break scanner.ferox_scanner, while a change to scanner.ferox_scanner can't break scan_manager.scan_container.
- Position
- Below the diagonal: scanner.ferox_scanner uses a module listed above it, which is the healthy direction.
24→18 scanner.ferox_scanner uses event_handlers.container✕
- Connections
- 2 pairs of types, where a type in scanner.ferox_scanner uses a type in event_handlers.container.
- The types involved
feroxbuster.scanner.ferox_scanner.FeroxScanner→feroxbuster.event_handlers.container.Handlesferoxbuster.scanner.ferox_scanner.ferox_scanner$module→feroxbuster.event_handlers.container.Handles
- Direction
- scanner.ferox_scanner uses event_handlers.container, so a change to event_handlers.container can break scanner.ferox_scanner, while a change to scanner.ferox_scanner can't break event_handlers.container.
- Position
- Below the diagonal: scanner.ferox_scanner uses a module listed above it, which is the healthy direction.
24→20 scanner.ferox_scanner uses scanner.requester✕
- Connections
- 1 pair of types, where a type in scanner.ferox_scanner uses a type in scanner.requester.
- The types involved
feroxbuster.scanner.ferox_scanner.FeroxScanner→feroxbuster.scanner.requester.Requester
- Direction
- scanner.ferox_scanner uses scanner.requester, so a change to scanner.requester can break scanner.ferox_scanner, while a change to scanner.ferox_scanner can't break scanner.requester.
- Position
- Below the diagonal: scanner.ferox_scanner uses a module listed above it, which is the healthy direction.
25→19 traits uses response✕
- Connections
- 1 pair of types, where a type in traits uses a type in response.
- The types involved
feroxbuster.traits.FeroxFilter→feroxbuster.response.FeroxResponse
- Direction
- traits uses response, so a change to response can break traits, while a change to traits can't break response.
- Position
- Below the diagonal: traits uses a module listed above it, which is the healthy direction.
26→6 config.container uses config.utils✕
- Connections
- 3 pairs of types, where a type in config.container uses a type in config.utils.
- The types involved
feroxbuster.config.container.Configuration→feroxbuster.config.utils.ContentTypeferoxbuster.config.container.Configuration→feroxbuster.config.utils.OutputLevelferoxbuster.config.container.Configuration→feroxbuster.config.utils.RequesterPolicy
- Direction
- config.container uses config.utils, so a change to config.utils can break config.container, while a change to config.container can't break config.utils.
- Position
- Below the diagonal: config.container uses a module listed above it, which is the healthy direction.
26→25 config.container uses traits✕
- Connections
- 1 pair of types, where a type in config.container uses a type in traits.
- The types involved
feroxbuster.config.container.Configuration→feroxbuster.traits.FeroxSerialize
- Direction
- config.container uses traits, so a change to traits can break config.container, while a change to config.container can't break traits.
- Position
- Below the diagonal: config.container uses a module listed above it, which is the healthy direction.
27→18 extractor.container uses event_handlers.container✕
- Connections
- 2 pairs of types, where a type in extractor.container uses a type in event_handlers.container.
- The types involved
feroxbuster.extractor.container.Extractor→feroxbuster.event_handlers.container.Handlesferoxbuster.extractor.container.container$module→feroxbuster.event_handlers.container.Handles
- Direction
- extractor.container uses event_handlers.container, so a change to event_handlers.container can break extractor.container, while a change to extractor.container can't break event_handlers.container.
- Position
- Below the diagonal: extractor.container uses a module listed above it, which is the healthy direction.
27→19 extractor.container uses response✕
- Connections
- 1 pair of types, where a type in extractor.container uses a type in response.
- The types involved
feroxbuster.extractor.container.Extractor→feroxbuster.response.FeroxResponse
- Direction
- extractor.container uses response, so a change to response can break extractor.container, while a change to extractor.container can't break response.
- Position
- Below the diagonal: extractor.container uses a module listed above it, which is the healthy direction.
27→21 extractor.container uses extractor.builder✕
- Connections
- 1 pair of types, where a type in extractor.container uses a type in extractor.builder.
- The types involved
feroxbuster.extractor.container.Extractor→feroxbuster.extractor.builder.ExtractionTarget
- Direction
- extractor.container uses extractor.builder, so a change to extractor.builder can break extractor.container, while a change to extractor.container can't break extractor.builder.
- Position
- Below the diagonal: extractor.container uses a module listed above it, which is the healthy direction.
28→19 filters.empty uses response✕
- Connections
- 1 pair of types, where a type in filters.empty uses a type in response.
- The types involved
feroxbuster.filters.empty.EmptyFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.empty uses response, so a change to response can break filters.empty, while a change to filters.empty can't break response.
- Position
- Below the diagonal: filters.empty uses a module listed above it, which is the healthy direction.
28→25 filters.empty uses traits✕
- Connections
- 1 pair of types, where a type in filters.empty uses a type in traits.
- The types involved
feroxbuster.filters.empty.EmptyFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.empty uses traits, so a change to traits can break filters.empty, while a change to filters.empty can't break traits.
- Position
- Below the diagonal: filters.empty uses a module listed above it, which is the healthy direction.
29→19 filters.lines uses response✕
- Connections
- 1 pair of types, where a type in filters.lines uses a type in response.
- The types involved
feroxbuster.filters.lines.LinesFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.lines uses response, so a change to response can break filters.lines, while a change to filters.lines can't break response.
- Position
- Below the diagonal: filters.lines uses a module listed above it, which is the healthy direction.
29→25 filters.lines uses traits✕
- Connections
- 1 pair of types, where a type in filters.lines uses a type in traits.
- The types involved
feroxbuster.filters.lines.LinesFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.lines uses traits, so a change to traits can break filters.lines, while a change to filters.lines can't break traits.
- Position
- Below the diagonal: filters.lines uses a module listed above it, which is the healthy direction.
30→19 filters.regex uses response✕
- Connections
- 1 pair of types, where a type in filters.regex uses a type in response.
- The types involved
feroxbuster.filters.regex.RegexFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.regex uses response, so a change to response can break filters.regex, while a change to filters.regex can't break response.
- Position
- Below the diagonal: filters.regex uses a module listed above it, which is the healthy direction.
30→25 filters.regex uses traits✕
- Connections
- 1 pair of types, where a type in filters.regex uses a type in traits.
- The types involved
feroxbuster.filters.regex.RegexFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.regex uses traits, so a change to traits can break filters.regex, while a change to filters.regex can't break traits.
- Position
- Below the diagonal: filters.regex uses a module listed above it, which is the healthy direction.
31→19 filters.similarity uses response✕
- Connections
- 1 pair of types, where a type in filters.similarity uses a type in response.
- The types involved
feroxbuster.filters.similarity.SimilarityFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.similarity uses response, so a change to response can break filters.similarity, while a change to filters.similarity can't break response.
- Position
- Below the diagonal: filters.similarity uses a module listed above it, which is the healthy direction.
31→25 filters.similarity uses traits✕
- Connections
- 1 pair of types, where a type in filters.similarity uses a type in traits.
- The types involved
feroxbuster.filters.similarity.SimilarityFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.similarity uses traits, so a change to traits can break filters.similarity, while a change to filters.similarity can't break traits.
- Position
- Below the diagonal: filters.similarity uses a module listed above it, which is the healthy direction.
32→19 filters.size uses response✕
- Connections
- 1 pair of types, where a type in filters.size uses a type in response.
- The types involved
feroxbuster.filters.size.SizeFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.size uses response, so a change to response can break filters.size, while a change to filters.size can't break response.
- Position
- Below the diagonal: filters.size uses a module listed above it, which is the healthy direction.
32→25 filters.size uses traits✕
- Connections
- 1 pair of types, where a type in filters.size uses a type in traits.
- The types involved
feroxbuster.filters.size.SizeFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.size uses traits, so a change to traits can break filters.size, while a change to filters.size can't break traits.
- Position
- Below the diagonal: filters.size uses a module listed above it, which is the healthy direction.
33→19 filters.status_code uses response✕
- Connections
- 1 pair of types, where a type in filters.status_code uses a type in response.
- The types involved
feroxbuster.filters.status_code.StatusCodeFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.status_code uses response, so a change to response can break filters.status_code, while a change to filters.status_code can't break response.
- Position
- Below the diagonal: filters.status_code uses a module listed above it, which is the healthy direction.
33→25 filters.status_code uses traits✕
- Connections
- 1 pair of types, where a type in filters.status_code uses a type in traits.
- The types involved
feroxbuster.filters.status_code.StatusCodeFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.status_code uses traits, so a change to traits can break filters.status_code, while a change to filters.status_code can't break traits.
- Position
- Below the diagonal: filters.status_code uses a module listed above it, which is the healthy direction.
34→19 filters.wildcard uses response✕
- Connections
- 1 pair of types, where a type in filters.wildcard uses a type in response.
- The types involved
feroxbuster.filters.wildcard.WildcardFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.wildcard uses response, so a change to response can break filters.wildcard, while a change to filters.wildcard can't break response.
- Position
- Below the diagonal: filters.wildcard uses a module listed above it, which is the healthy direction.
34→25 filters.wildcard uses traits✕
- Connections
- 1 pair of types, where a type in filters.wildcard uses a type in traits.
- The types involved
feroxbuster.filters.wildcard.WildcardFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.wildcard uses traits, so a change to traits can break filters.wildcard, while a change to filters.wildcard can't break traits.
- Position
- Below the diagonal: filters.wildcard uses a module listed above it, which is the healthy direction.
35→19 filters.words uses response✕
- Connections
- 1 pair of types, where a type in filters.words uses a type in response.
- The types involved
feroxbuster.filters.words.WordsFilter→feroxbuster.response.FeroxResponse
- Direction
- filters.words uses response, so a change to response can break filters.words, while a change to filters.words can't break response.
- Position
- Below the diagonal: filters.words uses a module listed above it, which is the healthy direction.
35→25 filters.words uses traits✕
- Connections
- 1 pair of types, where a type in filters.words uses a type in traits.
- The types involved
feroxbuster.filters.words.WordsFilter→feroxbuster.traits.FeroxFilter
- Direction
- filters.words uses traits, so a change to traits can break filters.words, while a change to filters.words can't break traits.
- Position
- Below the diagonal: filters.words uses a module listed above it, which is the healthy direction.
36→18 banner.container uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in banner.container uses a type in event_handlers.container.
- The types involved
feroxbuster.banner.container.Banner→feroxbuster.event_handlers.container.Handles
- Direction
- banner.container uses event_handlers.container, so a change to event_handlers.container can break banner.container, while a change to banner.container can't break event_handlers.container.
- Position
- Below the diagonal: banner.container uses a module listed above it, which is the healthy direction.
36→26 banner.container uses config.container✕
- Connections
- 1 pair of types, where a type in banner.container uses a type in config.container.
- The types involved
feroxbuster.banner.container.Banner→feroxbuster.config.container.Configuration
- Direction
- banner.container uses config.container, so a change to config.container can break banner.container, while a change to banner.container can't break config.container.
- Position
- Below the diagonal: banner.container uses a module listed above it, which is the healthy direction.
37→18 main uses event_handlers.container✕
- Connections
- 2 pairs of types, where a type in main uses a type in event_handlers.container.
- The types involved
feroxbuster.main.main$module→feroxbuster.event_handlers.container.Handlesferoxbuster.main.main$module→feroxbuster.event_handlers.container.Tasks
- Direction
- main uses event_handlers.container, so a change to event_handlers.container can break main, while a change to main can't break event_handlers.container.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
37→26 main uses config.container✕
- Connections
- 1 pair of types, where a type in main uses a type in config.container.
- The types involved
feroxbuster.main.main$module→feroxbuster.config.container.Configuration
- Direction
- main uses config.container, so a change to config.container can break main, while a change to main can't break config.container.
- Position
- Below the diagonal: main uses a module listed above it, which is the healthy direction.
38→8 scan_manager.state uses filters.container✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in filters.container.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.filters.container.FeroxFilters
- Direction
- scan_manager.state uses filters.container, so a change to filters.container can break scan_manager.state, while a change to scan_manager.state can't break filters.container.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
38→11 scan_manager.state uses statistics.container✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in statistics.container.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.statistics.container.Stats
- Direction
- scan_manager.state uses statistics.container, so a change to statistics.container can break scan_manager.state, while a change to scan_manager.state can't break statistics.container.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
38→16 scan_manager.state uses scan_manager.scan_container✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in scan_manager.scan_container.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.scan_manager.scan_container.FeroxScans
- Direction
- scan_manager.state uses scan_manager.scan_container, so a change to scan_manager.scan_container can break scan_manager.state, while a change to scan_manager.state can't break scan_manager.scan_container.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
38→23 scan_manager.state uses scan_manager.response_container✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in scan_manager.response_container.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.scan_manager.response_container.FeroxResponses
- Direction
- scan_manager.state uses scan_manager.response_container, so a change to scan_manager.response_container can break scan_manager.state, while a change to scan_manager.state can't break scan_manager.response_container.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
38→25 scan_manager.state uses traits✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in traits.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.traits.FeroxSerialize
- Direction
- scan_manager.state uses traits, so a change to traits can break scan_manager.state, while a change to scan_manager.state can't break traits.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
38→26 scan_manager.state uses config.container✕
- Connections
- 1 pair of types, where a type in scan_manager.state uses a type in config.container.
- The types involved
feroxbuster.scan_manager.state.FeroxState→feroxbuster.config.container.Configuration
- Direction
- scan_manager.state uses config.container, so a change to config.container can break scan_manager.state, while a change to scan_manager.state can't break config.container.
- Position
- Below the diagonal: scan_manager.state uses a module listed above it, which is the healthy direction.
39→6 scan_manager.utils uses config.utils✕
- Connections
- 1 pair of types, where a type in scan_manager.utils uses a type in config.utils.
- The types involved
feroxbuster.scan_manager.utils.utils$module→feroxbuster.config.utils.OutputLevel
- Direction
- scan_manager.utils uses config.utils, so a change to config.utils can break scan_manager.utils, while a change to scan_manager.utils can't break config.utils.
- Position
- Below the diagonal: scan_manager.utils uses a module listed above it, which is the healthy direction.
39→18 scan_manager.utils uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in scan_manager.utils uses a type in event_handlers.container.
- The types involved
feroxbuster.scan_manager.utils.utils$module→feroxbuster.event_handlers.container.Handles
- Direction
- scan_manager.utils uses event_handlers.container, so a change to event_handlers.container can break scan_manager.utils, while a change to scan_manager.utils can't break event_handlers.container.
- Position
- Below the diagonal: scan_manager.utils uses a module listed above it, which is the healthy direction.
39→26 scan_manager.utils uses config.container✕
- Connections
- 1 pair of types, where a type in scan_manager.utils uses a type in config.container.
- The types involved
feroxbuster.scan_manager.utils.utils$module→feroxbuster.config.container.Configuration
- Direction
- scan_manager.utils uses config.container, so a change to config.container can break scan_manager.utils, while a change to scan_manager.utils can't break config.container.
- Position
- Below the diagonal: scan_manager.utils uses a module listed above it, which is the healthy direction.
40→6 utils uses config.utils✕
- Connections
- 1 pair of types, where a type in utils uses a type in config.utils.
- The types involved
feroxbuster.utils.utils$module→feroxbuster.config.utils.OutputLevel
- Direction
- utils uses config.utils, so a change to config.utils can break utils, while a change to utils can't break config.utils.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
40→18 utils uses event_handlers.container✕
- Connections
- 1 pair of types, where a type in utils uses a type in event_handlers.container.
- The types involved
feroxbuster.utils.utils$module→feroxbuster.event_handlers.container.Handles
- Direction
- utils uses event_handlers.container, so a change to event_handlers.container can break utils, while a change to utils can't break event_handlers.container.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
40→19 utils uses response✕
- Connections
- 1 pair of types, where a type in utils uses a type in response.
- The types involved
feroxbuster.utils.utils$module→feroxbuster.response.FeroxResponse
- Direction
- utils uses response, so a change to response can break utils, while a change to utils can't break response.
- Position
- Below the diagonal: utils uses a module listed above it, which is the healthy direction.
40→26 utils uses config.container✕
- Connections
- 1 pair of types, where a type in utils uses a type in config.container.
- The types involved
feroxbuster.utils.utils$module→feroxbuster.config.container.Configuration
- Direction
- utils uses config.container, so a change to config.container can break utils, while a change to utils can't break config.container.
- Position
- Below the diagonal: utils 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 61 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 29 | High / Critical |
| A02:2025 — Security Misconfiguration | 3 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Begin by addressing the complete absence of Architecture Decision Records to properly document significant design choices and their consequences. Next, resolve the 29 orphaned files, prioritizing tests.rs, utils.rs, and container.rs, to improve codebase hygiene. Finally, restrict workflow token permissions in the CI/CD pipelines and update the README with clear instructions for running the test suite.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +7.2 pts | Low | ADR Quality |
| 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. | +6.4 pts | Medium | Architecture documentation |
| Resolve the 29 Orphaned file finding(s) in Knowledge Freshness — start with tests.rs (3), utils.rs (2), container.rs (2). | +5.2 pts | Medium | Knowledge Freshness |
| Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +2.3 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. | +1.3 pts | Low | Static Analysis (SAST) |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). | +1.3 pts | Low | Static Analysis (SAST) |
| Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite. | +2.6 pts | Medium | Documentation (README) |
| Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with utils.rs, container.rs, response.rs. | +1.0 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.5 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.1 | Mixed | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| src/config/container.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/scanner/ferox_scanner.rs | 6.0 | Mixed | Explicit Debt: TodoComment |
| src/event_handlers/outputs.rs | 6.7 | Mixed | Explicit Debt: TodoComment |
| src/banner/container.rs | 7.0 | Mixed | Cyclomatic Complexity: Banner::print_to (cyclomatic 47) |
| src/main.rs | 7.0 | Mixed | Cyclomatic Complexity: feroxbuster::wrapped_main (cyclomatic 38) |
| src/heuristics.rs | 7.0 | Mixed | Cyclomatic Complexity: HeuristicTests::detect_404_like_responses (cyclomatic 23) |
| src/statistics/container.rs | 7.1 | Mixed | Cyclomatic Complexity: Stats::deserialize (cyclomatic 107) |
| src/response.rs | 7.2 | Mixed | Cyclomatic Complexity: FeroxResponse::deserialize (cyclomatic 30) |
| src/scan_manager/scan.rs | 7.2 | Mixed | Cyclomatic Complexity: FeroxScan::deserialize (cyclomatic 22) |
| src/scan_manager/scan_container.rs | 7.2 | Mixed | Cyclomatic Complexity: FeroxScans::add_serialized_scans (cyclomatic 20) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
Watchdog 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. 47 of 47 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
What we checked — 47 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, 224 of 253 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, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — 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 |
| Watchdog 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 |
| LLM (sampled · advisory) | Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement | — | ◐ LLM · sampled · advisory |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`cargo llvm-cov`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.rs), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
- D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — Watchdog 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's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D24 Comment Value — not measured this run — Watchdog 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.
- D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
- D44 Platform End-of-Life — not measured this run — Watchdog 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
- AX6 Interface segregation — not measured this run — Watchdog 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing 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.
- AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM alpine:3.17.1 AS build 2 | LABEL maintainer="wfnintr@null.net" 3 | -------------------- ERROR: failed to solve: alpine:3.17.1: failed to resolve source metadata for docker.io/library/alpine:3.17.1: failed to do request: Head "https://registry-1.docker.io/v2/library/alpine/manifests/3.17.1": Forbidden; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby or Scala was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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). 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.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — Watchdog 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- X13 Undrained process stream — not measured this run — Watchdog 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- X16 Unfloored truncation loop — not measured this run — Watchdog 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, Java, PHP, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala 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.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — Watchdog 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 and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala 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.
- X18 Disposal-pattern correctness — not measured this run — Watchdog 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, Java, Kotlin, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala or PHP 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.
- X19 Unrestored process-global state — not measured this run — Watchdog 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, Java, Kotlin, Python, Dart, Ruby, Scala and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, Dart, Ruby, Scala or PHP 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.
- X22 Contradicted release guard — not measured this run — Watchdog 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 Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X23 Unguarded diagnostic materialisation — not measured this run — Watchdog 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, Java, F#, Python, Dart, Ruby, Scala, Kotlin and PHP source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin or PHP 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.
- X24 Document value interpolated into markup unescaped — not measured this run — Watchdog 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, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python 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.
- X25 Inert configuration knob — not measured this run — Watchdog 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, Java, Kotlin, Scala, PHP, Erlang, Python, Dart and Ruby source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart or Ruby 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.
- X3 Exception handling — not measured this run — Watchdog 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 PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript 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.
- X5 Nullable reference types — not measured this run — Watchdog 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, and Kotlin source only, and no C# was loaded, no TypeScript was found, and this repository's Rust is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D11 Test Reliability: Flakiness is inferred from history/markers — Watchdog runs 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
17 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was Stats::deserialize at 107.
What to do
- Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with Stats::deserialize (cyclomatic 107), Configuration::parse_cli_args (cyclomatic 93). — 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 2 together lifts Cyclomatic Complexity from 5.2 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
33 function(s) exceeded the cognitive complexity threshold of 15; the worst was Stats::deserialize at 267.
What to do
- Bring the 12 bodies over 30 down to 30 or less in Cognitive Complexity — start with Stats::deserialize (cognitive 267), Configuration::parse_cli_args (cognitive 144), Requester::request (cognitive 130). — 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 12 together lifts Cognitive Complexity from 2.0 to about 5.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
17 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 6 MethodTooLong finding(s) in God Classes — start with container.rs (4), ferox_scanner.rs, requester.rs. — One of this dimension's main actionable groups (6 warning-level).
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with parser.rs, main.rs, utils.rs. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 3 TooManyFields finding(s) in God Classes — start with container.rs (3). — One of this dimension's main actionable groups (3 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D4 · Code Duplication
7 duplicated block group(s) detected.
What to do
- Resolve the 2 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with container.rs, heuristics.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Duplicated block (14–16 lines × 2) finding(s) in Code Duplication — start with scan.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with filters.rs. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 37 classes have LCOM4 above 3.
D9 · Test Distribution
564 test methods: 400 unit, 164 integration, 0 BDD, 0 e2e. The Rust suite contributes 564 `#[test]` function(s) across 49 file(s) declaring at least one; its unit/integration split is Cargo's own — 16 of those file(s) are integration-test targets under a crate's tests/ directory, and the rest are #[test] functions compiled into the crate they test.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Rust (repository root, 49 test files): measured (0 flaky).
D12 · Dependency Hygiene
17 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 419 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's REDACTED closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
Top hotspots: src/main.rs (3×38=114)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
No source file's living knowledge is concentrated in a single author. Counted over 48 of the 76 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
8 deducted task-comment markers across 21691 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 8 TodoComment finding(s) in Explicit Debt — start with test_banner.rs (2), ferox_scanner.rs (2), test_heuristics.rs. — One of this dimension's main actionable groups (8 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (Cargo) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
61 finding(s): 0 critical, 61 high, 0 medium, 0 low. 50 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- No action in Static Analysis (SAST) — all 50 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 (50 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
20 finding(s): 0 critical, 2 high, 18 medium, 0 low.
What to do
- Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 7 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D31 · IaC & Container Security
3 finding(s): 0 critical, 1 high, 2 medium, 0 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
32 of 48 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/utils.rs. Counted over 48 of the 76 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 29 Orphaned file finding(s) in Knowledge Freshness — start with tests.rs (3), utils.rs (2), container.rs (2). — One of this dimension's main actionable groups (29 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with utils.rs, container.rs, response.rs. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
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 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
- 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).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
What to do
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X1 · Async correctness
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X21 · Side-effecting pattern guard
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X30 · Support guard that admits what it rejects
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 84% | Adequate — gated by D2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 84% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 55% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 68% | Adequate | Acceptable, with room to improve. |
| Security | 59% | Adequate — gated by D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 4 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X9 Subsumed condition operand — 17 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 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.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
- AX2 Stateful singletons — Not applicable: Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- 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:1 -------------------- 1 | >>> FROM alpine:3.17.1 AS build 2 | LABEL maintainer="wfnintr@null.net" 3 | -------------------- ERROR: failed to solve: alpine:3.17.1: failed to resolve source metadata for docker.io/library/alpine:3.17.1: failed to do request: Head "https://registry-1.docker.io/v2/library/alpine/manifests/3.17.1": Forbidden; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository starts no server another machine can reach (no actix-web HttpServer, axum::serve, Rocket launch, warp::serve, poem or salvo Server, tonic Server::builder, hyper or tiny_http server outside examples and tests, none bound beyond loopback). Access control is therefore N/A here — a crate is authorized by the application that serves it, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Diesel schema, a SeaORM entity, a Diesel or sqlx row struct, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store crate (sqlx, Diesel, SeaORM, rusqlite, tokio-postgres, MongoDB, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~6411 lines of test source are present (.rs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# only; Rust not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- 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+ projects each declaring an entity of their own. 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# and Visual Basic comments only — this repository's production source is .rs, 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
- D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.rs), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Rust source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `cargo install cargo-llvm-cov`, then `cargo llvm-cov --lcov --output-path lcov.info`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[bench]`, criterion's `bench_function`/`bench_with_input`, `#[divan::bench]` or `#[library_benchmark]` in any `.rs` file, or criterion, divan, iai or a `[[bench]]` target in a Cargo.toml, 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 applicable: Rust spells out every heap allocation and makes borrowed slices (&[T], &str) its ordinary parameter types, so the allocation-aware style this card rewards elsewhere is the language's baseline rather than a rung to climb.
- S1 Web-Security Posture — No web surface: 71 Rust file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server crate (actix-web, axum, Rocket, warp, poem, tide, salvo, tonic, a hyper server, …) among its Cargo manifests' run-time dependencies, and no server started in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
- X12 Unreachable branch — 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
- X13 Undrained process stream — 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
- X16 Unfloored truncation loop — 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
- X17 Uncapped recursion over a caller-supplied document — 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
- X18 Disposal-pattern 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
- X19 Unrestored process-global state — 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
- X2 Cancellation propagation — no C# was loaded; this repository's Rust was read, and no request in it can be cancelled by a caller — a Rust request takes no token: a future is cancelled by dropping it, from outside the call (select!, a timeout, an aborted task), and reqwest, hyper and tonic take none
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — 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
- X23 Unguarded diagnostic materialisation — 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
- X24 Document value interpolated into markup unescaped — 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
- X25 Inert configuration knob — 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
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Rust's compiler refuses the unsynchronised version: a collection shared between a callback's thread and the waiting body must be `Sync`, which a `Vec`, `VecDeque` or `HashMap` is only behind a `Mutex`/`RwLock`, so the race this check looks for cannot be written in safe Rust. Not a gap in the analyzer and not a finding about your code.
- X3 Exception handling — 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
- 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.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
- X5 Nullable reference types — 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
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 65 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 110 finding(s)
- TodoComment tests/test_banner.rs:1518
- TodoComment tests/test_banner.rs:1550
- TodoComment tests/test_heuristics.rs:483
- TodoComment src/scanner/ferox_scanner.rs:37
- TodoComment src/scanner/ferox_scanner.rs:50
- TodoComment src/event_handlers/inputs.rs:148
- TodoComment src/event_handlers/outputs.rs:111
- TodoComment src/config/container.rs:1037
- feroxbuster::wrapped_main (cognitive 70) src/main.rs:226
- feroxbuster::config::utils::parse_request_file (cognitive 63) src/config/utils.rs:431
- feroxbuster::get_targets (cognitive 30) src/main.rs:150
- feroxbuster::main (cognitive 24) src/main.rs:704
- feroxbuster::utils::make_request (cognitive 20) src/utils.rs:222
- feroxbuster::utils::should_deny_absolute (cognitive 19) src/utils.rs:448
- feroxbuster::scanner::ferox_scanner::check_for_user_input (cognitive 18) src/scanner/ferox_scanner.rs:42
- feroxbuster::scan (cognitive 16) src/main.rs:100
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- MethodTooLong: Configuration.parse_cli_args src/config/container.rs:675
- MethodTooLong: Banner.new src/banner/container.rs:202
- MethodTooLong: Stats.deserialize src/statistics/container.rs:215
- MethodTooLong: FeroxScanner.scan_url src/scanner/ferox_scanner.rs:217
- MethodTooLong: Requester.request src/scanner/requester.rs:447
- MethodTooLong: Banner.print_to src/banner/container.rs:641
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- HeuristicTests::detect_404_like_responses (cognitive 75) src/heuristics.rs:494
- HeuristicTests::has_directory_table_headers (cognitive 21) src/heuristics.rs:351
- HeuristicTests::has_high_link_density (cognitive 18) src/heuristics.rs:449
- HeuristicTests::examine_404_like_responses (cognitive 16) src/heuristics.rs:713
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- feroxbuster::wrapped_main (cyclomatic 38) src/main.rs:226
- feroxbuster::config::utils::parse_request_file (cyclomatic 35) src/config/utils.rs:431
- feroxbuster::get_targets (cyclomatic 16) src/main.rs:150
- FeroxResponse::deserialize (cognitive 56) src/response.rs:648
- FeroxResponse::is_directory (cognitive 19) src/response.rs:395
- FeroxResponse::as_str (cognitive 18) src/response.rs:462
- FeroxScans::add_serialized_scans (cognitive 42) src/scan_manager/scan_container.rs:136
- FeroxScans::make_visible (cognitive 18) src/scan_manager/scan_container.rs:742
- FeroxScans::cancel_scans (cognitive 16) src/scan_manager/scan_container.rs:361
- FunctionTooLong: feroxbuster::parser::initialize src/parser.rs:29
- FunctionTooLong: feroxbuster::wrapped_main src/main.rs:226
- FunctionTooLong: feroxbuster::config::utils::parse_request_file src/config/utils.rs:431
- TooManyFields: Configuration src/config/container.rs:91
- TooManyFields: Banner src/banner/container.rs:32
- TooManyFields: Stats src/statistics/container.rs:26
- ClassTooLong: Configuration src/config/container.rs:91
- ClassTooLong: Banner src/banner/container.rs:32
- ClassTooLong: Stats src/statistics/container.rs:26
- REDACTED
- REDACTED
- REDACTED
- Banner::print_to (cyclomatic 47) src/banner/container.rs:641
- Banner::new (cyclomatic 23) src/banner/container.rs:202
- HeuristicTests::detect_404_like_responses (cyclomatic 23) src/heuristics.rs:494
- HeuristicTests::examine_404_like_responses (cyclomatic 17) src/heuristics.rs:713
- Banner::print_to (cognitive 48) src/banner/container.rs:641
- Banner::new (cognitive 32) src/banner/container.rs:202
- FeroxScan::deserialize (cognitive 32) src/scan_manager/scan.rs:515
- FeroxScan::progress_bar (cognitive 20) src/scan_manager/scan.rs:248
- ScanHandler::try_recursion (cognitive 28) src/event_handlers/scans.rs:409
- ScanHandler::ordered_scan_url (cognitive 19) src/event_handlers/scans.rs:330
- FileTooLong: config/container.rs src/config/container.rs
- FileTooLong: src/parser.rs src/parser.rs
- REDACTED
- REDACTED
- Duplicated block (7 lines × 2) src/config/container.rs:715
- Duplicated block (7 lines × 2) src/heuristics.rs:316
- Stats::deserialize (cyclomatic 107) src/statistics/container.rs:215
- Configuration::parse_cli_args (cyclomatic 93) src/config/container.rs:675
- Requester::request (cyclomatic 43) src/scanner/requester.rs:447
- FeroxResponse::deserialize (cyclomatic 30) src/response.rs:648
- WildcardFilter::should_filter_response (cyclomatic 22) src/filters/wildcard.rs:58
- FeroxScan::deserialize (cyclomatic 22) src/scan_manager/scan.rs:515
- FeroxScans::add_serialized_scans (cyclomatic 20) src/scan_manager/scan_container.rs:136
- FeroxScanner::scan_url (cyclomatic 19) src/scanner/ferox_scanner.rs:217
- StatsHandler::start (cyclomatic 17) src/event_handlers/statistics.rs:79
- Extractor::request_links (cyclomatic 17) src/extractor/container.rs:164
- Hotspot: src/main.rs src/main.rs:226
- Stats::deserialize (cognitive 267) src/statistics/container.rs:215
- Configuration::parse_cli_args (cognitive 144) src/config/container.rs:675
- Requester::request (cognitive 130) src/scanner/requester.rs:447
- Extractor::request_links (cognitive 32) src/extractor/container.rs:164
- TermOutHandler::process_response (cognitive 28) src/event_handlers/outputs.rs:246
- FeroxScanner::scan_url (cognitive 28) src/scanner/ferox_scanner.rs:217
- WildcardFilter::should_filter_response (cognitive 22) src/filters/wildcard.rs:58
- PolicyData::adjust_up (cognitive 19) src/scanner/policy_data.rs:127
- Menu::split_to_nums (cognitive 16) src/scan_manager/menu.rs:226
- REDACTED
- Duplicated block (14–16 lines × 2) src/scan_manager/scan.rs:254
- Duplicated block (6 lines × 2) src/event_handlers/filters.rs:35
- Duplicated block (9 lines × 3) src/filters/lines.rs:14
- Duplicated block (17 lines × 2) src/scanner/limit_heap.rs:54
- Duplicated block (12 lines × 2) src/config/container.rs:1104
- Coverage collected but not gated
Minor — 61 finding(s)
- Orphaned file src/scan_manager/scan_container.rs:1
- Orphaned file src/scan_manager/scan.rs:1
- Orphaned file src/event_handlers/scans.rs:1
- Orphaned file src/scanner/ferox_scanner.rs:1
- Orphaned file src/extractor/tests.rs:1
- Orphaned file src/scanner/policy_data.rs:1
- Orphaned file src/scan_manager/menu.rs:1
- Orphaned file src/filters/tests.rs:1
- Orphaned file src/nlp/document.rs:1
- Orphaned file src/scanner/limit_heap.rs:1
- Orphaned file src/filters/wildcard.rs:1
- Orphaned file src/nlp/model.rs:1
- Orphaned file src/event_handlers/inputs.rs:1
- Orphaned file src/filters/utils.rs:1
- Orphaned file src/event_handlers/statistics.rs:1
- Orphaned file src/banner/tests.rs:1
- Orphaned file src/event_handlers/container.rs:1
- Orphaned file src/nlp/utils.rs:1
- Orphaned file src/filters/container.rs:1
- Orphaned file src/extractor/builder.rs:1
- Orphaned file src/message.rs:1
- Orphaned file src/traits.rs:1
- Orphaned file src/event_handlers/filters.rs:1
- Orphaned file src/progress.rs:1
- Orphaned file src/event_handlers/command.rs:1
- Subsumed condition operand src/heuristics.rs:334
- Subsumed condition operand src/heuristics.rs:391
- Subsumed condition operand src/heuristics.rs:395
- Subsumed condition operand src/utils.rs:43
- Subsumed condition operand src/utils.rs:44
- Subsumed condition operand src/utils.rs:53
- Subsumed condition operand src/utils.rs:54
- Subsumed condition operand src/utils.rs:55
- Subsumed condition operand src/utils.rs:57
- Subsumed condition operand src/utils.rs:58
- Subsumed condition operand src/utils.rs:71
- Subsumed condition operand src/utils.rs:72
- Subsumed condition operand src/utils.rs:73
- Subsumed condition operand src/utils.rs:75
- Subsumed condition operand src/utils.rs:76
- Subsumed condition operand src/utils.rs:77
- Subsumed condition operand src/utils.rs:79
- Most significant orphaned file src/utils.rs:1
- Most significant orphaned file src/statistics/container.rs:1
- Most significant orphaned file src/response.rs:1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Concentrated knowledge decay
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- Duplicated predicate src/event_handlers/scans.rs:332
- Silent fallback default on Err src/scan_manager/scan_container.rs:724
Minor — 17 finding(s)
- Outdated: anyhow
- Outdated: clap
- Outdated: clap_complete
- Outdated: ctrlc
- Outdated: env_logger
- Outdated: futures
- Outdated: gaoya
- Outdated: lazy_static
- Outdated: openssl
- Outdated: regex
- Outdated: self_update
- Outdated: serde_json
- Outdated: serde_regex
- Outdated: tokio
- Outdated: tokio-util
- Outdated: url
- Outdated: uuid
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9316f424f70544879b8142381db8c88b/history.json --exit-code 0 --source . | 1 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-9316f424f70544879b8142381db8c88b/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/watchdog-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 . | 61 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 20 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 3 | 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | artifacts/raw/osv-scanner.json |