Executive summary
toshi-search/Toshi falls short of our standard for production because we found no access checks on the code's endpoints or handlers and nine of the dependencies have a known vulnerability. It scores 52 out of 100 and is rated Adequate, and all 15 of its critical findings are security problems.
Security and Compliance, at 34, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 10 points. Adding access checks would lift Security and Compliance itself, worth about 11 points. Raising Security and Compliance to 70 would lift the score to about 63.
Ten pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, updating the vulnerable packages and setting a waiting period for automatic updates would close these risks.
The product code is 3,956 lines, about €3,900 to rebuild.
If Security and Compliance rose from 34 to 70, the lowest score rated Strong, the score would rise from 52 to about 63.
New since the last survey: 4 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Supply-chain Provenance & Signing · REDACTED
Fixed since the last survey: 2 findings
- Dependency Vulnerabilities · Medium CVE: RUSTSEC-2024-0336 REDACTED
- Supply-chain Provenance & Signing REDACTED
Rebuild cost: about €3,900 · Estimate
| Cost to rebuild | €1,300 to €6,500, for 22 to 68 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 3,956 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 toshi.error | 2 toshi_raft.proposal | 3 toshi_raft.raft_io | 4 toshi_raft.rpc_server | 5 toshi_raft.rpc_utils | 6 toshi_server.commit | 7 toshi_server.handlers.bulk | 8 toshi_server.handlers.index | 9 toshi_server.handlers.list | 10 toshi_server.handlers.root | 11 toshi_server.handlers.search | 12 toshi_server.settings | 13 toshi_server.shutdown | 14 toshi_types.error | 15 toshi_types.server | 16 toshi_raft | 17 toshi_server | 18 toshi_server.bin.toshi | 19 toshi_server.router | 20 toshi_server.utils | 21 toshi_types.query.boolean | 22 toshi_types.query.facet | 23 toshi_types.query.fuzzy | 24 toshi_types.query.phrase | 25 toshi_types.query.range | 26 toshi_types.query.regex | 27 toshi_types.query.term | 28 toshi_types.query | 29 toshi | 30 toshi_server.handlers.summary | 31 toshi_types | 32 toshi_types.client | 33 toshi.hyper_client | 34 toshi.isahc_client | 35 toshi_raft.handle | 36 toshi_server.handle | 37 toshi_server.index |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 toshi.error | |||||||||||||||||||||||||||||||||||||
| 2 toshi_raft.proposal | |||||||||||||||||||||||||||||||||||||
| 3 toshi_raft.raft_io | |||||||||||||||||||||||||||||||||||||
| 4 toshi_raft.rpc_server | |||||||||||||||||||||||||||||||||||||
| 5 toshi_raft.rpc_utils | |||||||||||||||||||||||||||||||||||||
| 6 toshi_server.commit | |||||||||||||||||||||||||||||||||||||
| 7 toshi_server.handlers.bulk | |||||||||||||||||||||||||||||||||||||
| 8 toshi_server.handlers.index | |||||||||||||||||||||||||||||||||||||
| 9 toshi_server.handlers.list | |||||||||||||||||||||||||||||||||||||
| 10 toshi_server.handlers.root | |||||||||||||||||||||||||||||||||||||
| 11 toshi_server.handlers.search | |||||||||||||||||||||||||||||||||||||
| 12 toshi_server.settings | |||||||||||||||||||||||||||||||||||||
| 13 toshi_server.shutdown | |||||||||||||||||||||||||||||||||||||
| 14 toshi_types.error | |||||||||||||||||||||||||||||||||||||
| 15 toshi_types.server | |||||||||||||||||||||||||||||||||||||
| 16 toshi_raft | 1 | ||||||||||||||||||||||||||||||||||||
| 17 toshi_server | 1 | ||||||||||||||||||||||||||||||||||||
| 18 toshi_server.bin.toshi | 1 | ||||||||||||||||||||||||||||||||||||
| 19 toshi_server.router | 1 | ||||||||||||||||||||||||||||||||||||
| 20 toshi_server.utils | 1 | ||||||||||||||||||||||||||||||||||||
| 21 toshi_types.query.boolean | 4 | ||||||||||||||||||||||||||||||||||||
| 22 toshi_types.query.facet | 1 | ||||||||||||||||||||||||||||||||||||
| 23 toshi_types.query.fuzzy | 3 | ||||||||||||||||||||||||||||||||||||
| 24 toshi_types.query.phrase | 2 | ||||||||||||||||||||||||||||||||||||
| 25 toshi_types.query.range | 3 | ||||||||||||||||||||||||||||||||||||
| 26 toshi_types.query.regex | 2 | ||||||||||||||||||||||||||||||||||||
| 27 toshi_types.query.term | 2 | ||||||||||||||||||||||||||||||||||||
| 28 toshi_types.query | 1 | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 29 toshi | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 30 toshi_server.handlers.summary | 1 | ||||||||||||||||||||||||||||||||||||
| 31 toshi_types | 2 | 2 | |||||||||||||||||||||||||||||||||||
| 32 toshi_types.client | 1 | ||||||||||||||||||||||||||||||||||||
| 33 toshi.hyper_client | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 34 toshi.isahc_client | 1 | 1 | 2 | ||||||||||||||||||||||||||||||||||
| 35 toshi_raft.handle | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 36 toshi_server.handle | 2 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 toshi_server.index | 1 | 1 |
16→2 toshi_raft uses toshi_raft.proposal✕
- Connections
- 1 pair of types, where a type in toshi_raft uses a type in toshi_raft.proposal.
- The types involved
toshi_raft.toshi_raft$module→toshi_raft.proposal.Proposal
- Direction
- toshi_raft uses toshi_raft.proposal, so a change to toshi_raft.proposal can break toshi_raft, while a change to toshi_raft can't break toshi_raft.proposal.
- Position
- Below the diagonal: toshi_raft uses a module listed above it, which is the healthy direction.
17→12 toshi_server uses toshi_server.settings✕
- Connections
- 1 pair of types, where a type in toshi_server uses a type in toshi_server.settings.
- The types involved
toshi_server.toshi_server$module→toshi_server.settings.Settings
- Direction
- toshi_server uses toshi_server.settings, so a change to toshi_server.settings can break toshi_server, while a change to toshi_server can't break toshi_server.settings.
- Position
- Below the diagonal: toshi_server uses a module listed above it, which is the healthy direction.
18→12 toshi_server.bin.toshi uses toshi_server.settings✕
- Connections
- 1 pair of types, where a type in toshi_server.bin.toshi uses a type in toshi_server.settings.
- The types involved
toshi_server.bin.toshi.toshi$module→toshi_server.settings.Settings
- Direction
- toshi_server.bin.toshi uses toshi_server.settings, so a change to toshi_server.settings can break toshi_server.bin.toshi, while a change to toshi_server.bin.toshi can't break toshi_server.settings.
- Position
- Below the diagonal: toshi_server.bin.toshi uses a module listed above it, which is the healthy direction.
19→12 toshi_server.router uses toshi_server.settings✕
- Connections
- 1 pair of types, where a type in toshi_server.router uses a type in toshi_server.settings.
- The types involved
toshi_server.router.Router→toshi_server.settings.Settings
- Direction
- toshi_server.router uses toshi_server.settings, so a change to toshi_server.settings can break toshi_server.router, while a change to toshi_server.router can't break toshi_server.settings.
- Position
- Below the diagonal: toshi_server.router uses a module listed above it, which is the healthy direction.
20→14 toshi_server.utils uses toshi_types.error✕
- Connections
- 1 pair of types, where a type in toshi_server.utils uses a type in toshi_types.error.
- The types involved
toshi_server.utils.utils$module→toshi_types.error.Error
- Direction
- toshi_server.utils uses toshi_types.error, so a change to toshi_types.error can break toshi_server.utils, while a change to toshi_server.utils can't break toshi_types.error.
- Position
- Below the diagonal: toshi_server.utils uses a module listed above it, which is the healthy direction.
21→28 toshi_types.query.boolean uses toshi_types.query part of a loop✕
- Connections
- 4 pairs of types, where a type in toshi_types.query.boolean uses a type in toshi_types.query.
- The types involved
toshi_types.query.boolean.BoolQuery→toshi_types.query.CreateQuerytoshi_types.query.boolean.BoolQuery→toshi_types.query.Querytoshi_types.query.boolean.BoolQueryBuilder→toshi_types.query.Querytoshi_types.query.boolean.boolean$module→toshi_types.query.Query
- Direction
- toshi_types.query.boolean uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.boolean, while a change to toshi_types.query.boolean can't break toshi_types.query.
- 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.
22→28 toshi_types.query.facet uses toshi_types.query part of a loop✕
- Connections
- 1 pair of types, where a type in toshi_types.query.facet uses a type in toshi_types.query.
- The types involved
toshi_types.query.facet.FacetQuery→toshi_types.query.KeyValue
- Direction
- toshi_types.query.facet uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.facet, while a change to toshi_types.query.facet can't break toshi_types.query.
- 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.
23→28 toshi_types.query.fuzzy uses toshi_types.query part of a loop✕
- Connections
- 3 pairs of types, where a type in toshi_types.query.fuzzy uses a type in toshi_types.query.
- The types involved
toshi_types.query.fuzzy.FuzzyQuery→toshi_types.query.CreateQuerytoshi_types.query.fuzzy.FuzzyQuery→toshi_types.query.KeyValuetoshi_types.query.fuzzy.FuzzyQueryBuilder→toshi_types.query.Query
- Direction
- toshi_types.query.fuzzy uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.fuzzy, while a change to toshi_types.query.fuzzy can't break toshi_types.query.
- 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.
24→28 toshi_types.query.phrase uses toshi_types.query part of a loop✕
- Connections
- 2 pairs of types, where a type in toshi_types.query.phrase uses a type in toshi_types.query.
- The types involved
toshi_types.query.phrase.PhraseQuery→toshi_types.query.CreateQuerytoshi_types.query.phrase.PhraseQuery→toshi_types.query.KeyValue
- Direction
- toshi_types.query.phrase uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.phrase, while a change to toshi_types.query.phrase can't break toshi_types.query.
- 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.
25→28 toshi_types.query.range uses toshi_types.query part of a loop✕
- Connections
- 3 pairs of types, where a type in toshi_types.query.range uses a type in toshi_types.query.
- The types involved
toshi_types.query.range.RangeQuery→toshi_types.query.CreateQuerytoshi_types.query.range.RangeQuery→toshi_types.query.KeyValuetoshi_types.query.range.RangeQueryBuilder→toshi_types.query.Query
- Direction
- toshi_types.query.range uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.range, while a change to toshi_types.query.range can't break toshi_types.query.
- 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.
26→28 toshi_types.query.regex uses toshi_types.query part of a loop✕
- Connections
- 2 pairs of types, where a type in toshi_types.query.regex uses a type in toshi_types.query.
- The types involved
toshi_types.query.regex.RegexQuery→toshi_types.query.CreateQuerytoshi_types.query.regex.RegexQuery→toshi_types.query.KeyValue
- Direction
- toshi_types.query.regex uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.regex, while a change to toshi_types.query.regex can't break toshi_types.query.
- 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.
27→28 toshi_types.query.term uses toshi_types.query part of a loop✕
- Connections
- 2 pairs of types, where a type in toshi_types.query.term uses a type in toshi_types.query.
- The types involved
toshi_types.query.term.ExactTerm→toshi_types.query.CreateQuerytoshi_types.query.term.ExactTerm→toshi_types.query.KeyValue
- Direction
- toshi_types.query.term uses toshi_types.query, so a change to toshi_types.query can break toshi_types.query.term, while a change to toshi_types.query.term can't break toshi_types.query.
- 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.
28→21 toshi_types.query uses toshi_types.query.boolean✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.boolean.
- The types involved
toshi_types.query.Query→toshi_types.query.boolean.BoolQuery
- Direction
- toshi_types.query uses toshi_types.query.boolean, so a change to toshi_types.query.boolean can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.boolean.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→22 toshi_types.query uses toshi_types.query.facet✕
- Connections
- 2 pairs of types, where a type in toshi_types.query uses a type in toshi_types.query.facet.
- The types involved
toshi_types.query.Search→toshi_types.query.facet.FacetQuerytoshi_types.query.SearchBuilder→toshi_types.query.facet.FacetQuery
- Direction
- toshi_types.query uses toshi_types.query.facet, so a change to toshi_types.query.facet can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.facet.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→23 toshi_types.query uses toshi_types.query.fuzzy✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.fuzzy.
- The types involved
toshi_types.query.Query→toshi_types.query.fuzzy.FuzzyQuery
- Direction
- toshi_types.query uses toshi_types.query.fuzzy, so a change to toshi_types.query.fuzzy can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.fuzzy.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→24 toshi_types.query uses toshi_types.query.phrase✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.phrase.
- The types involved
toshi_types.query.Query→toshi_types.query.phrase.PhraseQuery
- Direction
- toshi_types.query uses toshi_types.query.phrase, so a change to toshi_types.query.phrase can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.phrase.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→25 toshi_types.query uses toshi_types.query.range✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.range.
- The types involved
toshi_types.query.Query→toshi_types.query.range.RangeQuery
- Direction
- toshi_types.query uses toshi_types.query.range, so a change to toshi_types.query.range can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.range.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→26 toshi_types.query uses toshi_types.query.regex✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.regex.
- The types involved
toshi_types.query.Query→toshi_types.query.regex.RegexQuery
- Direction
- toshi_types.query uses toshi_types.query.regex, so a change to toshi_types.query.regex can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.regex.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
28→27 toshi_types.query uses toshi_types.query.term✕
- Connections
- 1 pair of types, where a type in toshi_types.query uses a type in toshi_types.query.term.
- The types involved
toshi_types.query.Query→toshi_types.query.term.ExactTerm
- Direction
- toshi_types.query uses toshi_types.query.term, so a change to toshi_types.query.term can break toshi_types.query, while a change to toshi_types.query can't break toshi_types.query.term.
- Position
- Below the diagonal: toshi_types.query uses a module listed above it, which is the healthy direction.
29→15 toshi uses toshi_types.server✕
- Connections
- 2 pairs of types, where a type in toshi uses a type in toshi_types.server.
- The types involved
toshi.AsyncClient→toshi_types.server.IndexOptionstoshi.SyncClient→toshi_types.server.IndexOptions
- Direction
- toshi uses toshi_types.server, so a change to toshi_types.server can break toshi, while a change to toshi can't break toshi_types.server.
- Position
- Below the diagonal: toshi uses a module listed above it, which is the healthy direction.
29→28 toshi uses toshi_types.query✕
- Connections
- 2 pairs of types, where a type in toshi uses a type in toshi_types.query.
- The types involved
toshi.AsyncClient→toshi_types.query.Searchtoshi.SyncClient→toshi_types.query.Search
- Direction
- toshi uses toshi_types.query, so a change to toshi_types.query can break toshi, while a change to toshi can't break toshi_types.query.
- Position
- Below the diagonal: toshi uses a module listed above it, which is the healthy direction.
30→28 toshi_server.handlers.summary uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi_server.handlers.summary uses a type in toshi_types.query.
- The types involved
toshi_server.handlers.summary.summary$module→toshi_types.query.QueryOptions
- Direction
- toshi_server.handlers.summary uses toshi_types.query, so a change to toshi_types.query can break toshi_server.handlers.summary, while a change to toshi_server.handlers.summary can't break toshi_types.query.
- Position
- Below the diagonal: toshi_server.handlers.summary uses a module listed above it, which is the healthy direction.
31→15 toshi_types uses toshi_types.server✕
- Connections
- 2 pairs of types, where a type in toshi_types uses a type in toshi_types.server.
- The types involved
toshi_types.IndexHandle→toshi_types.server.AddDocumenttoshi_types.IndexHandle→toshi_types.server.DeleteDoc
- Direction
- toshi_types uses toshi_types.server, so a change to toshi_types.server can break toshi_types, while a change to toshi_types can't break toshi_types.server.
- Position
- Below the diagonal: toshi_types uses a module listed above it, which is the healthy direction.
31→28 toshi_types uses toshi_types.query✕
- Connections
- 2 pairs of types, where a type in toshi_types uses a type in toshi_types.query.
- The types involved
toshi_types.IndexHandle→toshi_types.query.Searchtoshi_types.Serve→toshi_types.query.QueryOptions
- Direction
- toshi_types uses toshi_types.query, so a change to toshi_types.query can break toshi_types, while a change to toshi_types can't break toshi_types.query.
- Position
- Below the diagonal: toshi_types uses a module listed above it, which is the healthy direction.
32→28 toshi_types.client uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi_types.client uses a type in toshi_types.query.
- The types involved
toshi_types.client.SearchResults→toshi_types.query.KeyValue
- Direction
- toshi_types.client uses toshi_types.query, so a change to toshi_types.query can break toshi_types.client, while a change to toshi_types.client can't break toshi_types.query.
- Position
- Below the diagonal: toshi_types.client uses a module listed above it, which is the healthy direction.
33→15 toshi.hyper_client uses toshi_types.server✕
- Connections
- 1 pair of types, where a type in toshi.hyper_client uses a type in toshi_types.server.
- The types involved
toshi.hyper_client.HyperToshi→toshi_types.server.IndexOptions
- Direction
- toshi.hyper_client uses toshi_types.server, so a change to toshi_types.server can break toshi.hyper_client, while a change to toshi.hyper_client can't break toshi_types.server.
- Position
- Below the diagonal: toshi.hyper_client uses a module listed above it, which is the healthy direction.
33→28 toshi.hyper_client uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi.hyper_client uses a type in toshi_types.query.
- The types involved
toshi.hyper_client.HyperToshi→toshi_types.query.Search
- Direction
- toshi.hyper_client uses toshi_types.query, so a change to toshi_types.query can break toshi.hyper_client, while a change to toshi.hyper_client can't break toshi_types.query.
- Position
- Below the diagonal: toshi.hyper_client uses a module listed above it, which is the healthy direction.
33→29 toshi.hyper_client uses toshi✕
- Connections
- 1 pair of types, where a type in toshi.hyper_client uses a type in toshi.
- The types involved
toshi.hyper_client.HyperToshi→toshi.AsyncClient
- Direction
- toshi.hyper_client uses toshi, so a change to toshi can break toshi.hyper_client, while a change to toshi.hyper_client can't break toshi.
- Position
- Below the diagonal: toshi.hyper_client uses a module listed above it, which is the healthy direction.
34→15 toshi.isahc_client uses toshi_types.server✕
- Connections
- 1 pair of types, where a type in toshi.isahc_client uses a type in toshi_types.server.
- The types involved
toshi.isahc_client.ToshiClient→toshi_types.server.IndexOptions
- Direction
- toshi.isahc_client uses toshi_types.server, so a change to toshi_types.server can break toshi.isahc_client, while a change to toshi.isahc_client can't break toshi_types.server.
- Position
- Below the diagonal: toshi.isahc_client uses a module listed above it, which is the healthy direction.
34→28 toshi.isahc_client uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi.isahc_client uses a type in toshi_types.query.
- The types involved
toshi.isahc_client.ToshiClient→toshi_types.query.Search
- Direction
- toshi.isahc_client uses toshi_types.query, so a change to toshi_types.query can break toshi.isahc_client, while a change to toshi.isahc_client can't break toshi_types.query.
- Position
- Below the diagonal: toshi.isahc_client uses a module listed above it, which is the healthy direction.
34→29 toshi.isahc_client uses toshi✕
- Connections
- 2 pairs of types, where a type in toshi.isahc_client uses a type in toshi.
- The types involved
toshi.isahc_client.ToshiClient→toshi.AsyncClienttoshi.isahc_client.ToshiClient→toshi.SyncClient
- Direction
- toshi.isahc_client uses toshi, so a change to toshi can break toshi.isahc_client, while a change to toshi.isahc_client can't break toshi.
- Position
- Below the diagonal: toshi.isahc_client uses a module listed above it, which is the healthy direction.
35→15 toshi_raft.handle uses toshi_types.server✕
- Connections
- 2 pairs of types, where a type in toshi_raft.handle uses a type in toshi_types.server.
- The types involved
toshi_raft.handle.RaftHandle→toshi_types.server.AddDocumenttoshi_raft.handle.RaftHandle→toshi_types.server.DeleteDoc
- Direction
- toshi_raft.handle uses toshi_types.server, so a change to toshi_types.server can break toshi_raft.handle, while a change to toshi_raft.handle can't break toshi_types.server.
- Position
- Below the diagonal: toshi_raft.handle uses a module listed above it, which is the healthy direction.
35→28 toshi_raft.handle uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi_raft.handle uses a type in toshi_types.query.
- The types involved
toshi_raft.handle.RaftHandle→toshi_types.query.Search
- Direction
- toshi_raft.handle uses toshi_types.query, so a change to toshi_types.query can break toshi_raft.handle, while a change to toshi_raft.handle can't break toshi_types.query.
- Position
- Below the diagonal: toshi_raft.handle uses a module listed above it, which is the healthy direction.
35→31 toshi_raft.handle uses toshi_types✕
- Connections
- 1 pair of types, where a type in toshi_raft.handle uses a type in toshi_types.
- The types involved
toshi_raft.handle.RaftHandle→toshi_types.IndexHandle
- Direction
- toshi_raft.handle uses toshi_types, so a change to toshi_types can break toshi_raft.handle, while a change to toshi_raft.handle can't break toshi_types.
- Position
- Below the diagonal: toshi_raft.handle uses a module listed above it, which is the healthy direction.
36→15 toshi_server.handle uses toshi_types.server✕
- Connections
- 2 pairs of types, where a type in toshi_server.handle uses a type in toshi_types.server.
- The types involved
toshi_server.handle.LocalIndex→toshi_types.server.AddDocumenttoshi_server.handle.LocalIndex→toshi_types.server.DeleteDoc
- Direction
- toshi_server.handle uses toshi_types.server, so a change to toshi_types.server can break toshi_server.handle, while a change to toshi_server.handle can't break toshi_types.server.
- Position
- Below the diagonal: toshi_server.handle uses a module listed above it, which is the healthy direction.
36→28 toshi_server.handle uses toshi_types.query✕
- Connections
- 1 pair of types, where a type in toshi_server.handle uses a type in toshi_types.query.
- The types involved
toshi_server.handle.LocalIndex→toshi_types.query.Search
- Direction
- toshi_server.handle uses toshi_types.query, so a change to toshi_types.query can break toshi_server.handle, while a change to toshi_server.handle can't break toshi_types.query.
- Position
- Below the diagonal: toshi_server.handle uses a module listed above it, which is the healthy direction.
36→31 toshi_server.handle uses toshi_types✕
- Connections
- 1 pair of types, where a type in toshi_server.handle uses a type in toshi_types.
- The types involved
toshi_server.handle.LocalIndex→toshi_types.IndexHandle
- Direction
- toshi_server.handle uses toshi_types, so a change to toshi_types can break toshi_server.handle, while a change to toshi_server.handle can't break toshi_types.
- Position
- Below the diagonal: toshi_server.handle uses a module listed above it, which is the healthy direction.
37→12 toshi_server.index uses toshi_server.settings✕
- Connections
- 1 pair of types, where a type in toshi_server.index uses a type in toshi_server.settings.
- The types involved
toshi_server.index.IndexCatalog→toshi_server.settings.Settings
- Direction
- toshi_server.index uses toshi_server.settings, so a change to toshi_server.settings can break toshi_server.index, while a change to toshi_server.index can't break toshi_server.settings.
- Position
- Below the diagonal: toshi_server.index uses a module listed above it, which is the healthy direction.
37→31 toshi_server.index uses toshi_types✕
- Connections
- 1 pair of types, where a type in toshi_server.index uses a type in toshi_types.
- The types involved
toshi_server.index.IndexCatalog→toshi_types.Catalog
- Direction
- toshi_server.index uses toshi_types, so a change to toshi_types can break toshi_server.index, while a change to toshi_server.index can't break toshi_types.
- Position
- Below the diagonal: toshi_server.index 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 |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 38 | High / Critical |
| A05:2025 — Injection | 20 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
First, secure the application by implementing a global authentication guard with explicit public opt-outs and named role permissions to enforce default-deny access. Next, address the 23 orphaned files, prioritizing lib.rs, handle.rs, and index.rs, to improve codebase hygiene. Finally, establish a vulnerability disclosure policy with a reporting contact and document significant design decisions in a dedicated ADR folder to ensure architectural clarity and security compliance.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +10.4 pts | Low | ADR Quality |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +11.2 pts | Medium | Access Controls |
| Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. | +5.1 pts | Low | Vulnerability-disclosure Policy |
| Resolve the 23 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (3), handle.rs (2), index.rs (2). | +10.1 pts | Medium | Knowledge Freshness |
| 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. | +7.6 pts | Medium | Architecture documentation |
| Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). | +3.5 pts | Low | Static Analysis (SAST) |
| Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only. | +4.5 pts | Medium | Web-Security Posture |
| Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). | +1.9 pts | Low | Dependency Vulnerabilities |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.2 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 0.6 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| toshi-server/src/handle.rs | 7.4 | Mixed | Cyclomatic Complexity: LocalIndex::search_index (cyclomatic 17) |
| toshi-raft/src/lib.rs | 8.2 | Near-clean | Explicit Debt: TodoComment |
| toshi-server/src/handlers/index.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (6 lines × 2) |
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. 45 of 45 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.8 — 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 — 45 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, 88 of 112 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ 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 Codecov configuration (codecov.yml) and a coverage step in CI (`codecov/codecov-action`) 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.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 23 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 19 of the 39 production source files in this repository: 16 are under the ~2,400-byte size floor this dimension measures over, and the remaining 4 have no attributable history left to measure.
- 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 Dockerfile) 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.
- 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.
- 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.
- X4 Structured logging — 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, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's Rust calls level macros (`info!`, `warn!`, …) the reading cannot place in `tracing` or `log` — its crate depends on both, imports them through a `#[macro_use]` at the crate root, or logs through `slog` — so its log calls cannot be judged, 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.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
Dimensions
D1 · Cyclomatic Complexity
1 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was LocalIndex::search_index at 17.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with LocalIndex::search_index (cyclomatic 17). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
- 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
1 function(s) exceeded the cognitive complexity threshold of 15; the worst was LocalIndex::search_index at 20.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with LocalIndex::search_index (cognitive 20). — Refactoring it lifts Cognitive Complexity from 9.6 to about 10.0/10.
- 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
0 over-large unit(s) detected — types, modules or files that carry too much.
D4 · Code Duplication
2 duplicated block group(s) detected.
What to do
- Resolve the 1 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with handle.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 index.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.
D5 · Coupling
5 production modules (Cargo), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 23 classes have LCOM4 above 3.
D9 · Test Distribution
48 test methods: 47 unit, 1 integration, 0 BDD, 0 e2e. The Rust suite contributes 48 `#[test]` function(s) across 16 file(s) declaring at least one; its unit/integration split is Cargo's own — 1 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, 16 test files): measured (0 flaky).
D12 · Dependency Hygiene
14 outdated, 0 yanked direct Cargo dependencies. 30 of 38 direct crates were graded against crates.io (0 not published there, 8 not resolved by a committed REDACTED). 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.
What to do
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 356 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.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
1 deducted task-comment markers across 3956 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with lib.rs. — One of this dimension's main actionable groups (1 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. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
0 of 5 build units (Cargo) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
20 finding(s): 0 critical, 11 high, 9 medium, 0 low. 10 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.
What to do
- Resolve the 8 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 10 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 (10 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
38 finding(s): 0 critical, 4 high, 34 medium, 0 low.
What to do
- Resolve the 9 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
23 of 23 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is toshi-types/src/query/boolean.rs. Counted over 23 of the 39 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 23 Orphaned file finding(s) in Knowledge Freshness — start with lib.rs (3), handle.rs (2), index.rs (2). — One of this dimension's main actionable groups (23 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. — 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
C2 · Access Controls
- This repository serves requests — a server (Server::builder()) (toshi-raft/src/rpc_server.rs:35) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — toshi-raft/src/rpc_server.rs:35
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
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
P1 · CI/CD gates
P10 · Library API & versioning
- 47/52 types (90%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
- Keep implementation types off the public surface (Rust: `pub(crate)`, or keep the module private) so internals can change without breaking consumers.
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.
PF3 · Async & latency hygiene
S1 · Web-Security Posture
- This repository starts an HTTP server and nothing in its Rust source or committed `Rocket.toml` secures the transport: no TLS served (actix-web `bind_rustls`/`bind_openssl`, axum-server `bind_rustls` with a `RustlsConfig`, tonic `ServerTlsConfig`, a `TlsAcceptor`, Rocket's `[default.tls]`), no `Strict-Transport-Security` header, no `X-Forwarded-Proto` read from a TLS-terminating proxy — so its traffic may cross the network in clear text. (−2.0 on this card.) The server: `Server::builder()` (toshi-raft/src/rpc_server.rs:35).
- None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is set on a response this repository's Rust server sends — defense in depth, even when a proxy could set them. (−2.0 on this card.) The server: `Server::builder()` (toshi-raft/src/rpc_server.rs:35).
What to do
- Secure the server's transport: serve TLS itself (`HttpServer::bind_rustls_0_23(addr, config)` in actix-web, `axum_server::bind_rustls(addr, RustlsConfig::from_pem_file(…))`, tonic's `Server::builder().tls_config(ServerTlsConfig::new().identity(…))`, Rocket's `[default.tls]`), or run it behind a TLS-terminating proxy and check `X-Forwarded-Proto`; send `Strict-Transport-Security` once it is HTTPS-only.
- Set security response headers on what the server sends — actix-web's `DefaultHeaders::new().add((header::X_CONTENT_TYPE_OPTIONS, "nosniff"))`, tower-http's `SetResponseHeaderLayer::overriding(…)` on an axum router, or keep Rocket's default `Shield` — with `Content-Security-Policy`, `X-Content-Type-Options` and a frame policy on every response.
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 | 99% | Exemplary | Solid. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 44% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 74% | Strong | Solid. |
| Security | 34% | Weak — gated by D30, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 3 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 70 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
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- 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.
- 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 — ~123 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.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- 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.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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
- 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 none of the 3 signals this lens looks for
- 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
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — 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.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Rust source (service entry point: toshi-raft/src/rpc_server.rs:35 (Server::builder()))
- 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 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
- 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.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 52 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No authorization toshi-raft/src/rpc_server.rs:35
- LocalIndex::search_index (cyclomatic 17) toshi-server/src/handle.rs:77
- TodoComment toshi-raft/src/lib.rs:213
- LocalIndex::search_index (cognitive 20) toshi-server/src/handle.rs:77
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) toshi-server/src/handle.rs:230
- Duplicated block (6 lines × 2) toshi-server/src/handlers/index.rs:23
- Off the main sequence: toshi-types
Minor — 31 finding(s)
- Orphaned file toshi-types/src/query/boolean.rs:1
- Orphaned file toshi-types/src/query/mod.rs:1
- Orphaned file toshi-server/src/handle.rs:1
- Orphaned file toshi-server/src/settings.rs:1
- Orphaned file toshi-server/src/handlers/search.rs:1
- Orphaned file toshi-raft/src/lib.rs:1
- Orphaned file toshi-server/src/handlers/bulk.rs:1
- Orphaned file toshi-server/src/handlers/index.rs:1
- Orphaned file toshi-types/src/query/range.rs:1
- Orphaned file toshi-raft/src/rpc_server.rs:1
- Orphaned file toshi-client/src/isahc_client.rs:1
- Orphaned file toshi-types/src/lib.rs:1
- Orphaned file toshi-server/src/commit.rs:1
- Orphaned file toshi-server/src/index.rs:1
- Orphaned file toshi-client/src/hyper_client.rs:1
- Orphaned file toshi-types/src/query/phrase.rs:1
- Orphaned file toshi-server/src/router.rs:1
- Orphaned file toshi-types/src/client.rs:1
- Orphaned file toshi-raft/src/handle.rs:1
- Orphaned file toshi-types/src/error.rs:1
- Orphaned file toshi-types/src/server.rs:1
- Orphaned file toshi-client/src/lib.rs:1
- Orphaned file toshi-types/src/query/fuzzy.rs:1
- No ADRs found
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- Large public API surface
- No app-layer HTTPS enforcement detected
- No security response headers detected
Minor — 14 finding(s)
- Outdated: anyhow
- Outdated: async-trait
- Outdated: bytes
- Outdated: clap
- Outdated: futures
- Outdated: log
- Outdated: serde
- Outdated: serde_json
- Outdated: slog
- Outdated: slog-scope
- Outdated: sloggers
- Outdated: tokio
- Outdated: tokio-stream
- Outdated: tokio-util
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-a53b121290674a8ba98eafd0831a246c/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a53b121290674a8ba98eafd0831a246c/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 . | 20 | 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 . /tmp/codehealth-osv-sbom-adfbb845807b4293a378807a1b6cd028 | 38 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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 . /tmp/codehealth-osv-sbom-adfbb845807b4293a378807a1b6cd028 | 0 | artifacts/raw/osv-scanner.json |