Executive summary
uber-go/zap falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 69 out of 100 and is rated Adequate, and all nine of its critical findings are security problems in the build pipeline and in its automatic dependency updates.
Maturity, at 56, 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 37 files no active contributor knows comes next, worth about 10 points. Raising Maturity to 70 would lift the score to about 75.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. One automatic update takes new releases before a bad one can be spotted, and one secret can leak from the build pipeline. Pinning each tool to an exact version, setting a waiting period for automatic updates and limiting the secret to its own step would close these risks.
The product code is 8,569 lines, about €28,000 to rebuild.
If Maturity rose from 56 to 70, the lowest score rated Strong, the score would rise from 69 to about 75.
New since the last survey: 1 finding
- Code Duplication · Edited copy of a member (10 corresponding lines) sugar.go
Rebuild cost: about €28,000 · Estimate
| Cost to rebuild | €9,200 to €46,000, for 154 to 489 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 69. 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: 8,569 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 org/zap/internal/color | 2 org/zap/internal/exit | 3 org/zap/internal/pool | 4 org/zap/internal/readme | 5 org/zap/buffer | 6 org/zap/internal/bufferpool | 7 org/zap/internal/stacktrace | 8 org/zap/zapcore | 9 org/zap/exp/zapfield | 10 org/zap/exp/zapslog | 11 org/zap/internal | 12 org/zap/internal/ztest | 13 org/zap | 14 org/zap/zaptest/observer | 15 org/zap/zapgrpc | 16 org/zap/zapio | 17 org/zap/zaptest |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 org/zap/internal/color | |||||||||||||||||
| 2 org/zap/internal/exit | |||||||||||||||||
| 3 org/zap/internal/pool | |||||||||||||||||
| 4 org/zap/internal/readme | |||||||||||||||||
| 5 org/zap/buffer | 1 | ||||||||||||||||
| 6 org/zap/internal/bufferpool | 1 | ||||||||||||||||
| 7 org/zap/internal/stacktrace | 2 | ||||||||||||||||
| 8 org/zap/zapcore | 1 | 4 | 5 | ||||||||||||||
| 9 org/zap/exp/zapfield | 2 | ||||||||||||||||
| 10 org/zap/exp/zapslog | 6 | ||||||||||||||||
| 11 org/zap/internal | 2 | ||||||||||||||||
| 12 org/zap/internal/ztest | 5 | ||||||||||||||||
| 13 org/zap | 60 | 1 | |||||||||||||||
| 14 org/zap/zaptest/observer | 11 | 1 | |||||||||||||||
| 15 org/zap/zapgrpc | 4 | 2 | |||||||||||||||
| 16 org/zap/zapio | 2 | 2 | |||||||||||||||
| 17 org/zap/zaptest | 3 | 3 |
5→3 org/zap/buffer uses org/zap/internal/pool✕
- Connections
- 1 pair of types, where a type in org/zap/buffer uses a type in org/zap/internal/pool.
- The types involved
go.uber.org/zap/buffer.Pool→go.uber.org/zap/internal/pool.Pool
- Direction
- org/zap/buffer uses org/zap/internal/pool, so a change to org/zap/internal/pool can break org/zap/buffer, while a change to org/zap/buffer can't break org/zap/internal/pool.
- Position
- Below the diagonal: org/zap/buffer uses a module listed above it, which is the healthy direction.
6→5 org/zap/internal/bufferpool uses org/zap/buffer✕
- Connections
- 1 pair of types, where a type in org/zap/internal/bufferpool uses a type in org/zap/buffer.
- The types involved
go.uber.org/zap/internal/bufferpool.bufferpool→go.uber.org/zap/buffer.Pool
- Direction
- org/zap/internal/bufferpool uses org/zap/buffer, so a change to org/zap/buffer can break org/zap/internal/bufferpool, while a change to org/zap/internal/bufferpool can't break org/zap/buffer.
- Position
- Below the diagonal: org/zap/internal/bufferpool uses a module listed above it, which is the healthy direction.
7→5 org/zap/internal/stacktrace uses org/zap/buffer✕
- Connections
- 2 pairs of types, where a type in org/zap/internal/stacktrace uses a type in org/zap/buffer.
- The types involved
go.uber.org/zap/internal/stacktrace.Formatter→go.uber.org/zap/buffer.Buffergo.uber.org/zap/internal/stacktrace.stacktrace→go.uber.org/zap/buffer.Buffer
- Direction
- org/zap/internal/stacktrace uses org/zap/buffer, so a change to org/zap/buffer can break org/zap/internal/stacktrace, while a change to org/zap/internal/stacktrace can't break org/zap/buffer.
- Position
- Below the diagonal: org/zap/internal/stacktrace uses a module listed above it, which is the healthy direction.
8→1 org/zap/zapcore uses org/zap/internal/color✕
- Connections
- 1 pair of types, where a type in org/zap/zapcore uses a type in org/zap/internal/color.
- The types involved
go.uber.org/zap/zapcore.zapcore→go.uber.org/zap/internal/color.Color
- Direction
- org/zap/zapcore uses org/zap/internal/color, so a change to org/zap/internal/color can break org/zap/zapcore, while a change to org/zap/zapcore can't break org/zap/internal/color.
- Position
- Below the diagonal: org/zap/zapcore uses a module listed above it, which is the healthy direction.
8→5 org/zap/zapcore uses org/zap/buffer✕
- Connections
- 4 pairs of types, where a type in org/zap/zapcore uses a type in org/zap/buffer.
- The types involved
go.uber.org/zap/zapcore.Encoder→go.uber.org/zap/buffer.Buffergo.uber.org/zap/zapcore.consoleEncoder→go.uber.org/zap/buffer.Buffergo.uber.org/zap/zapcore.jsonEncoder→go.uber.org/zap/buffer.Buffergo.uber.org/zap/zapcore.zapcore→go.uber.org/zap/buffer.Buffer
- Direction
- org/zap/zapcore uses org/zap/buffer, so a change to org/zap/buffer can break org/zap/zapcore, while a change to org/zap/zapcore can't break org/zap/buffer.
- Position
- Below the diagonal: org/zap/zapcore uses a module listed above it, which is the healthy direction.
8→11 org/zap/zapcore uses org/zap/internal part of a loop✕
- Connections
- 5 pairs of types, where a type in org/zap/zapcore uses a type in org/zap/internal.
- The types involved
go.uber.org/zap/zapcore.hooked→go.uber.org/zap/internal.LeveledEnablergo.uber.org/zap/zapcore.ioCore→go.uber.org/zap/internal.LeveledEnablergo.uber.org/zap/zapcore.levelFilterCore→go.uber.org/zap/internal.LeveledEnablergo.uber.org/zap/zapcore.multiCore→go.uber.org/zap/internal.LeveledEnablergo.uber.org/zap/zapcore.sampler→go.uber.org/zap/internal.LeveledEnabler
- Direction
- org/zap/zapcore uses org/zap/internal, so a change to org/zap/internal can break org/zap/zapcore, while a change to org/zap/zapcore can't break org/zap/internal.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→8 org/zap/exp/zapfield uses org/zap/zapcore✕
- Connections
- 2 pairs of types, where a type in org/zap/exp/zapfield uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/exp/zapfield.stringArray→go.uber.org/zap/zapcore.ArrayEncodergo.uber.org/zap/exp/zapfield.zapfield→go.uber.org/zap/zapcore.Field
- Direction
- org/zap/exp/zapfield uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/exp/zapfield, while a change to org/zap/exp/zapfield can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/exp/zapfield uses a module listed above it, which is the healthy direction.
10→8 org/zap/exp/zapslog uses org/zap/zapcore✕
- Connections
- 6 pairs of types, where a type in org/zap/exp/zapslog uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/exp/zapslog.Handler→go.uber.org/zap/zapcore.Corego.uber.org/zap/exp/zapslog.Handler→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap/exp/zapslog.groupObject→go.uber.org/zap/zapcore.ObjectEncodergo.uber.org/zap/exp/zapslog.zapslog→go.uber.org/zap/zapcore.Corego.uber.org/zap/exp/zapslog.zapslog→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap/exp/zapslog.zapslog→go.uber.org/zap/zapcore.Level
- Direction
- org/zap/exp/zapslog uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/exp/zapslog, while a change to org/zap/exp/zapslog can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/exp/zapslog uses a module listed above it, which is the healthy direction.
11→8 org/zap/internal uses org/zap/zapcore✕
- Connections
- 2 pairs of types, where a type in org/zap/internal uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/internal.LeveledEnabler→go.uber.org/zap/zapcore.Levelgo.uber.org/zap/internal.LeveledEnabler→go.uber.org/zap/zapcore.LevelEnabler
- Direction
- org/zap/internal uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/internal, while a change to org/zap/internal can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/internal uses a module listed above it, which is the healthy direction.
12→8 org/zap/internal/ztest uses org/zap/zapcore✕
- Connections
- 5 pairs of types, where a type in org/zap/internal/ztest uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/internal/ztest.Buffer→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap/internal/ztest.Discarder→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap/internal/ztest.FailWriter→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap/internal/ztest.MockClock→go.uber.org/zap/zapcore.Clockgo.uber.org/zap/internal/ztest.ShortWriter→go.uber.org/zap/zapcore.WriteSyncer
- Direction
- org/zap/internal/ztest uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/internal/ztest, while a change to org/zap/internal/ztest can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/internal/ztest uses a module listed above it, which is the healthy direction.
13→8 org/zap uses org/zap/zapcore✕
- Connections
- 60 pairs of types, where a type in org/zap uses a type in org/zap/zapcore. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
go.uber.org/zap.AtomicLevel→go.uber.org/zap/zapcore.Levelgo.uber.org/zap.AtomicLevel→go.uber.org/zap/zapcore.leveledEnablergo.uber.org/zap.Config→go.uber.org/zap/zapcore.Encodergo.uber.org/zap.Config→go.uber.org/zap/zapcore.EncoderConfiggo.uber.org/zap.Config→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap.LevelEnablerFunc→go.uber.org/zap/zapcore.Levelgo.uber.org/zap.Logger→go.uber.org/zap/zapcore.CheckWriteHookgo.uber.org/zap.Logger→go.uber.org/zap/zapcore.CheckedEntrygo.uber.org/zap.Logger→go.uber.org/zap/zapcore.Clockgo.uber.org/zap.Logger→go.uber.org/zap/zapcore.Corego.uber.org/zap.Logger→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap.Logger→go.uber.org/zap/zapcore.Levelgo.uber.org/zap.Logger→go.uber.org/zap/zapcore.LevelEnablergo.uber.org/zap.Logger→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap.ObjectMarshalerPtr→go.uber.org/zap/zapcore.ObjectMarshalergo.uber.org/zap.Sink→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap.SugaredLogger→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap.SugaredLogger→go.uber.org/zap/zapcore.Levelgo.uber.org/zap.anyFieldC→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap.bools→go.uber.org/zap/zapcore.ArrayEncodergo.uber.org/zap.byteStringsArray→go.uber.org/zap/zapcore.ArrayEncodergo.uber.org/zap.complex128s→go.uber.org/zap/zapcore.ArrayEncodergo.uber.org/zap.complex64s→go.uber.org/zap/zapcore.ArrayEncodergo.uber.org/zap.dictObject→go.uber.org/zap/zapcore.ObjectEncodergo.uber.org/zap.durations→go.uber.org/zap/zapcore.ArrayEncoder
- Direction
- org/zap uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap, while a change to org/zap can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap uses a module listed above it, which is the healthy direction.
13→11 org/zap uses org/zap/internal✕
- Connections
- 1 pair of types, where a type in org/zap uses a type in org/zap/internal.
- The types involved
go.uber.org/zap.AtomicLevel→go.uber.org/zap/internal.LeveledEnabler
- Direction
- org/zap uses org/zap/internal, so a change to org/zap/internal can break org/zap, while a change to org/zap can't break org/zap/internal.
- Position
- Below the diagonal: org/zap uses a module listed above it, which is the healthy direction.
14→8 org/zap/zaptest/observer uses org/zap/zapcore✕
- Connections
- 11 pairs of types, where a type in org/zap/zaptest/observer uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/zaptest/observer.LoggedEntry→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap/zaptest/observer.ObservedLogs→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap/zaptest/observer.ObservedLogs→go.uber.org/zap/zapcore.Levelgo.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.CheckedEntrygo.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.Corego.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.Entrygo.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.Fieldgo.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.Levelgo.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/zapcore.leveledEnablergo.uber.org/zap/zaptest/observer.observer→go.uber.org/zap/zapcore.Corego.uber.org/zap/zaptest/observer.observer→go.uber.org/zap/zapcore.LevelEnabler
- Direction
- org/zap/zaptest/observer uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/zaptest/observer, while a change to org/zap/zaptest/observer can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/zaptest/observer uses a module listed above it, which is the healthy direction.
14→11 org/zap/zaptest/observer uses org/zap/internal✕
- Connections
- 1 pair of types, where a type in org/zap/zaptest/observer uses a type in org/zap/internal.
- The types involved
go.uber.org/zap/zaptest/observer.contextObserver→go.uber.org/zap/internal.LeveledEnabler
- Direction
- org/zap/zaptest/observer uses org/zap/internal, so a change to org/zap/internal can break org/zap/zaptest/observer, while a change to org/zap/zaptest/observer can't break org/zap/internal.
- Position
- Below the diagonal: org/zap/zaptest/observer uses a module listed above it, which is the healthy direction.
15→8 org/zap/zapgrpc uses org/zap/zapcore✕
- Connections
- 4 pairs of types, where a type in org/zap/zapgrpc uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/zapgrpc.Logger→go.uber.org/zap/zapcore.LevelEnablergo.uber.org/zap/zapgrpc.printer→go.uber.org/zap/zapcore.Levelgo.uber.org/zap/zapgrpc.printer→go.uber.org/zap/zapcore.LevelEnablergo.uber.org/zap/zapgrpc.zapgrpc→go.uber.org/zap/zapcore.Level
- Direction
- org/zap/zapgrpc uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/zapgrpc, while a change to org/zap/zapgrpc can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/zapgrpc uses a module listed above it, which is the healthy direction.
15→13 org/zap/zapgrpc uses org/zap✕
- Connections
- 2 pairs of types, where a type in org/zap/zapgrpc uses a type in org/zap.
- The types involved
go.uber.org/zap/zapgrpc.Logger→go.uber.org/zap.SugaredLoggergo.uber.org/zap/zapgrpc.zapgrpc→go.uber.org/zap.Logger
- Direction
- org/zap/zapgrpc uses org/zap, so a change to org/zap can break org/zap/zapgrpc, while a change to org/zap/zapgrpc can't break org/zap.
- Position
- Below the diagonal: org/zap/zapgrpc uses a module listed above it, which is the healthy direction.
16→8 org/zap/zapio uses org/zap/zapcore✕
- Connections
- 2 pairs of types, where a type in org/zap/zapio uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/zapio.Writer→go.uber.org/zap/zapcore.Levelgo.uber.org/zap/zapio.Writer→go.uber.org/zap/zapcore.WriteSyncer
- Direction
- org/zap/zapio uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/zapio, while a change to org/zap/zapio can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/zapio uses a module listed above it, which is the healthy direction.
16→13 org/zap/zapio uses org/zap✕
- Connections
- 2 pairs of types, where a type in org/zap/zapio uses a type in org/zap.
- The types involved
go.uber.org/zap/zapio.Writer→go.uber.org/zap.Loggergo.uber.org/zap/zapio.Writer→go.uber.org/zap.Sink
- Direction
- org/zap/zapio uses org/zap, so a change to org/zap can break org/zap/zapio, while a change to org/zap/zapio can't break org/zap.
- Position
- Below the diagonal: org/zap/zapio uses a module listed above it, which is the healthy direction.
17→8 org/zap/zaptest uses org/zap/zapcore✕
- Connections
- 3 pairs of types, where a type in org/zap/zaptest uses a type in org/zap/zapcore.
- The types involved
go.uber.org/zap/zaptest.TestingWriter→go.uber.org/zap/zapcore.WriteSyncergo.uber.org/zap/zaptest.loggerOptions→go.uber.org/zap/zapcore.LevelEnablergo.uber.org/zap/zaptest.zaptest→go.uber.org/zap/zapcore.LevelEnabler
- Direction
- org/zap/zaptest uses org/zap/zapcore, so a change to org/zap/zapcore can break org/zap/zaptest, while a change to org/zap/zaptest can't break org/zap/zapcore.
- Position
- Below the diagonal: org/zap/zaptest uses a module listed above it, which is the healthy direction.
17→13 org/zap/zaptest uses org/zap✕
- Connections
- 3 pairs of types, where a type in org/zap/zaptest uses a type in org/zap.
- The types involved
go.uber.org/zap/zaptest.loggerOptions→go.uber.org/zap.Optiongo.uber.org/zap/zaptest.zaptest→go.uber.org/zap.Loggergo.uber.org/zap/zaptest.zaptest→go.uber.org/zap.Option
- Direction
- org/zap/zaptest uses org/zap, so a change to org/zap can break org/zap/zaptest, while a change to org/zap/zaptest can't break org/zap.
- Position
- Below the diagonal: org/zap/zaptest 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 | 9 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 5 | Medium |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality — start with readme.go; Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with writer.go (3), encoder.go (2), logger.go (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 readme.go. | +12.1 pts | Low | ADR Quality |
| Resolve the 37 Orphaned file finding(s) in Knowledge Freshness — start with writer.go (3), encoder.go (2), logger.go (2). | +9.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. | +9.9 pts | Medium | Architecture documentation |
| 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. | +1.7 pts | Medium | Documentation (README) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.8 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.8 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 4.4 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| zapcore/encoder.go | 7.3 | Mixed | Explicit Debt: TodoComment |
| zapcore/json_encoder.go | 7.4 | Mixed | Cyclomatic Complexity: jsonEncoder.EncodeEntry (cyclomatic 18) |
| sugar.go | 7.4 | Mixed | Cognitive Complexity: SugaredLogger.sweetenFields (cognitive 19) |
| zapcore/console_encoder.go | 7.8 | Mixed | Cyclomatic Complexity: consoleEncoder.EncodeEntry (cyclomatic 18) |
| logger.go | 7.8 | Mixed | Cyclomatic Complexity: Logger.check (cyclomatic 16) |
| exp/zapslog/handler.go | 8.2 | Near-clean | Explicit Debt: TodoComment |
| field.go | 8.5 | Near-clean | God Classes: FunctionTooLong: zap.Any |
| zapcore/error.go | 8.5 | Near-clean | Code Duplication: Duplicated block (13 lines × 2) |
| internal/readme/readme.go | 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 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 40 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, 64 of 79 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
- 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 READ here — but this repository measures it: a Codecov configuration (.codecov.yml, target 95%) and a coverage step in CI (`codecov/codecov-action`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- 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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (go.mod), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- 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.
- D32 Data Compliance (PII/GDPR) — 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. `array.go`, `exp/zapfield/zapfield.go`, `zapcore/json_encoder.go` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- 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 Go 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 Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- 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.
- X2 Cancellation propagation — 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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 Go 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.
- X27 Collection changed while being enumerated — 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, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go 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.
- X29 Per-element action decided by a fixed element — 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, 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.
- X4 Structured logging — 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, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala or Rust was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- 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 (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
3 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was consoleEncoder.EncodeEntry at 18. A further 2 function(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 zap.Any at 64 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold functions was excluded, so the exclusion is disclosed nowhere in the file itself: field.go (zap.Any at 64), zapcore/field.go (Field.AddTo at 31). 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 3 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with consoleEncoder.EncodeEntry (cyclomatic 18), jsonEncoder.EncodeEntry (cyclomatic 18), Logger.check (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cyclomatic Complexity from 9.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
4 function(s) exceeded the cognitive complexity threshold of 15; the worst was jsonEncoder.EncodeEntry at 24.
What to do
- Bring the 4 bodies over 15 down to 15 or less in Cognitive Complexity — start with jsonEncoder.EncodeEntry (cognitive 24), consoleEncoder.EncodeEntry (cognitive 20), SugaredLogger.sweetenFields (cognitive 19). — 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 4 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with json_encoder.go, sugar.go. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with field.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
1 duplicated block group(s) detected. One further row reports members as variants of one another; it aggregates block groups already counted above and is not itself counted.
What to do
- Resolve the 1 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with sugar.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (13 lines × 2) finding(s) in Code Duplication — start with error.go. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
D6 · Cohesion (LCOM4)
0 of 27 classes have LCOM4 above 3.
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (4 modules): measured (0 flaky).
D12 · Dependency Hygiene
4 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from go.mod and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 17 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's go.mod requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
3 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is config.go. Counted over 41 of the 64 production source files in this repository: 22 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
3 deducted task-comment markers across 8569 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 3 TodoComment finding(s) in Explicit Debt — start with encoder.go (2), handler.go. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 4 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with readme.go. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 2 build units (Go) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
33 % of calls cross a namespace and 16 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 9 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `array.go` (line 148), `exp/zapfield/zapfield.go` (line 30, line 34, line 44), `zapcore/json_encoder.go` (line 509) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 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 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in any ecosystem this repository declares.
D34 · Knowledge Freshness
38 of 42 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is field.go. Counted over 42 of the 64 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 37 Orphaned file finding(s) in Knowledge Freshness — start with writer.go (3), encoder.go (2), logger.go (2). — One of this dimension's main actionable groups (37 recommendation-level).
- Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Most significant orphaned file finding(s) in Knowledge Freshness — start with field.go. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 0 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.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX4 · Dependency direction
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `gomod` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF1 · Benchmark discipline
X3 · Exception handling
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 97% | Exemplary | Solid. |
| Architecture | 93% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 56% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 89% | Strong | Solid. |
| Security | 68% | Checked 4 of 10 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- 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 — 72 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: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- 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
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~13188 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (zapcore), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .go, 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
- 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) — 3 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- 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 project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 1 value object(s)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event-sourced shape(s) (event folds / event-recording aggregates))
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 Go aggregate(s) recording domain events (own events-slice append / raise-record))
- 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
- P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 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
- 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: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Go's `++`, `--` and assignments are STATEMENTS, not expressions, so none of them can appear in a `case` expression or anywhere else in a condition, and a type switch's cases are types. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X23 Unguarded diagnostic materialisation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X26 Unsynchronised callback handoff — not applicable — 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 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
- 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 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Go's type system has no nullable and non-nullable types — every pointer, map, slice and interface is nil-able at every position, there is no switch that turns null checking on, and the compiler produces no nullability warning for an operator to silence. Not a gap in the analyzer and not a finding about your code.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 9 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 16 finding(s)
- TodoComment zapcore/encoder.go:282
- TodoComment zapcore/encoder.go:289
- TodoComment exp/zapslog/handler.go:106
- TooManyMethods: jsonEncoder zapcore/json_encoder.go:54
- TooManyMethods: SugaredLogger sugar.go:55
- consoleEncoder.EncodeEntry (cyclomatic 18) zapcore/console_encoder.go:70
- jsonEncoder.EncodeEntry (cyclomatic 18) zapcore/json_encoder.go:361
- Logger.check (cyclomatic 16) logger.go:322
- jsonEncoder.EncodeEntry (cognitive 24) zapcore/json_encoder.go:361
- consoleEncoder.EncodeEntry (cognitive 20) zapcore/console_encoder.go:70
- SugaredLogger.sweetenFields (cognitive 19) sugar.go:395
- Logger.check (cognitive 16) logger.go:322
- FunctionTooLong: zap.Any field.go:490
- REDACTED
- Edited copy of a member (10 corresponding lines) sugar.go:346
- Duplicated block (13 lines × 2) zapcore/error.go:50
Minor — 50 finding(s)
- Orphaned file zapcore/encoder.go:1
- Orphaned file zapcore/json_encoder.go:1
- Orphaned file sugar.go:1
- Orphaned file logger.go:1
- Orphaned file array.go:1
- Orphaned file zapcore/field.go:1
- Orphaned file zapcore/memory_encoder.go:1
- Orphaned file zapcore/sampler.go:1
- Orphaned file internal/readme/readme.go:1
- Orphaned file zapgrpc/zapgrpc.go:1
- Orphaned file zapcore/level.go:1
- Orphaned file options.go:1
- Orphaned file zapcore/buffered_write_syncer.go:1
- Orphaned file zaptest/observer/observer.go:1
- Orphaned file sink.go:1
- Orphaned file internal/stacktrace/stack.go:1
- Orphaned file global.go:1
- Orphaned file level.go:1
- Orphaned file doc.go:1
- Orphaned file zapcore/console_encoder.go:1
- Orphaned file zaptest/logger.go:1
- Orphaned file zapio/writer.go:1
- Orphaned file buffer/buffer.go:1
- Orphaned file internal/ztest/clock.go:1
- Orphaned file zapcore/error.go:1
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found internal/readme/readme.go:22
- Projects may be oversized for their cohesion
- Concentrated knowledge decay
- Most significant orphaned file field.go:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- Dependabot does not watch gomod REDACTED:2
Minor — 4 finding(s)
- Outdated: github.com/rs/zerolog
- Outdated: github.com/sirupsen/logrus
- Outdated: go.uber.org/multierr
- Outdated: go.yaml.in/yaml/v3
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-dde0328caf1d41138c905e2b92424d57/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-dde0328caf1d41138c905e2b92424d57/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 . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-af0c4d5bf679473888dd0a053e4edbef | 0 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 3 file(s) — `array.go`, `exp/zapfield/zapfield.go`, `zapcore/json_encoder.go` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-af0c4d5bf679473888dd0a053e4edbef | 0 | artifacts/raw/osv-scanner.json |