Executive summary
HectorMRC/rauth falls short of our standard for a preview release because 14 files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 56 out of 100 and is rated Adequate, and 31 of its 36 critical findings are security problems.
Maturity, at 41, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 12 points. Having someone learn and document the 14 files no active contributor knows comes next, worth about 11 points. Raising Maturity to 62 would lift the score to about 62.
Twenty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five passwords or keys are open to anyone who can read the repository, and four secrets can leak from the build pipeline. Pinning each tool to an exact version, replacing each exposed password or key and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once. The four sets of files in separate parts that keep changing together need that dependency made explicit.
The product code is 3,987 lines, about €4,600 to rebuild.
If Maturity rose from 41 to 62, the lowest score rated Strong, the score would rise from 56 to about 62.
New since the last survey: 11 findings
- Code Duplication · Edited copy of a member (31 corresponding lines) src/crypto.rs
- Code Duplication · Edited copies of one member (3 members, 29+ corresponding lines) src/user/application.rs
- Code Duplication · Edited copy of a member (21 corresponding lines) src/secret/repository.rs
- Code Duplication · Edited copy of a member (18 corresponding lines) src/smtp.rs
- Code Duplication · Edited copy of a member (14 corresponding lines) src/crypto.rs
- Code Duplication · Edited copies of one member (4 members, 13+ corresponding lines) src/user/application.rs
- Code Duplication · Edited copies of one member (5 members, 22+ corresponding lines) src/secret/repository.rs
- Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) src/metadata/repository.rs
- Code Duplication · Edited copy of a member (11 corresponding lines) src/secret/repository.rs
- Code Duplication · Edited copies of one member (3 members, 15+ corresponding lines) src/metadata/repository.rs
- Code Duplication · Duplicated block (9 lines × 2) src/secret/repository.rs
Fixed since the last survey: 1 finding
- Code Duplication · Duplicated block (11 lines × 2) src/secret/repository.rs
Rebuild cost: about €4,600 · Estimate
| Cost to rebuild | €1,500 to €7,700, for 26 to 81 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.8 at a score of 56. 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,987 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 rauth.base64 | 2 rauth.bin.grpc | 3 rauth.bin.rest | 4 rauth.crypto | 5 rauth.email | 6 rauth.grpc | 7 rauth.http | 8 rauth.metadata.domain | 9 rauth.rabbitmq | 10 rauth.regex | 11 rauth.result | 12 rauth.time | 13 rauth.token.domain | 14 scripts | 15 rauth.metadata.application | 16 rauth.token.application | 17 rauth.user.domain | 18 rauth.metadata.repository | 19 rauth.secret.domain | 20 rauth.session.application | 21 rauth.session.rest | 22 rauth.token.repository | 23 rauth.user.application | 24 rauth.secret.application | 25 rauth.session.grpc | 26 rauth.smtp | 27 rauth.user.event_bus | 28 rauth.user.grpc | 29 rauth.user.repository | 30 rauth.secret.repository |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 rauth.base64 | ||||||||||||||||||||||||||||||
| 2 rauth.bin.grpc | ||||||||||||||||||||||||||||||
| 3 rauth.bin.rest | ||||||||||||||||||||||||||||||
| 4 rauth.crypto | ||||||||||||||||||||||||||||||
| 5 rauth.email | ||||||||||||||||||||||||||||||
| 6 rauth.grpc | ||||||||||||||||||||||||||||||
| 7 rauth.http | ||||||||||||||||||||||||||||||
| 8 rauth.metadata.domain | ||||||||||||||||||||||||||||||
| 9 rauth.rabbitmq | ||||||||||||||||||||||||||||||
| 10 rauth.regex | ||||||||||||||||||||||||||||||
| 11 rauth.result | ||||||||||||||||||||||||||||||
| 12 rauth.time | ||||||||||||||||||||||||||||||
| 13 rauth.token.domain | ||||||||||||||||||||||||||||||
| 14 scripts | ||||||||||||||||||||||||||||||
| 15 rauth.metadata.application | 1 | |||||||||||||||||||||||||||||
| 16 rauth.token.application | 3 | |||||||||||||||||||||||||||||
| 17 rauth.user.domain | 1 | |||||||||||||||||||||||||||||
| 18 rauth.metadata.repository | 1 | 1 | ||||||||||||||||||||||||||||
| 19 rauth.secret.domain | 1 | 1 | ||||||||||||||||||||||||||||
| 20 rauth.session.application | 2 | |||||||||||||||||||||||||||||
| 21 rauth.session.rest | 1 | |||||||||||||||||||||||||||||
| 22 rauth.token.repository | 1 | |||||||||||||||||||||||||||||
| 23 rauth.user.application | 1 | 2 | ||||||||||||||||||||||||||||
| 24 rauth.secret.application | 1 | |||||||||||||||||||||||||||||
| 25 rauth.session.grpc | 1 | |||||||||||||||||||||||||||||
| 26 rauth.smtp | 1 | |||||||||||||||||||||||||||||
| 27 rauth.user.event_bus | 1 | 1 | 1 | |||||||||||||||||||||||||||
| 28 rauth.user.grpc | 1 | 1 | ||||||||||||||||||||||||||||
| 29 rauth.user.repository | 1 | 1 | ||||||||||||||||||||||||||||
| 30 rauth.secret.repository | 1 | 1 |
15→8 rauth.metadata.application uses rauth.metadata.domain✕
- Connections
- 1 pair of types, where a type in rauth.metadata.application uses a type in rauth.metadata.domain.
- The types involved
rauth.metadata.application.MetadataRepository→rauth.metadata.domain.Metadata
- Direction
- rauth.metadata.application uses rauth.metadata.domain, so a change to rauth.metadata.domain can break rauth.metadata.application, while a change to rauth.metadata.application can't break rauth.metadata.domain.
- Position
- Below the diagonal: rauth.metadata.application uses a module listed above it, which is the healthy direction.
16→13 rauth.token.application uses rauth.token.domain✕
- Connections
- 3 pairs of types, where a type in rauth.token.application uses a type in rauth.token.domain.
- The types involved
rauth.token.application.TokenApplication→rauth.token.domain.Tokenrauth.token.application.TokenApplication→rauth.token.domain.TokenKindrauth.token.application.VerifyOptions→rauth.token.domain.TokenKind
- Direction
- rauth.token.application uses rauth.token.domain, so a change to rauth.token.domain can break rauth.token.application, while a change to rauth.token.application can't break rauth.token.domain.
- Position
- Below the diagonal: rauth.token.application uses a module listed above it, which is the healthy direction.
17→8 rauth.user.domain uses rauth.metadata.domain✕
- Connections
- 1 pair of types, where a type in rauth.user.domain uses a type in rauth.metadata.domain.
- The types involved
rauth.user.domain.User→rauth.metadata.domain.Metadata
- Direction
- rauth.user.domain uses rauth.metadata.domain, so a change to rauth.metadata.domain can break rauth.user.domain, while a change to rauth.user.domain can't break rauth.metadata.domain.
- Position
- Below the diagonal: rauth.user.domain uses a module listed above it, which is the healthy direction.
18→8 rauth.metadata.repository uses rauth.metadata.domain✕
- Connections
- 1 pair of types, where a type in rauth.metadata.repository uses a type in rauth.metadata.domain.
- The types involved
rauth.metadata.repository.PostgresMetadataRepository→rauth.metadata.domain.Metadata
- Direction
- rauth.metadata.repository uses rauth.metadata.domain, so a change to rauth.metadata.domain can break rauth.metadata.repository, while a change to rauth.metadata.repository can't break rauth.metadata.domain.
- Position
- Below the diagonal: rauth.metadata.repository uses a module listed above it, which is the healthy direction.
18→15 rauth.metadata.repository uses rauth.metadata.application✕
- Connections
- 1 pair of types, where a type in rauth.metadata.repository uses a type in rauth.metadata.application.
- The types involved
rauth.metadata.repository.PostgresMetadataRepository→rauth.metadata.application.MetadataRepository
- Direction
- rauth.metadata.repository uses rauth.metadata.application, so a change to rauth.metadata.application can break rauth.metadata.repository, while a change to rauth.metadata.repository can't break rauth.metadata.application.
- Position
- Below the diagonal: rauth.metadata.repository uses a module listed above it, which is the healthy direction.
19→8 rauth.secret.domain uses rauth.metadata.domain✕
- Connections
- 1 pair of types, where a type in rauth.secret.domain uses a type in rauth.metadata.domain.
- The types involved
rauth.secret.domain.Secret→rauth.metadata.domain.Metadata
- Direction
- rauth.secret.domain uses rauth.metadata.domain, so a change to rauth.metadata.domain can break rauth.secret.domain, while a change to rauth.secret.domain can't break rauth.metadata.domain.
- Position
- Below the diagonal: rauth.secret.domain uses a module listed above it, which is the healthy direction.
19→17 rauth.secret.domain uses rauth.user.domain✕
- Connections
- 1 pair of types, where a type in rauth.secret.domain uses a type in rauth.user.domain.
- The types involved
rauth.secret.domain.Secret→rauth.user.domain.User
- Direction
- rauth.secret.domain uses rauth.user.domain, so a change to rauth.user.domain can break rauth.secret.domain, while a change to rauth.secret.domain can't break rauth.user.domain.
- Position
- Below the diagonal: rauth.secret.domain uses a module listed above it, which is the healthy direction.
20→16 rauth.session.application uses rauth.token.application✕
- Connections
- 2 pairs of types, where a type in rauth.session.application uses a type in rauth.token.application.
- The types involved
rauth.session.application.SessionApplication→rauth.token.application.TokenApplicationrauth.session.application.application$module→rauth.token.application.TokenApplication
- Direction
- rauth.session.application uses rauth.token.application, so a change to rauth.token.application can break rauth.session.application, while a change to rauth.session.application can't break rauth.token.application.
- Position
- Below the diagonal: rauth.session.application uses a module listed above it, which is the healthy direction.
21→16 rauth.session.rest uses rauth.token.application✕
- Connections
- 1 pair of types, where a type in rauth.session.rest uses a type in rauth.token.application.
- The types involved
rauth.session.rest.SessionRestService→rauth.token.application.TokenApplication
- Direction
- rauth.session.rest uses rauth.token.application, so a change to rauth.token.application can break rauth.session.rest, while a change to rauth.session.rest can't break rauth.token.application.
- Position
- Below the diagonal: rauth.session.rest uses a module listed above it, which is the healthy direction.
22→16 rauth.token.repository uses rauth.token.application✕
- Connections
- 1 pair of types, where a type in rauth.token.repository uses a type in rauth.token.application.
- The types involved
rauth.token.repository.RedisTokenRepository→rauth.token.application.TokenRepository
- Direction
- rauth.token.repository uses rauth.token.application, so a change to rauth.token.application can break rauth.token.repository, while a change to rauth.token.repository can't break rauth.token.application.
- Position
- Below the diagonal: rauth.token.repository uses a module listed above it, which is the healthy direction.
23→16 rauth.user.application uses rauth.token.application✕
- Connections
- 1 pair of types, where a type in rauth.user.application uses a type in rauth.token.application.
- The types involved
rauth.user.application.UserApplication→rauth.token.application.TokenApplication
- Direction
- rauth.user.application uses rauth.token.application, so a change to rauth.token.application can break rauth.user.application, while a change to rauth.user.application can't break rauth.token.application.
- Position
- Below the diagonal: rauth.user.application uses a module listed above it, which is the healthy direction.
23→17 rauth.user.application uses rauth.user.domain✕
- Connections
- 2 pairs of types, where a type in rauth.user.application uses a type in rauth.user.domain.
- The types involved
rauth.user.application.EventBus→rauth.user.domain.Userrauth.user.application.UserRepository→rauth.user.domain.User
- Direction
- rauth.user.application uses rauth.user.domain, so a change to rauth.user.domain can break rauth.user.application, while a change to rauth.user.application can't break rauth.user.domain.
- Position
- Below the diagonal: rauth.user.application uses a module listed above it, which is the healthy direction.
24→19 rauth.secret.application uses rauth.secret.domain✕
- Connections
- 1 pair of types, where a type in rauth.secret.application uses a type in rauth.secret.domain.
- The types involved
rauth.secret.application.SecretRepository→rauth.secret.domain.Secret
- Direction
- rauth.secret.application uses rauth.secret.domain, so a change to rauth.secret.domain can break rauth.secret.application, while a change to rauth.secret.application can't break rauth.secret.domain.
- Position
- Below the diagonal: rauth.secret.application uses a module listed above it, which is the healthy direction.
25→20 rauth.session.grpc uses rauth.session.application✕
- Connections
- 1 pair of types, where a type in rauth.session.grpc uses a type in rauth.session.application.
- The types involved
rauth.session.grpc.SessionGrpcService→rauth.session.application.SessionApplication
- Direction
- rauth.session.grpc uses rauth.session.application, so a change to rauth.session.application can break rauth.session.grpc, while a change to rauth.session.grpc can't break rauth.session.application.
- Position
- Below the diagonal: rauth.session.grpc uses a module listed above it, which is the healthy direction.
26→23 rauth.smtp uses rauth.user.application✕
- Connections
- 1 pair of types, where a type in rauth.smtp uses a type in rauth.user.application.
- The types involved
rauth.smtp.Smtp→rauth.user.application.Mailer
- Direction
- rauth.smtp uses rauth.user.application, so a change to rauth.user.application can break rauth.smtp, while a change to rauth.smtp can't break rauth.user.application.
- Position
- Below the diagonal: rauth.smtp uses a module listed above it, which is the healthy direction.
27→9 rauth.user.event_bus uses rauth.rabbitmq✕
- Connections
- 1 pair of types, where a type in rauth.user.event_bus uses a type in rauth.rabbitmq.
- The types involved
rauth.user.event_bus.UserEventPayload→rauth.rabbitmq.EventKind
- Direction
- rauth.user.event_bus uses rauth.rabbitmq, so a change to rauth.rabbitmq can break rauth.user.event_bus, while a change to rauth.user.event_bus can't break rauth.rabbitmq.
- Position
- Below the diagonal: rauth.user.event_bus uses a module listed above it, which is the healthy direction.
27→17 rauth.user.event_bus uses rauth.user.domain✕
- Connections
- 1 pair of types, where a type in rauth.user.event_bus uses a type in rauth.user.domain.
- The types involved
rauth.user.event_bus.RabbitMqUserBus→rauth.user.domain.User
- Direction
- rauth.user.event_bus uses rauth.user.domain, so a change to rauth.user.domain can break rauth.user.event_bus, while a change to rauth.user.event_bus can't break rauth.user.domain.
- Position
- Below the diagonal: rauth.user.event_bus uses a module listed above it, which is the healthy direction.
27→23 rauth.user.event_bus uses rauth.user.application✕
- Connections
- 1 pair of types, where a type in rauth.user.event_bus uses a type in rauth.user.application.
- The types involved
rauth.user.event_bus.RabbitMqUserBus→rauth.user.application.EventBus
- Direction
- rauth.user.event_bus uses rauth.user.application, so a change to rauth.user.application can break rauth.user.event_bus, while a change to rauth.user.event_bus can't break rauth.user.application.
- Position
- Below the diagonal: rauth.user.event_bus uses a module listed above it, which is the healthy direction.
28→17 rauth.user.grpc uses rauth.user.domain✕
- Connections
- 1 pair of types, where a type in rauth.user.grpc uses a type in rauth.user.domain.
- The types involved
rauth.user.grpc.UserGrpcService→rauth.user.domain.User
- Direction
- rauth.user.grpc uses rauth.user.domain, so a change to rauth.user.domain can break rauth.user.grpc, while a change to rauth.user.grpc can't break rauth.user.domain.
- Position
- Below the diagonal: rauth.user.grpc uses a module listed above it, which is the healthy direction.
28→23 rauth.user.grpc uses rauth.user.application✕
- Connections
- 1 pair of types, where a type in rauth.user.grpc uses a type in rauth.user.application.
- The types involved
rauth.user.grpc.UserGrpcService→rauth.user.application.UserApplication
- Direction
- rauth.user.grpc uses rauth.user.application, so a change to rauth.user.application can break rauth.user.grpc, while a change to rauth.user.grpc can't break rauth.user.application.
- Position
- Below the diagonal: rauth.user.grpc uses a module listed above it, which is the healthy direction.
29→17 rauth.user.repository uses rauth.user.domain✕
- Connections
- 1 pair of types, where a type in rauth.user.repository uses a type in rauth.user.domain.
- The types involved
rauth.user.repository.PostgresUserRepository→rauth.user.domain.User
- Direction
- rauth.user.repository uses rauth.user.domain, so a change to rauth.user.domain can break rauth.user.repository, while a change to rauth.user.repository can't break rauth.user.domain.
- Position
- Below the diagonal: rauth.user.repository uses a module listed above it, which is the healthy direction.
29→23 rauth.user.repository uses rauth.user.application✕
- Connections
- 1 pair of types, where a type in rauth.user.repository uses a type in rauth.user.application.
- The types involved
rauth.user.repository.PostgresUserRepository→rauth.user.application.UserRepository
- Direction
- rauth.user.repository uses rauth.user.application, so a change to rauth.user.application can break rauth.user.repository, while a change to rauth.user.repository can't break rauth.user.application.
- Position
- Below the diagonal: rauth.user.repository uses a module listed above it, which is the healthy direction.
30→19 rauth.secret.repository uses rauth.secret.domain✕
- Connections
- 1 pair of types, where a type in rauth.secret.repository uses a type in rauth.secret.domain.
- The types involved
rauth.secret.repository.PostgresSecretRepository→rauth.secret.domain.Secret
- Direction
- rauth.secret.repository uses rauth.secret.domain, so a change to rauth.secret.domain can break rauth.secret.repository, while a change to rauth.secret.repository can't break rauth.secret.domain.
- Position
- Below the diagonal: rauth.secret.repository uses a module listed above it, which is the healthy direction.
30→24 rauth.secret.repository uses rauth.secret.application✕
- Connections
- 1 pair of types, where a type in rauth.secret.repository uses a type in rauth.secret.application.
- The types involved
rauth.secret.repository.PostgresSecretRepository→rauth.secret.application.SecretRepository
- Direction
- rauth.secret.repository uses rauth.secret.application, so a change to rauth.secret.application can break rauth.secret.repository, while a change to rauth.secret.repository can't break rauth.secret.application.
- Position
- Below the diagonal: rauth.secret.repository uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 32 | High / Critical |
| A02:2025 — Security Misconfiguration | 11 | Medium |
| A07:2025 — Authentication Failures | 6 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 6 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml; Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with repository.rs (4), application.rs (3), domain.rs (2); 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. | +11.8 pts | Low | ADR Quality |
| Resolve the 14 Orphaned file finding(s) in Knowledge Freshness — start with repository.rs (4), application.rs (3), domain.rs (2). | +10.9 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. | +8.6 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with application.rs. | +3.8 pts | Low | Knowledge Freshness |
| Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (5). | +2.6 pts | Low | Secrets (history) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +2.1 pts | Low | Supply-chain Provenance & Signing |
| Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps. | +3.6 pts | Medium | Data Protection |
| Add a build/run (quick start) section to the root README — the first thing a newcomer needs. | +3.3 pts | Medium | Documentation (README) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.6 | Mixed | Secrets (history): High secret: REDACTED |
| src/secret/repository.rs | 5.1 | Mixed | Change Coupling: Boundary-crossing change coupling: repository.rs ↔ repository.rs |
| REDACTED | 5.8 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/session/grpc.rs | 6.5 | Mixed | Change Coupling: Boundary-crossing change coupling: grpc.rs ↔ repository.rs |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| REDACTED | 6.9 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| src/user/application.rs | 7.1 | Near-clean | Code Duplication: Edited copies of one member (3 members, 29+ corresponding lines) |
| src/metadata/repository.rs | 7.2 | Near-clean | Code Duplication: Edited copies of one member (3 members, 18+ corresponding lines) |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| src/crypto.rs | 7.4 | Near-clean | Code Duplication: Edited copy of a member (31 corresponding lines) |
| src/smtp.rs | 7.8 | Near-clean | Code Duplication: Edited copy of a member (18 corresponding lines) |
| src/metadata/domain.rs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: domain.rs ↔ domain.rs |
| src/token/repository.rs | 8.0 | Near-clean | Change Coupling: Boundary-crossing change coupling: repository.rs ↔ grpc.rs |
| src/session/application.rs | 8.5 | Near-clean | Code Duplication: Duplicated block (16 lines × 2) |
| Cargo.toml | 9.5 | Near-clean | ADR Quality: No ADRs found |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 39 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 39 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, 92 of 105 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Rust half could not be measured — the Cargo suite in repository root did not build, so it was never run. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo — a coverage step in CI (`cargo llvm-cov`) shows coverage is measured in your own CI.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (repository root, 9 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository declares Cargo manifests but commits no Cargo.lock, so its dependency graph was closed from the manifests over the crates.io index, and part of it could not be read: no published release of log satisfies `0.*`. A licence verdict over part of a dependency graph is not a licence verdict. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (2 contributor(s) across 530 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 1 hold 4% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22'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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
- D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — validating REDACTED: services.redis.security_opt must be a list; runtime evidence skipped.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby 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.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, 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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go and JavaScript/TypeScript source only, and no C# was loaded and no PHP, Java, Kotlin, Python, Ruby, Scala, Dart, Swift, Erlang, Go, JavaScript or TypeScript was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and 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
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- 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.
- DM4 Rich vs anemic domain model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 function(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 function(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
12 duplicated block group(s) detected. 13.9 % of the production lines (553 of 3,987) are in a reported copy. A further 10 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 2 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with repository.rs, grpc.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with application.rs, crypto.rs. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copy of a member (31 corresponding lines) finding(s) in Code Duplication — start with crypto.rs. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 11 classes have LCOM4 above 3.
D12 · Dependency Hygiene
0 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 3987 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with Cargo.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
5 finding(s): 0 critical, 5 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 5 High secret finding(s) in Secrets (history) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
32 finding(s): 0 critical, 26 high, 6 medium, 0 low. 21 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 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-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 21 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 (21 issue-level, 0 of them charged here).
D31 · IaC & Container Security
11 finding(s): 0 critical, 0 high, 11 medium, 0 low.
What to do
- Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (7), REDACTED (4). — One of this dimension's main actionable groups (11 warning-level).
D34 · Knowledge Freshness
15 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/user/application.rs. Counted over 15 of the 35 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 14 Orphaned file finding(s) in Knowledge Freshness — start with repository.rs (4), application.rs (3), domain.rs (2). — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with application.rs. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
Strongest change-coupling: domain.rs↔domain.rs 72%; repository.rs↔grpc.rs 67%; repository.rs↔repository.rs 64%
What to do
- Resolve the 4 Boundary-crossing change coupling finding(s) in Change Coupling — start with repository.rs (2), domain.rs, grpc.rs. — One of this dimension's main actionable groups (4 issue-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX9 · CQS / query purity
C1 · Data Protection
What to do
- Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / Secret Manager, Azure Key Vault, HashiCorp Vault — not a key read from an environment variable beside the data) and encrypt the most sensitive columns (an AEAD over the field before Diesel/sqlx write it, SQLCipher, pgcrypto) — partial coverage still leaves gaps.
- Enforce HTTPS on the server that receives this data: terminate TLS in it (axum-server/actix bind_rustls, tonic ServerTlsConfig, a tokio-rustls acceptor) and send Strict-Transport-Security, or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
What to do
- Name the access rules — roles and permissions declared once (an enum Role/Permission, actix-web-grants #[protect(…)], axum-login's permission_required!, a casbin or oso policy) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM4 · Rich vs anemic domain model
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- 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
P2 · Observability
What to do
- Add a health-check endpoint (a /health route on your axum/actix router) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
P8 · Schema migrations
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()` (src/bin/grpc.rs:119).
- 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()` (src/bin/grpc.rs:119).
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
X28 · Index access outside its own emptiness guard
X4 · Structured logging
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Solid. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 41% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 74% | Strong | Solid. |
| Security | 48% | Weak — gated by D29, D36, C1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model — a struct, Diesel table, SeaORM entity or SQL migration table named for it — a SeaORM ActiveModelBehavior hook or database trigger that records each change, or an event-sourced store beside one) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 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.
- 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 — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — validating REDACTED: services.redis.security_opt must be a list; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- D10 Test Quality — ~7 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.
- D11 Test Reliability — Test reliability not included — the .rs suite was found but not re-run
- D14 License Compliance — Crate licences not graded — the lock-less Cargo graph could not be read in full
- D16 Bus Factor — single-maintainer repository — bus factor is not applicable
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (381 declarations, no unit with a dominant convention).
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .py, .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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (3987 LoC, 40 module-visible types across 8 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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.
- D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet).
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this Cargo build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — Rust suite
- DM1 Aggregate boundaries — this Rust crate declares no domain aggregate (a struct with private state and its own command methods), so DM1's aggregate-boundary read has no population to be taken over
- DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM5 Encapsulated state — this Rust crate declares no type implementing a hand-rolled Hash/PartialEq, so DM5's value-identity encapsulation read has no population to be taken over
- DM6 Domain ↔ infrastructure boundary — this Rust crate maps no type to a persistence framework (diesel/sea-orm/sqlx), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- 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. 1 claim(s) of kinds M4 does not check were not checked (path 1); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the Rust source (service entry point: src/bin/grpc.rs:24 (tonic::transport::Server))
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `#[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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- 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
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not 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.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not 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.
- X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 36 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
- Boundary-crossing change coupling: domain.rs ↔ domain.rs src/metadata/domain.rs:1
- Boundary-crossing change coupling: repository.rs ↔ grpc.rs src/token/repository.rs:1
- Boundary-crossing change coupling: repository.rs ↔ repository.rs src/secret/repository.rs:1
- Boundary-crossing change coupling: grpc.rs ↔ repository.rs src/session/grpc.rs:1
- REDACTED
- Orphaned knowledge src/user/application.rs:1
Serious — 43 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (9 lines × 2) src/secret/repository.rs:102
- Duplicated block (9 lines × 2) src/session/grpc.rs:45
- Duplicated block (8 lines × 2) src/user/application.rs:136
- Duplicated block (8 lines × 2) src/crypto.rs:104
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) src/crypto.rs:97
- Edited copies of one member (3 members, 29+ corresponding lines) src/user/application.rs:149
- Edited copy of a member (21 corresponding lines) src/secret/repository.rs:98
- Edited copy of a member (18 corresponding lines) src/smtp.rs:117
- Edited copy of a member (14 corresponding lines) src/crypto.rs:23
- Edited copies of one member (4 members, 13+ corresponding lines) src/user/application.rs:134
- Edited copies of one member (5 members, 22+ corresponding lines) src/secret/repository.rs:45
- Edited copies of one member (3 members, 18+ corresponding lines) src/metadata/repository.rs:73
- Edited copy of a member (11 corresponding lines) src/secret/repository.rs:27
- Edited copies of one member (3 members, 15+ corresponding lines) src/metadata/repository.rs:93
- Duplicated block (19 lines × 2) src/user/application.rs:204
- Duplicated block (16 lines × 2) src/session/application.rs:37
- Duplicated block (15 lines × 2) src/metadata/repository.rs:28
- Duplicated block (14 lines × 2) src/secret/repository.rs:105
- Duplicated block (10 lines × 3) src/user/application.rs:150
- Duplicated block (6 lines × 3) src/user/application.rs:135
- Duplicated block (6 lines × 2) src/smtp.rs:118
- Duplicated block (12 lines × 2) src/metadata/repository.rs:55
- Coverage collected but not gated
Minor — 26 finding(s)
- Orphaned file src/session/application.rs:1
- Orphaned file src/token/application.rs:1
- Orphaned file src/config.rs:1
- Orphaned file src/user/repository.rs:1
- Orphaned file src/crypto.rs:1
- Orphaned file src/smtp.rs:1
- Orphaned file src/token/domain.rs:1
- Orphaned file src/secret/repository.rs:1
- Orphaned file src/user/grpc.rs:1
- Orphaned file src/user/domain.rs:1
- Orphaned file src/metadata/repository.rs:1
- Orphaned file src/secret/application.rs:1
- Orphaned file src/token/repository.rs:1
- Orphaned file src/user/event_bus.rs:1
- No named authorization policies
- No ADRs found Cargo.toml:60
- REDACTED
- Further orphaned files (smaller)
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No changelog
- No app-layer HTTPS enforcement detected
- No security response headers detected
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fdabe460edf14f689e0ae57b94bee649/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-fdabe460edf14f689e0ae57b94bee649/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 32 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 11 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | none (dependency manifest found, not scanned for vulnerabilities here) | — | none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Cargo manifest — not scanned yet). | 0 | — |