Executive summary
ActiveLogin/ActiveLogin.Identity falls short of our standard for production because nine files are no longer known to anyone active in the project and we found no recorded design decisions and no architecture document or diagram. It scores 63 out of 100 and is rated Adequate, and 11 of its 12 critical findings are security problems.
Maturity, at 50, is the weakest lens and counts most in the score. The best first step is having someone learn and document the nine files no active contributor knows, worth about 13 points. Replacing the two exposed passwords or keys and switching the old ones off comes next, worth about 6 points. Raising Maturity to 70 would lift the score to about 72.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two passwords or keys in the code and two in the code's history are open to anyone who can read the repository. Pinning each tool to an exact version and replacing each exposed password or key would close both risks. The set of compiler warnings switched off in a project needs turning back on in the build file.
The product code is 1,796 lines, about €4,800 to rebuild.
If Maturity rose from 50 to 70, the lowest score rated Strong, the score would rise from 63 to about 72.
Rebuild cost: about €4,800 · Estimate
| Cost to rebuild | €1,600 to €8,100, for 27 to 85 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Low, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.9 at a score of 63. 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 | Very small: 1,796 lines of product code |
| Comment lines | The estimate prices 1,765 lines. Comment lines count towards the size of 1,796 lines but aren't priced as work. |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 Swedish | 2 Swedish.AspNetCore.Validation | 3 Swedish.Shared.Hints | 4 Swedish.Shared.Hints.Option | 5 Swedish.BirthNumberModule | 6 Swedish.ChecksumModule | 7 Swedish.CoordinationDayModule | 8 Swedish.CoordinationMonthModule | 9 Swedish.CoordinationNumberModule | 10 Swedish.DayModule | 11 Swedish.Extensions | 12 Swedish.Extensions.CoordNum | 13 Swedish.Extensions.IndividualNum | 14 Swedish.Extensions.Pin | 15 Swedish.IndividualIdentityNumberModule | 16 Swedish.IndividualNumberModule | 17 Swedish.MonthModule | 18 Swedish.Parse | 19 Swedish.PersonalIdentityNumberModule | 20 Swedish.Shared | 21 Swedish.Shared.Hints.AgeResultModule | 22 Swedish.YearModule | 23 Swedish.Parse.Helpers | 24 Swedish.Parse.PinType |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 Swedish | ||||||||||||||||||||||||
| 2 Swedish.AspNetCore.Validation | ||||||||||||||||||||||||
| 3 Swedish.Shared.Hints | ||||||||||||||||||||||||
| 4 Swedish.Shared.Hints.Option | ||||||||||||||||||||||||
| 5 Swedish.BirthNumberModule | 1 | |||||||||||||||||||||||
| 6 Swedish.ChecksumModule | 8 | |||||||||||||||||||||||
| 7 Swedish.CoordinationDayModule | 3 | |||||||||||||||||||||||
| 8 Swedish.CoordinationMonthModule | 1 | |||||||||||||||||||||||
| 9 Swedish.CoordinationNumberModule | 2 | |||||||||||||||||||||||
| 10 Swedish.DayModule | 3 | |||||||||||||||||||||||
| 11 Swedish.Extensions | 6 | |||||||||||||||||||||||
| 12 Swedish.Extensions.CoordNum | 2 | |||||||||||||||||||||||
| 13 Swedish.Extensions.IndividualNum | 1 | |||||||||||||||||||||||
| 14 Swedish.Extensions.Pin | 2 | |||||||||||||||||||||||
| 15 Swedish.IndividualIdentityNumberModule | 1 | |||||||||||||||||||||||
| 16 Swedish.IndividualNumberModule | 1 | |||||||||||||||||||||||
| 17 Swedish.MonthModule | 1 | |||||||||||||||||||||||
| 18 Swedish.Parse | 2 | |||||||||||||||||||||||
| 19 Swedish.PersonalIdentityNumberModule | 2 | |||||||||||||||||||||||
| 20 Swedish.Shared | 1 | |||||||||||||||||||||||
| 21 Swedish.Shared.Hints.AgeResultModule | 1 | |||||||||||||||||||||||
| 22 Swedish.YearModule | 1 | |||||||||||||||||||||||
| 23 Swedish.Parse.Helpers | 2 | 1 | ||||||||||||||||||||||
| 24 Swedish.Parse.PinType | 1 |
5→1 Swedish.BirthNumberModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.BirthNumberModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.BirthNumberModule.BirthNumberModule→ActiveLogin.Identity.Swedish.BirthNumber
- Direction
- Swedish.BirthNumberModule uses Swedish, so a change to Swedish can break Swedish.BirthNumberModule, while a change to Swedish.BirthNumberModule can't break Swedish.
- Position
- Below the diagonal: Swedish.BirthNumberModule uses a module listed above it, which is the healthy direction.
6→1 Swedish.ChecksumModule uses Swedish✕
- Connections
- 8 pairs of types, where a type in Swedish.ChecksumModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.BirthNumberActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.ChecksumActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.CoordinationDayActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.CoordinationMonthActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.DayActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.IndividualNumberActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.MonthActiveLogin.Identity.Swedish.ChecksumModule.ChecksumModule→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.ChecksumModule uses Swedish, so a change to Swedish can break Swedish.ChecksumModule, while a change to Swedish.ChecksumModule can't break Swedish.
- Position
- Below the diagonal: Swedish.ChecksumModule uses a module listed above it, which is the healthy direction.
7→1 Swedish.CoordinationDayModule uses Swedish✕
- Connections
- 3 pairs of types, where a type in Swedish.CoordinationDayModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.CoordinationDayModule.CoordinationDayModule→ActiveLogin.Identity.Swedish.CoordinationDayActiveLogin.Identity.Swedish.CoordinationDayModule.CoordinationDayModule→ActiveLogin.Identity.Swedish.CoordinationMonthActiveLogin.Identity.Swedish.CoordinationDayModule.CoordinationDayModule→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.CoordinationDayModule uses Swedish, so a change to Swedish can break Swedish.CoordinationDayModule, while a change to Swedish.CoordinationDayModule can't break Swedish.
- Position
- Below the diagonal: Swedish.CoordinationDayModule uses a module listed above it, which is the healthy direction.
8→1 Swedish.CoordinationMonthModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.CoordinationMonthModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.CoordinationMonthModule.CoordinationMonthModule→ActiveLogin.Identity.Swedish.CoordinationMonth
- Direction
- Swedish.CoordinationMonthModule uses Swedish, so a change to Swedish can break Swedish.CoordinationMonthModule, while a change to Swedish.CoordinationMonthModule can't break Swedish.
- Position
- Below the diagonal: Swedish.CoordinationMonthModule uses a module listed above it, which is the healthy direction.
9→1 Swedish.CoordinationNumberModule uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.CoordinationNumberModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.CoordinationNumberModule.CoordinationNumberModule→ActiveLogin.Identity.Swedish.CoordinationNumberInternalActiveLogin.Identity.Swedish.CoordinationNumberModule.CoordinationNumberModule→ActiveLogin.Identity.Swedish.StrictModeInternal
- Direction
- Swedish.CoordinationNumberModule uses Swedish, so a change to Swedish can break Swedish.CoordinationNumberModule, while a change to Swedish.CoordinationNumberModule can't break Swedish.
- Position
- Below the diagonal: Swedish.CoordinationNumberModule uses a module listed above it, which is the healthy direction.
10→1 Swedish.DayModule uses Swedish✕
- Connections
- 3 pairs of types, where a type in Swedish.DayModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.DayModule.DayModule→ActiveLogin.Identity.Swedish.DayActiveLogin.Identity.Swedish.DayModule.DayModule→ActiveLogin.Identity.Swedish.MonthActiveLogin.Identity.Swedish.DayModule.DayModule→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.DayModule uses Swedish, so a change to Swedish can break Swedish.DayModule, while a change to Swedish.DayModule can't break Swedish.
- Position
- Below the diagonal: Swedish.DayModule uses a module listed above it, which is the healthy direction.
11→1 Swedish.Extensions uses Swedish✕
- Connections
- 6 pairs of types, where a type in Swedish.Extensions uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Extensions.CoordinationNumberHintExtensions→ActiveLogin.Identity.Swedish.CoordinationNumberActiveLogin.Identity.Swedish.Extensions.CoordinationNumberHintExtensions→ActiveLogin.Identity.Swedish.GenderActiveLogin.Identity.Swedish.Extensions.IndividualIdentityNumberHintExtensions→ActiveLogin.Identity.Swedish.GenderActiveLogin.Identity.Swedish.Extensions.IndividualIdentityNumberHintExtensions→ActiveLogin.Identity.Swedish.IndividualIdentityNumberActiveLogin.Identity.Swedish.Extensions.PersonalIdentityNumberHintExtensions→ActiveLogin.Identity.Swedish.GenderActiveLogin.Identity.Swedish.Extensions.PersonalIdentityNumberHintExtensions→ActiveLogin.Identity.Swedish.PersonalIdentityNumber
- Direction
- Swedish.Extensions uses Swedish, so a change to Swedish can break Swedish.Extensions, while a change to Swedish.Extensions can't break Swedish.
- Position
- Below the diagonal: Swedish.Extensions uses a module listed above it, which is the healthy direction.
12→1 Swedish.Extensions.CoordNum uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.Extensions.CoordNum uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Extensions.CoordNum.CoordNum→ActiveLogin.Identity.Swedish.CoordinationNumberInternalActiveLogin.Identity.Swedish.Extensions.CoordNum.CoordNum→ActiveLogin.Identity.Swedish.Gender
- Direction
- Swedish.Extensions.CoordNum uses Swedish, so a change to Swedish can break Swedish.Extensions.CoordNum, while a change to Swedish.Extensions.CoordNum can't break Swedish.
- Position
- Below the diagonal: Swedish.Extensions.CoordNum uses a module listed above it, which is the healthy direction.
13→1 Swedish.Extensions.IndividualNum uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.Extensions.IndividualNum uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Extensions.IndividualNum.IndividualNum→ActiveLogin.Identity.Swedish.IndividualIdentityNumberInternal
- Direction
- Swedish.Extensions.IndividualNum uses Swedish, so a change to Swedish can break Swedish.Extensions.IndividualNum, while a change to Swedish.Extensions.IndividualNum can't break Swedish.
- Position
- Below the diagonal: Swedish.Extensions.IndividualNum uses a module listed above it, which is the healthy direction.
14→1 Swedish.Extensions.Pin uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.Extensions.Pin uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Extensions.Pin.Pin→ActiveLogin.Identity.Swedish.GenderActiveLogin.Identity.Swedish.Extensions.Pin.Pin→ActiveLogin.Identity.Swedish.PersonalIdentityNumberInternal
- Direction
- Swedish.Extensions.Pin uses Swedish, so a change to Swedish can break Swedish.Extensions.Pin, while a change to Swedish.Extensions.Pin can't break Swedish.
- Position
- Below the diagonal: Swedish.Extensions.Pin uses a module listed above it, which is the healthy direction.
15→1 Swedish.IndividualIdentityNumberModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.IndividualIdentityNumberModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.IndividualIdentityNumberModule.IndividualIdentityNumberModule→ActiveLogin.Identity.Swedish.IndividualIdentityNumberInternal
- Direction
- Swedish.IndividualIdentityNumberModule uses Swedish, so a change to Swedish can break Swedish.IndividualIdentityNumberModule, while a change to Swedish.IndividualIdentityNumberModule can't break Swedish.
- Position
- Below the diagonal: Swedish.IndividualIdentityNumberModule uses a module listed above it, which is the healthy direction.
16→1 Swedish.IndividualNumberModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.IndividualNumberModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.IndividualNumberModule.IndividualNumberModule→ActiveLogin.Identity.Swedish.IndividualNumber
- Direction
- Swedish.IndividualNumberModule uses Swedish, so a change to Swedish can break Swedish.IndividualNumberModule, while a change to Swedish.IndividualNumberModule can't break Swedish.
- Position
- Below the diagonal: Swedish.IndividualNumberModule uses a module listed above it, which is the healthy direction.
17→1 Swedish.MonthModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.MonthModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.MonthModule.MonthModule→ActiveLogin.Identity.Swedish.Month
- Direction
- Swedish.MonthModule uses Swedish, so a change to Swedish can break Swedish.MonthModule, while a change to Swedish.MonthModule can't break Swedish.
- Position
- Below the diagonal: Swedish.MonthModule uses a module listed above it, which is the healthy direction.
18→1 Swedish.Parse uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.Parse uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Parse.Parse→ActiveLogin.Identity.Swedish.StrictModeInternalActiveLogin.Identity.Swedish.Parse.Parse→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.Parse uses Swedish, so a change to Swedish can break Swedish.Parse, while a change to Swedish.Parse can't break Swedish.
- Position
- Below the diagonal: Swedish.Parse uses a module listed above it, which is the healthy direction.
19→1 Swedish.PersonalIdentityNumberModule uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.PersonalIdentityNumberModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.PersonalIdentityNumberModule.PersonalIdentityNumberModule→ActiveLogin.Identity.Swedish.PersonalIdentityNumberInternalActiveLogin.Identity.Swedish.PersonalIdentityNumberModule.PersonalIdentityNumberModule→ActiveLogin.Identity.Swedish.StrictModeInternal
- Direction
- Swedish.PersonalIdentityNumberModule uses Swedish, so a change to Swedish can break Swedish.PersonalIdentityNumberModule, while a change to Swedish.PersonalIdentityNumberModule can't break Swedish.
- Position
- Below the diagonal: Swedish.PersonalIdentityNumberModule uses a module listed above it, which is the healthy direction.
20→1 Swedish.Shared uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.Shared uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Shared.Shared→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.Shared uses Swedish, so a change to Swedish can break Swedish.Shared, while a change to Swedish.Shared can't break Swedish.
- Position
- Below the diagonal: Swedish.Shared uses a module listed above it, which is the healthy direction.
21→3 Swedish.Shared.Hints.AgeResultModule uses Swedish.Shared.Hints✕
- Connections
- 1 pair of types, where a type in Swedish.Shared.Hints.AgeResultModule uses a type in Swedish.Shared.Hints.
- The types involved
ActiveLogin.Identity.Swedish.Shared.Hints.AgeResultModule.AgeResultModule→ActiveLogin.Identity.Swedish.Shared.Hints.AgeResult
- Direction
- Swedish.Shared.Hints.AgeResultModule uses Swedish.Shared.Hints, so a change to Swedish.Shared.Hints can break Swedish.Shared.Hints.AgeResultModule, while a change to Swedish.Shared.Hints.AgeResultModule can't break Swedish.Shared.Hints.
- Position
- Below the diagonal: Swedish.Shared.Hints.AgeResultModule uses a module listed above it, which is the healthy direction.
22→1 Swedish.YearModule uses Swedish✕
- Connections
- 1 pair of types, where a type in Swedish.YearModule uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.YearModule.YearModule→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.YearModule uses Swedish, so a change to Swedish can break Swedish.YearModule, while a change to Swedish.YearModule can't break Swedish.
- Position
- Below the diagonal: Swedish.YearModule uses a module listed above it, which is the healthy direction.
23→1 Swedish.Parse.Helpers uses Swedish✕
- Connections
- 2 pairs of types, where a type in Swedish.Parse.Helpers uses a type in Swedish.
- The types involved
ActiveLogin.Identity.Swedish.Parse.Helpers.Helpers→ActiveLogin.Identity.Swedish.StrictModeInternalActiveLogin.Identity.Swedish.Parse.Helpers.Helpers→ActiveLogin.Identity.Swedish.Year
- Direction
- Swedish.Parse.Helpers uses Swedish, so a change to Swedish can break Swedish.Parse.Helpers, while a change to Swedish.Parse.Helpers can't break Swedish.
- Position
- Below the diagonal: Swedish.Parse.Helpers uses a module listed above it, which is the healthy direction.
23→18 Swedish.Parse.Helpers uses Swedish.Parse✕
- Connections
- 1 pair of types, where a type in Swedish.Parse.Helpers uses a type in Swedish.Parse.
- The types involved
ActiveLogin.Identity.Swedish.Parse.Helpers.Helpers→ActiveLogin.Identity.Swedish.Parse.PinType`1
- Direction
- Swedish.Parse.Helpers uses Swedish.Parse, so a change to Swedish.Parse can break Swedish.Parse.Helpers, while a change to Swedish.Parse.Helpers can't break Swedish.Parse.
- Position
- Below the diagonal: Swedish.Parse.Helpers uses a module listed above it, which is the healthy direction.
24→18 Swedish.Parse.PinType uses Swedish.Parse✕
- Connections
- 1 pair of types, where a type in Swedish.Parse.PinType uses a type in Swedish.Parse.
- The types involved
ActiveLogin.Identity.Swedish.Parse.PinType.PinType→ActiveLogin.Identity.Swedish.Parse.PinType`1
- Direction
- Swedish.Parse.PinType uses Swedish.Parse, so a change to Swedish.Parse can break Swedish.Parse.PinType, while a change to Swedish.Parse.PinType can't break Swedish.Parse.
- Position
- Below the diagonal: Swedish.Parse.PinType 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 7 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A07:2025 — Authentication Failures | 4 | High / Critical |
Roadmap
Top priorities: Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with PersonalIdentityNumber.fs, CoordinationNumber.fs, IndividualIdentityNumber.fs; 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; Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 9 Orphaned file finding(s) in Knowledge Freshness — start with PersonalIdentityNumber.fs, CoordinationNumber.fs, IndividualIdentityNumber.fs. | +12.8 pts | Low | Knowledge Freshness |
| Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). | +5.9 pts | Low | Secret Scanning |
| 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. | +10.2 pts | Medium | Architecture documentation |
| Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with ActiveLogin.Identity.Swedish.Test.csproj, ActiveLogin.Identity.Swedish.AspNetCore.Test.csproj. | +2.5 pts | Low | Dependency Hygiene |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +2.4 pts | Low | Knowledge Freshness |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.0 pts | Medium | Release Hygiene |
| Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). | +0.4 pts | Low | Secrets (history) |
| Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with PersonalIdentityNumber_ToString.cs. | +0.4 pts | Low | Explicit Debt |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | Secret Scanning: Leaked secret: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.5 | Mixed | Explicit Debt: NoWarnInCsproj |
| test/ActiveLogin.Identity.Swedish.Test/PersonalIdentityNumber_ToString.cs | 8.2 | Near-clean | Explicit Debt: CommentedOutCode |
| test/ActiveLogin.Identity.Swedish.Test/ActiveLogin.Identity.Swedish.Test.csproj | 8.5 | Near-clean | Dependency Hygiene: Deprecated: xunit |
| test/ActiveLogin.Identity.Swedish.AspNetCore.Test/ActiveLogin.Identity.Swedish.AspNetCore.Test.csproj | 8.5 | Near-clean | Dependency Hygiene: Deprecated: xunit |
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 38 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 — 38 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, 27 of 46 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — 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. Code Duplication couldn't be assessed within its 5-minute budget on a solution this large — not included in this run.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .cs, .fs, and our analyzer cannot run the .fs test suite(s) — so no coverage was collected for the repository as a whole. The .NET half may well have built and run; what is missing is a coverage figure that covers the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test 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. The 92 test(s) behind this row are the ones the C# collector could read, and this repository also carries at least 20 test source file(s) (.fs) that it cannot: it parses C# syntax and matches C# test attributes, so a vitest/jest/JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 9 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 3 of the 16 production source files in this repository: 7 are under the ~2,400-byte size floor this dimension measures over, and the remaining 6 have no attributable history left to measure.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'test/ActiveLogin.Identity.Swedish.Test/ActiveLogin.Identity.Swedish.Test.csproj' with message: The URL of repository remote 'origin' is invalid: ''.
- D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 2 deducted marker(s) and the 0.5/KLoC density on this row were taken over this repository's .NET projects ALONE: .fs (1,500 lines, 84% of production source) went unread, because every marker collector on this path is reached through a C# workspace. D17's marker collectors need a compiler we do not have for that language, so none of its nine marker kinds were read there. The debt in that source is UNMEASURED — its absence from the score above is a gap in this analyzer's language coverage, not a finding that the code carries none.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — 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. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- 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
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
4 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 92 tests. Measured on the C# suite only — at least 20 test source file(s) (.fs) went unread, so its test quality is unmeasured and is not in these counts.
D11 · Test Reliability
0 flaky across 1 measured tier(s). other: measured (0 flaky).
D12 · Dependency Hygiene
9 outdated, 0 vulnerable, 1 deprecated packages.
What to do
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with ActiveLogin.Identity.Swedish.Test.csproj, ActiveLogin.Identity.Swedish.AspNetCore.Test.csproj. — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
2 secret(s) detected.
What to do
- Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D14 · License Compliance
0 of 165 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 12 direct `PackageReference`(s), and 146 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
2 deducted debt markers + unmeasured dead symbols across 296 LoC in the .NET projects (0.5/KLoC) → score 8.9. Dead code not measured: the solution did not load cleanly, so the reference search was skipped. Measured on the .NET source only: .fs (84% of production source) was not read, and carries at least 0 uncounted task marker(s) in 0 file(s).
What to do
- Resolve the 1 NoWarnInCsproj finding(s) in Explicit Debt — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 CommentedOutCode finding(s) in Explicit Debt — start with PersonalIdentityNumber_ToString.cs. — One of this dimension's main actionable groups (1 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 2 unit(s).
D26 · Project Cohesion
0 of 4 projects flagged as possibly oversized/incoherent.
D27 · Navigability
90 % of calls cross a namespace and 0 % go through an interface, but 99 % 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)
2 finding(s): 0 critical, 2 high, 0 medium, 0 low.
What to do
- Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
D29 · Static Analysis (SAST)
7 finding(s): 0 critical, 7 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- 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
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
9 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/ActiveLogin.Identity.Swedish/PersonalIdentityNumber.fs. Counted over 9 of the 16 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 9 Orphaned file finding(s) in Knowledge Freshness — start with PersonalIdentityNumber.fs, CoordinationNumber.fs, IndividualIdentityNumber.fs. — One of this dimension's main actionable groups (9 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 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 — start with REDACTED. — 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
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 9 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
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX8 · Test isolation
GD1 · Unfinished & placeholder code
M1 · Documentation (README)
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
P3 · Security & performance tooling
- `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:43
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
X5 · Nullable reference types
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 95% | Exemplary | Solid. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 50% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 65% | Adequate — gated by D13 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 76% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 77 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 — no DI registrations detected
- AX2 Stateful singletons — no singleton implementations detected
- AX6 Interface segregation — no public interfaces
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution, but this repository's production source is mostly .fs, which the C#/VB workspace does not load — the projects that loaded are an immaterial minority, so solution shape was not assessed for this repository. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (837 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
- D23 Boundary Type-Coupling — small single-context codebase (1,796 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .fs source were not judged.
- 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) — 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.
- D4 Code Duplication — Code Duplication not included (time budget)
- 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.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 11 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (2 with fewer than two methods, 6 stateless, 3 stub-like), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — analyzer environment
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (48 value object(s))
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- IC1 Incompleteness & stubs — IC1 reached only 16% of this repository's production lines — fsharp (1,500 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repo is a library, not a deployed service — it has no process to operate, so production observability (structured logging, tracing/metrics, health checks) is N/A. A library may log via an injected ILogger, but the absence of operational telemetry is not a defect here. If it grows a host (web API, worker), the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — this isn't a service/API/worker
- P8 Schema migrations — no EF Core usage detected
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Performance is assessed only for perf-relevant repos — a packaged library, one that ships benchmarks, or one already using allocation-aware APIs. This repo isn't one, so the Performance lens is not applicable and is excluded from the score.
- S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 16% of this repository's production lines — fsharp (1,500 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no async method does work a token could cancel
- X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — X27 reached only 16% of this repository's production lines — fsharp (1,500 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X4 Structured logging — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 12 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- NoWarnInCsproj REDACTED:8
Serious — 7 finding(s)
- Deprecated: xunit test/ActiveLogin.Identity.Swedish.Test/ActiveLogin.Identity.Swedish.Test.csproj:13
- Deprecated: xunit test/ActiveLogin.Identity.Swedish.AspNetCore.Test/ActiveLogin.Identity.Swedish.AspNetCore.Test.csproj:13
- CommentedOutCode test/ActiveLogin.Identity.Swedish.Test/PersonalIdentityNumber_ToString.cs:19
- REDACTED
- REDACTED
- REDACTED
- NuGet dependencies are not locked
Minor — 18 finding(s)
- Orphaned file src/ActiveLogin.Identity.Swedish/PersonalIdentityNumber.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish/CoordinationNumber.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish/IndividualIdentityNumber.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish/Types.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish/Parse.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish.TestData/TestData.fs:1
- Orphaned file src/ActiveLogin.Identity.Swedish.AspNetCore/Validation/PersonalIdentityNumberAttribute.cs:1
- Orphaned file src/ActiveLogin.Identity.Swedish.AspNetCore/Validation/CoordinationNumberAttribute.cs:1
- Orphaned file src/ActiveLogin.Identity.Swedish/CoordinationNumberHints.fs:1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No architecture diagram/doc
- No dependency-update automation REDACTED:43
- No changelog
Minor — 9 finding(s)
- Outdated: AltCover
- Outdated: Microsoft.NET.Test.Sdk
- Outdated: xunit.runner.visualstudio
- Outdated: Microsoft.SourceLink.GitHub
- Outdated: FSharp.Core
- Outdated: Expecto
- Outdated: Expecto.FsCheck
- Outdated: FsCheck
- Outdated: YoloDev.Expecto.TestSdk
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-3a7239fcf093432dab208a3af695a7ce/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-3a7239fcf093432dab208a3af695a7ce/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 . | 7 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | dotnet | — | dotnet list ActiveLogin.Identity.sln package --vulnerable --include-transitive --format json | 1 | artifacts/raw/dotnet-vulnerable.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| 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-15269011a34e4ac48380c40cc1310066 | 0 | artifacts/raw/osv-scanner.json |