Executive summary
rycont/umjunsik-lang falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 45 out of 100 and is rated Weak, and ten of its 11 critical findings are security problems in its code.
Production Readiness, at 33, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 8 points. Adding an automated build and test pipeline would lift Production Readiness itself, worth about 7 points. Raising Production Readiness to 70 would lift the score to about 53.
Ten weaknesses in the code could be used by an attacker. One part of the code is no longer understood by anyone working on it. Having someone learn the forgotten files and fixing the weaknesses the scanner points to would close both risks.
The product code is 4,200 lines, about €3,100 to rebuild.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 45 to about 53.
New since the last survey: 5 findings
- Cyclomatic Complexity · Run (cyclomatic 26) umjunsik-lang-csharp/Program.cs
- Cognitive Complexity · Run (cognitive 31) umjunsik-lang-csharp/Program.cs
- Code Duplication · Edited copy of a member (30 corresponding lines) umjunsik-lang-rust/compiler/src/main.rs
- Code Duplication · Edited copy of a member (25 corresponding lines) umjunsik-lang-go/parser/parser.go
- Code Duplication · Duplicated block (11 lines × 2) umjunsik-lang-rust/compiler/src/main.rs
Fixed since the last survey: 2 findings
- Code Duplication · Duplicated block (11 lines × 2) umjunsik-lang-rust/compiler/src/main.rs
- Code Coverage · Coverage not measured — no coverage collector is wired up
Rebuild cost: about €3,100 · Estimate
| Cost to rebuild | €1,000 to €5,200, for 17 to 55 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 4,200 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 com.alphagot.kumjunsiklang | 2 setting | 3 setting.console | 4 setting.var | 5 umjunsik-lang-node | 6 umjunsik-lang-python | 7 umjunsik-lang-python.runtime | 8 umjunsik-lang-web.src | 9 umjunsik-lang/umjunsik-lang-go | 10 umjunsik-lang/umjunsik-lang-go/object | 11 umjunsik-lang/umjunsik-lang-go/token | 12 umjunsik.ast | 13 umjunsik.parser | 14 (global) | 15 rummc | 16 rummi | 17 umjunsik-lang/umjunsik-lang-go/ast | 18 umjunsik-lang/umjunsik-lang-go/lexer | 19 umjunsik-lang/umjunsik-lang-go/eval | 20 umjunsik-lang/umjunsik-lang-go/parser |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 com.alphagot.kumjunsiklang | ||||||||||||||||||||
| 2 setting | ||||||||||||||||||||
| 3 setting.console | ||||||||||||||||||||
| 4 setting.var | ||||||||||||||||||||
| 5 umjunsik-lang-node | ||||||||||||||||||||
| 6 umjunsik-lang-python | ||||||||||||||||||||
| 7 umjunsik-lang-python.runtime | ||||||||||||||||||||
| 8 umjunsik-lang-web.src | ||||||||||||||||||||
| 9 umjunsik-lang/umjunsik-lang-go | ||||||||||||||||||||
| 10 umjunsik-lang/umjunsik-lang-go/object | ||||||||||||||||||||
| 11 umjunsik-lang/umjunsik-lang-go/token | ||||||||||||||||||||
| 12 umjunsik.ast | ||||||||||||||||||||
| 13 umjunsik.parser | ||||||||||||||||||||
| 14 (global) | 1 | |||||||||||||||||||
| 15 rummc | 5 | |||||||||||||||||||
| 16 rummi | 2 | |||||||||||||||||||
| 17 umjunsik-lang/umjunsik-lang-go/ast | 12 | |||||||||||||||||||
| 18 umjunsik-lang/umjunsik-lang-go/lexer | 3 | |||||||||||||||||||
| 19 umjunsik-lang/umjunsik-lang-go/eval | 3 | 2 | ||||||||||||||||||
| 20 umjunsik-lang/umjunsik-lang-go/parser | 2 | 4 | 2 |
14→2 (global) uses setting✕
- Connections
- 1 pair of types, where a type in (global) uses a type in setting.
- The types involved
main→setting.Items
- Direction
- (global) uses setting, so a change to setting can break (global), while a change to (global) can't break setting.
- Position
- Below the diagonal: (global) uses a module listed above it, which is the healthy direction.
15→12 rummc uses umjunsik.ast✕
- Connections
- 5 pairs of types, where a type in rummc uses a type in umjunsik.ast.
- The types involved
rummc.Compiler→umjunsik.ast.Loadrummc.Compiler→umjunsik.ast.Multiplyrummc.Compiler→umjunsik.ast.Programrummc.Compiler→umjunsik.ast.Statementrummc.Compiler→umjunsik.ast.Term
- Direction
- rummc uses umjunsik.ast, so a change to umjunsik.ast can break rummc, while a change to rummc can't break umjunsik.ast.
- Position
- Below the diagonal: rummc uses a module listed above it, which is the healthy direction.
16→12 rummi uses umjunsik.ast✕
- Connections
- 2 pairs of types, where a type in rummi uses a type in umjunsik.ast.
- The types involved
rummi.rummi$module→umjunsik.ast.Multiplyrummi.rummi$module→umjunsik.ast.Statement
- Direction
- rummi uses umjunsik.ast, so a change to umjunsik.ast can break rummi, while a change to rummi can't break umjunsik.ast.
- Position
- Below the diagonal: rummi uses a module listed above it, which is the healthy direction.
17→11 umjunsik-lang/umjunsik-lang-go/ast uses umjunsik-lang/umjunsik-lang-go/token✕
- Connections
- 12 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/ast uses a type in umjunsik-lang/umjunsik-lang-go/token.
- The types involved
umjunsik-lang/umjunsik-lang-go/ast.DONGTANExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.ExpressionLine→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.FIGHTINGExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.InfixIntegerExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.IntegerLiteral→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.JUNEExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.SIKBExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.SIKKIExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.SIKQExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.SPACEExpression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.UEpxression→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/ast.UMExpression→umjunsik-lang/umjunsik-lang-go/token.Token
- Direction
- umjunsik-lang/umjunsik-lang-go/ast uses umjunsik-lang/umjunsik-lang-go/token, so a change to umjunsik-lang/umjunsik-lang-go/token can break umjunsik-lang/umjunsik-lang-go/ast, while a change to umjunsik-lang/umjunsik-lang-go/ast can't break umjunsik-lang/umjunsik-lang-go/token.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/ast uses a module listed above it, which is the healthy direction.
18→11 umjunsik-lang/umjunsik-lang-go/lexer uses umjunsik-lang/umjunsik-lang-go/token✕
- Connections
- 3 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/lexer uses a type in umjunsik-lang/umjunsik-lang-go/token.
- The types involved
umjunsik-lang/umjunsik-lang-go/lexer.Lexer→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/lexer.lexer→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/lexer.lexer→umjunsik-lang/umjunsik-lang-go/token.TokenType
- Direction
- umjunsik-lang/umjunsik-lang-go/lexer uses umjunsik-lang/umjunsik-lang-go/token, so a change to umjunsik-lang/umjunsik-lang-go/token can break umjunsik-lang/umjunsik-lang-go/lexer, while a change to umjunsik-lang/umjunsik-lang-go/lexer can't break umjunsik-lang/umjunsik-lang-go/token.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/lexer uses a module listed above it, which is the healthy direction.
19→10 umjunsik-lang/umjunsik-lang-go/eval uses umjunsik-lang/umjunsik-lang-go/object✕
- Connections
- 3 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/eval uses a type in umjunsik-lang/umjunsik-lang-go/object.
- The types involved
umjunsik-lang/umjunsik-lang-go/eval.eval→umjunsik-lang/umjunsik-lang-go/object.Environmentumjunsik-lang/umjunsik-lang-go/eval.eval→umjunsik-lang/umjunsik-lang-go/object.Errorumjunsik-lang/umjunsik-lang-go/eval.eval→umjunsik-lang/umjunsik-lang-go/object.Object
- Direction
- umjunsik-lang/umjunsik-lang-go/eval uses umjunsik-lang/umjunsik-lang-go/object, so a change to umjunsik-lang/umjunsik-lang-go/object can break umjunsik-lang/umjunsik-lang-go/eval, while a change to umjunsik-lang/umjunsik-lang-go/eval can't break umjunsik-lang/umjunsik-lang-go/object.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/eval uses a module listed above it, which is the healthy direction.
19→17 umjunsik-lang/umjunsik-lang-go/eval uses umjunsik-lang/umjunsik-lang-go/ast✕
- Connections
- 2 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/eval uses a type in umjunsik-lang/umjunsik-lang-go/ast.
- The types involved
umjunsik-lang/umjunsik-lang-go/eval.eval→umjunsik-lang/umjunsik-lang-go/ast.Nodeumjunsik-lang/umjunsik-lang-go/eval.eval→umjunsik-lang/umjunsik-lang-go/ast.Program
- Direction
- umjunsik-lang/umjunsik-lang-go/eval uses umjunsik-lang/umjunsik-lang-go/ast, so a change to umjunsik-lang/umjunsik-lang-go/ast can break umjunsik-lang/umjunsik-lang-go/eval, while a change to umjunsik-lang/umjunsik-lang-go/eval can't break umjunsik-lang/umjunsik-lang-go/ast.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/eval uses a module listed above it, which is the healthy direction.
20→11 umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/token✕
- Connections
- 2 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/parser uses a type in umjunsik-lang/umjunsik-lang-go/token.
- The types involved
umjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/token.Tokenumjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/token.TokenType
- Direction
- umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/token, so a change to umjunsik-lang/umjunsik-lang-go/token can break umjunsik-lang/umjunsik-lang-go/parser, while a change to umjunsik-lang/umjunsik-lang-go/parser can't break umjunsik-lang/umjunsik-lang-go/token.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/parser uses a module listed above it, which is the healthy direction.
20→17 umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/ast✕
- Connections
- 4 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/parser uses a type in umjunsik-lang/umjunsik-lang-go/ast.
- The types involved
umjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/ast.Expressionumjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/ast.ExpressionLineumjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/ast.Lineumjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/ast.Program
- Direction
- umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/ast, so a change to umjunsik-lang/umjunsik-lang-go/ast can break umjunsik-lang/umjunsik-lang-go/parser, while a change to umjunsik-lang/umjunsik-lang-go/parser can't break umjunsik-lang/umjunsik-lang-go/ast.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/parser uses a module listed above it, which is the healthy direction.
20→18 umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/lexer✕
- Connections
- 2 pairs of types, where a type in umjunsik-lang/umjunsik-lang-go/parser uses a type in umjunsik-lang/umjunsik-lang-go/lexer.
- The types involved
umjunsik-lang/umjunsik-lang-go/parser.Parser→umjunsik-lang/umjunsik-lang-go/lexer.Lexerumjunsik-lang/umjunsik-lang-go/parser.parser→umjunsik-lang/umjunsik-lang-go/lexer.Lexer
- Direction
- umjunsik-lang/umjunsik-lang-go/parser uses umjunsik-lang/umjunsik-lang-go/lexer, so a change to umjunsik-lang/umjunsik-lang-go/lexer can break umjunsik-lang/umjunsik-lang-go/parser, while a change to umjunsik-lang/umjunsik-lang-go/parser can't break umjunsik-lang/umjunsik-lang-go/lexer.
- Position
- Below the diagonal: umjunsik-lang/umjunsik-lang-go/parser uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 11 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 1 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with umjunsik-lang-csharp.csproj; Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with main.rs (2), index.ts (2), parser.rs; Add a CI workflow that builds and runs the test suite on every push/PR.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with umjunsik-lang-csharp.csproj. | +7.7 pts | Low | ADR Quality |
| Resolve the 11 Orphaned file finding(s) in Knowledge Freshness — start with main.rs (2), index.ts (2), parser.rs. | +7.1 pts | Medium | Knowledge Freshness |
| Add a CI workflow that builds and runs the test suite on every push/PR. | +6.5 pts | Medium | CI/CD gates |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +6.0 pts | Medium | Architecture documentation |
| Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Module1.vb. | +2.5 pts | Low | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +3.4 pts | Medium | Release Hygiene |
| Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`. | +2.6 pts | Medium | Nullable reference types |
| Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. | +1.0 pts | Low | Knowledge Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| umjunsik-lang-rust/compiler/src/main.rs | 7.4 | Mixed | Code Duplication: Edited copy of a member (30 corresponding lines) |
| umjunsik-lang-csharp/umjunsik-lang-csharp.csproj | 7.4 | Mixed | Platform End-of-Life: End-of-life runtime: .NET net6.0 |
| umjunsik-lang-csharp/Program.cs | 7.8 | Mixed | Cyclomatic Complexity: Run (cyclomatic 26) |
| umjunsik-lang-web/src/main.js | 7.8 | Mixed | Cyclomatic Complexity: main.run (cyclomatic 25) |
| umjunsik-lang-deno/index.ts | 7.8 | Mixed | Cyclomatic Complexity: index.run (cyclomatic 23) |
| umjunsik-lang-node/src/index.ts | 7.8 | Mixed | Cyclomatic Complexity: index.run (cyclomatic 22) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| umjunsik-lang-go/lexer/lexer.go | 8.5 | Near-clean | Cyclomatic Complexity: Lexer.NextToken (cyclomatic 20) |
| umjunsik-lang-kotlin/src/main/kotlin/com/alphagot/kumjunsiklang/Main.kt | 8.5 | Near-clean | Cognitive Complexity: MainKt.parseLine (cognitive 25) |
| umjunsik-lang-rust/interpreter/src/main.rs | 8.5 | Near-clean | Cognitive Complexity: rummi::run_statement (cognitive 16) |
| umjunsik-lang-go/parser/parser.go | 8.5 | Near-clean | Code Duplication: Edited copy of a member (25 corresponding lines) |
| REDACTED | 9.3 | Near-clean | Static Analysis (SAST): Low: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
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 34 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 — 34 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, 46 of 54 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — 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. The 2 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .vb (1,199 lines, 29% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rs) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.rs) and this repository declares a Cargo test suite (umjunsik-lang-rust, 1 test file), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Gradle build (build.gradle/build.gradle.kts), but the licence verdict published here was taken over its crate dependencies. Nothing was read about its Gradle dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 12 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 11 of the 36 production source files in this repository: 24 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
- D17 Explicit Debt — 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. The 0 deducted marker(s) and the 0.0/KLoC density on this row were taken over this repository's .NET projects ALONE: .vb (1,199 lines, 29% of production source), .rs (981 lines, 24% of production source), .go (775 lines, 19% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- 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.
- D21 Naming 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- 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. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — 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 most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality 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").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
6 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Run at 26. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being eval.Eval at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: umjunsik-lang-go/eval/eval.go (eval.Eval at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Run (cyclomatic 26), main.run (cyclomatic 25), index.run (cyclomatic 23). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was Run at 31.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with Run (cognitive 31), index.run (cognitive 26), run (cognitive 26). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D4 · Code Duplication
2 duplicated block group(s) detected. 2.6 % of the production lines (95 of 3,677) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .vb (29% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
What to do
- Resolve the 1 Edited copy of a member (30 corresponding lines) finding(s) in Code Duplication — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (25 corresponding lines) finding(s) in Code Duplication — start with parser.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with main.rs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
7 production modules (Gradle+Cargo+npm+Go+Python), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 1 classes have LCOM4 above 3.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 30 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository commits no Cargo.lock, so its graph was resolved here: its manifests' `[dependencies]` and `[build-dependencies]` closed over the crates.io index, each crate at the newest release its requirement admits (what a fresh `cargo generate-lockfile` picks, not a graph the repository has pinned). Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), a Gradle build (build.gradle/build.gradle.kts) and package.json, and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted debt markers + 0 dead symbols across 93 LoC in the .NET projects (0.0/KLoC) → score 10.0. Measured on the .NET source only: .vb, .rs, .go (72% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 3 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 umjunsik-lang-csharp.csproj. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 10 high, 0 medium, 1 low.
What to do
- Resolve the 10 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D30 · Dependency Vulnerabilities
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
12 of 12 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is umjunsik-lang-vba/Module1.vb. Counted over 12 of the 36 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 11 Orphaned file finding(s) in Knowledge Freshness — start with main.rs (2), index.ts (2), parser.rs. — One of this dimension's main actionable groups (11 recommendation-level).
- Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with Module1.vb. — 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
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 3 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with umjunsik-lang-csharp.csproj. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX9 · CQS / query purity
GD1 · Unfinished & placeholder code
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
- No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
What to do
- Add a CI workflow that builds and runs the test suite on every push/PR.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `umjunsik-lang-node/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — umjunsik-lang-node/package.json:9
What to do
- Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
X5 · Nullable reference types
- 0/1 NRT-eligible project(s) enable <Nullable>enable</Nullable> (projects targeting a pre-C#-8 framework are excluded — NRTs aren't available there). NRTs catch a whole class of null-deref bugs at compile time.
What to do
- Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99% | Exemplary | Solid. |
| Maturity | 38% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D29 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 79 check(s) not relevant to this codebase
- AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
- AX1 Captive dependencies — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D10 Test Quality — ~0 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
- D12 Dependency Hygiene — Dependency hygiene not measured
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .c, .go, .java, .kt, .py, .rs, .ts, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 2 candidate(s) found and not reported.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Rust surface was not measured.
- D23 Boundary Type-Coupling — small single-context codebase (3,677 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .java, .kt, .py, .rs source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one project, `umjunsik-lang-csharp` (93 LoC, 0 public types across 0 namespaces), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D27 Navigability — Most of this repository's production source (.c, .go, .java, .kt, .py, .ts, .vb) was not read by navigability analysis, so tracing effort was not assessed — whatever else resolved (another language's projects) is not this repository's navigability. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
- ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — reported, not scored — this repository's C# declares no analysable method bodies (a constants, record or DTO assembly), and this score is a density of unfinished work per method, which has no denominator here. The file-level signals below were still collected and are shown in full
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks.
- P12 CI test-gate honesty — no CI workflow found
- P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- 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 — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- 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.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 2% of this repository's production lines — vbnet (1,199 lines), rust (981 lines), go (775 lines), c (410 lines), java (185 lines), kotlin (171 lines), typescript (152 lines), python (121 lines), javascript (113 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 2% of this repository's production lines — vbnet (1,199 lines), rust (981 lines), go (775 lines), c (410 lines), java (185 lines), kotlin (171 lines), typescript (152 lines), python (121 lines), javascript (113 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — X3 reached only 2% of this repository's production lines — vbnet (1,199 lines), rust (981 lines), go (775 lines), c (410 lines), java (185 lines), kotlin (171 lines), typescript (152 lines), python (121 lines), javascript (113 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 11 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned knowledge umjunsik-lang-vba/Module1.vb:1
Serious — 19 finding(s)
- Run (cyclomatic 26) umjunsik-lang-csharp/Program.cs:21
- main.run (cyclomatic 25) umjunsik-lang-web/src/main.js:36
- index.run (cyclomatic 23) umjunsik-lang-deno/index.ts:3
- index.run (cyclomatic 22) umjunsik-lang-node/src/index.ts:8
- Lexer.NextToken (cyclomatic 20) umjunsik-lang-go/lexer/lexer.go:35
- Run (cognitive 31) umjunsik-lang-csharp/Program.cs:21
- index.run (cognitive 26) umjunsik-lang-deno/index.ts:3
- run (cognitive 26) umjunsik-lang-web/src/main.js:36
- MainKt.parseLine (cognitive 25) umjunsik-lang-kotlin/src/main/kotlin/com/alphagot/kumjunsiklang/Main.kt:26
- index.run (cognitive 24) umjunsik-lang-node/src/index.ts:8
- rummi::run_statement (cognitive 16) umjunsik-lang-rust/interpreter/src/main.rs:115
- REDACTED
- Edited copy of a member (30 corresponding lines) umjunsik-lang-rust/compiler/src/main.rs:107
- Edited copy of a member (25 corresponding lines) umjunsik-lang-go/parser/parser.go:170
- Duplicated block (11 lines × 2) umjunsik-lang-rust/compiler/src/main.rs:108
- Duplicated block (8 lines × 2) umjunsik-lang-rust/compiler/src/main.rs:122
- End-of-life runtime: .NET net6.0 umjunsik-lang-csharp/umjunsik-lang-csharp.csproj:5
- Off the main sequence: umjunsik (Cargo)
- No CI pipeline
Minor — 24 finding(s)
- Orphaned file umjunsik-lang-rust/compiler/src/main.rs:1
- Orphaned file umjunsik-lang-rust/lib/src/parser.rs:1
- Orphaned file umjunsik-lang-go/parser/parser.go:1
- Orphaned file umjunsik-lang-rust/interpreter/src/main.rs:1
- Orphaned file umjunsik-lang-go/ast/ast.go:1
- Orphaned file umjunsik-lang-csharp/Program.cs:1
- Orphaned file umjunsik-lang-kotlin/src/main/kotlin/com/alphagot/kumjunsiklang/Main.kt:1
- Orphaned file umjunsik-lang-python/runtime.py:1
- Orphaned file umjunsik-lang-deno/index.ts:1
- Orphaned file umjunsik-lang-node/src/index.ts:1
- Orphaned file umjunsik-lang-go/lexer/lexer.go:1
- Duplicated predicate umjunsik-lang-node/src/index.ts:32
- Duplicated predicate umjunsik-lang-node/src/index.ts:46
- Duplicated predicate umjunsik-lang-node/src/index.ts:50
- Duplicated predicate umjunsik-lang-node/src/index.ts:11
- No ADRs found umjunsik-lang-csharp/umjunsik-lang-csharp.csproj:4
- REDACTED
- Further orphaned files (smaller)
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation umjunsik-lang-node/package.json:9
- No changelog
- Nullable reference types not enabled everywhere
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-c378cc1942be48e8a13855bda503e3af/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-c378cc1942be48e8a13855bda503e3af/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 . | 11 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list umjunsik-lang-csharp/umjunsik-lang-csharp.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D36 · Supply-chain Provenance & Signing | provenance | — | provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |