Public report of BBSR-GEG-Portal/druckapplication-fuer-energieausweise, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 02:59 UTC · Survey ID cd_22a0dad6f51248fc8fcc96f4d9b4619c

BBSR-GEG-Portal/druckapplication-fuer-energieausweise

Measured 15 November 2026, 02:59 UTC, at code version 6b5b6d1

CAI score 41out of 100 Weak
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A medium codebase: 27,676 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 12

Findings by how serious they are

6 critical 117 serious 10 minor

41 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 02:59 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

30of 30 dimensions measured by tools.
125of 133 findings point to an exact file and line, so you can open each one in the code. The other 8 concern the repository as a whole, such as missing documentation.
30dimensions across 5 lenses, read from 27,676 lines of product code in 1 project.
Chapters

Executive summary

BBSR-GEG-Portal/druckapplication-fuer-energieausweise falls short of our standard for production because the project has no automated tests and we found no working pipeline that builds or tests changes to the code. It scores 41 out of 100 and is rated Weak, and none of its six critical findings concern security.

Production Readiness, at 12, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 7 points. Adding automated tests would lift Production Readiness itself, worth about 28 points. Raising Production Readiness to 70 would lift the score to about 66.

The project has no automated tests, so a change can break it without warning. Five errors are caught and ignored, so failures can go unnoticed. Adding automated tests and handling or logging the ignored errors would close both risks.

The product code is 27,676 lines, about €25,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 12 · counts for 47%Maturity 55 · counts for 26%Architecture 74 · counts for 14%Code Health 81 · counts for 8%Security and Compliance 100 · counts for 4%

If Production Readiness rose from 12 to 70, the lowest score rated Strong, the score would rise from 41 to about 66.

Code composition: what the lines of code are
Product code 100%
New since the last survey: 13 findings

These 13 critical or serious findings weren't in the previous survey, on 29 October 2026.

  • Code Duplication · Edited copy of a member (142 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb
  • Code Duplication · Edited copy of a member (31 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
  • Code Duplication · Edited copy of a member (28 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb
  • Code Duplication · Edited copy of a member (84 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb
  • Code Duplication · Edited copy of a member (52 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb
  • Code Duplication · Edited copy of a member (48 corresponding lines) VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb
  • Code Duplication · Edited copy of a member (13 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
  • Code Duplication · Edited copy of a member (11 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
  • Code Duplication · Edited copy of a member (15 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
  • Code Duplication · Edited copy of a member (23 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Webdienst.vb
  • Code Duplication · Edited copy of a member (4 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
  • Code Duplication · Edited copies of one member (8 members, 28+ corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb
  • Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Rebuild cost: about €25,000 · Estimate
Cost to rebuild€8,200 to €41,000, for 137 to 436 hours of work, about 0.2 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 41. 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.
SizeMedium: 27,676 lines of product code
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BBSR-Energieausweis.vbproj.
Raises the score by about 7 points · Low effort · ADR Quality
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 28 points · High effort · Code Coverage
3
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.
Raises the score by about 6 points · Medium effort · Architecture documentation

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €25,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 12 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 14% on every change. The history of the code shows how much it changes: about 1,823 lines over the last 90 days, which is about 7,393 lines a year. At that pace, the extra work comes to an estimated 1.1 to 6.8 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

4 modules, with 1 dependency between them. Every module uses only modules listed above it, so there are no loops.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 BBSR_Energieausweis.DynaPDF2 BBSR_Energieausweis.My3 Microsoft.VisualBasic4 BBSR_Energieausweis
1 BBSR_Energieausweis.DynaPDF
2 BBSR_Energieausweis.My
3 Microsoft.VisualBasic
4 BBSR_Energieausweis3
Uses a module listed above itPart of a loopThe module itself
1 BBSR_Energieausweis.DynaPDF2 BBSR_Energieausweis.My3 Microsoft.VisualBasic4 BBSR_EnergieausweisBBSR_Energieausweis.DynaPDF1BBSR_Energieausweis.My2Microsoft.VisualBasic3BBSR_Energieausweis43

At a glance — Code Health · 81% · Strong ·

At a glance — Architecture · 74% · Adequate · gated by AX5 ·

At a glance — Maturity · 55% · Adequate · gated by M2 ·

At a glance — Readiness · 12% · Critical · gated by D8, P1, P2, P3 ·

At a glance — Security · 100% · Checked 2 of 9 ·

Roadmap

Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BBSR-Energieausweis.vbproj; 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.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BBSR-Energieausweis.vbproj.+7.4 ptsLowADR Quality
Resolve the 1 No automated tests finding(s) in Code Coverage.+27.9 ptsHighCode Coverage
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+6.1 ptsMediumArchitecture documentation
Add a CI workflow that builds and runs the test suite on every push/PR.+5.3 ptsMediumCI/CD gates
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.+5.3 ptsMediumObservability
Resolve the 5 OnErrorResumeSwallow finding(s) in Explicit Debt — start with Modul_PDF.vb (5).+1.5 ptsLowExplicit Debt
Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.+2.4 ptsMediumArchitecture & structure
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.+2.3 ptsMediumRelease Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 19 files carrying findings, judged against the Production bar: 5% slop · 74% mixed · 21% near-clean.

FileScoreBandWorst signal
VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb1.4SlopExplicit Debt: OnErrorResumeSwallow
VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb6.6MixedCognitive Complexity: Modul_Berechnungen.Zusammenstellung_NWB_Verbrauchserfassung (cognitive 25)
VB-NET-BBSR-Drucktool/Module/Modul_XML.vb7.0MixedCyclomatic Complexity: Modul_XML.Datensatz_Lesen (cyclomatic 561)
VB-NET-BBSR-Drucktool/Module/Modul_Image.vb7.0MixedCyclomatic Complexity: Modul_Image.Image_Diagram_NWB_Energieaufteilung (cyclomatic 18)
VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb7.0MixedCyclomatic Complexity: Fenster_Start.Energeiausweis_erstellen (cyclomatic 25)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cyclomatic 214)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cyclomatic 158)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cyclomatic 158)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cyclomatic 141)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cyclomatic 139)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen (cyclomatic 103)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen (cyclomatic 100)
VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb7.1MixedCyclomatic Complexity: Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen (cyclomatic 100)
VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb7.2MixedCyclomatic Complexity: Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen (cyclomatic 24)
VB-NET-BBSR-Drucktool/Module/Modul_Variablen.vb7.8MixedGod Classes: ClassTooLong: Modul_Variablen
VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_Funktionen.vb8.5Near-cleanCognitive Complexity: Modul_Ablauf_Funktionen.Testdaten_anlegen (cognitive 19)
VB-NET-BBSR-Drucktool/Module/Modul_Webdienst.vb8.5Near-cleanCode Duplication: Edited copy of a member (23 corresponding lines)
VB-NET-BBSR-Drucktool/VB-NET-BBSR-Drucktool.sln8.5Near-cleanSolution Shape: Solution references a project that does not exist
VB-NET-BBSR-Drucktool/BBSR-Energieausweis.vbproj9.5Near-cleanADR Quality: No ADRs found

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 6

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.

Serious — 117

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.

Minor — 10

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 41

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 30 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 30 dimensions across the health lenses
D1D2D3D4D5D8D13D15D17D18D20D24D26D27D28D29D35AX10AX3AX4AX5GD1M1M2M3M4P1P2P3P6

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 125 of 133 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1dd25-33f2-762e-b0db-0da4942f6706.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `dotnet list package` did not return usable output (restore or query failed); no outdated/vulnerable/deprecated data to assess. The tool said: `dotnet list package` exited 1 with no output.
  • D14 License Compliance — 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. License scan produced no result — the tool ran but wrote no JSON report (no package reference resolved); the offline NuGet fallback resolved nothing.
  • D15 Churn × Complexity Hotspots — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 6 commit(s), too few for a reliable trend signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
  • 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. Too few commits for a meaningful bus factor (6 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
  • 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: Project file not found: 'VB-NET-BBSR-Webservice/BBSR-Webservice/BBSR-Webservice.vbproj'.
  • D18 Solution Shape — 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 build did not finish within its budget on this run; structural metrics are reported, build/warning status is unknown.
  • 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 naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • 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.
  • D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (6 commit(s) sampled).
  • D35 Change Coupling — measured, with a gap in what it reached — 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. Git history depth insufficient — this repository has 6 commit(s), too few for a reliable change-coupling signal. The clone is complete, so there is no deeper history to fetch: the signal returns as the project accumulates history.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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.
  • PF3 Async & latency hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. No function of a language this check models was read, so there was no async code to examine. That is a limit of the analyzer on this repository, not a finding about it.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X10 Duplicated predicate — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X14 Bypassable address classification — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X15 Unvalidated length from an untrusted reader — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X20 Mistyped argument 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X21 Side-effecting pattern 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X26 Unsynchronised callback handoff — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X30 Support guard that admits what it rejects — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X32 Type resolved by simple name across every loaded assembly — 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 implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • 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 is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is implemented over the C# syntax tree, and no C# was loaded on this run, 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.
  • X6 Hand-rolled structured-format parsing — 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 Python, JavaScript/TypeScript, Go, Java/Kotlin/Scala, Ruby, PHP, Rust, Swift, Erlang, Elixir and Dart source only, and no C# was loaded and none of those languages 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.
  • X7 Silent fallback defaults — 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#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart syntax only, and no C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift or Dart was loaded for 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
  • 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.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • 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").
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • 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 Complexity4.8 / 10Weak✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.8 / 10 · rule-coverage 100% · ceiling Prevented

17 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Modul_XML.Datensatz_Lesen at 561. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Modul_Ablauf_ohne_Oberflaeche.Main at 18 — they are counted neither in the figure above nor in this dimension's score.

Modul_XML.Datensatz_Lesen (cyclomatic 561)VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:792
Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cyclomatic 214)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb:27
Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cyclomatic 158)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb:25
Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cyclomatic 158)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb:25
Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cyclomatic 141)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb:25

+ 12 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 240 down to 240 or less in Cyclomatic Complexity — start with Modul_XML.Datensatz_Lesen (cyclomatic 561). — Refactoring it lifts Cyclomatic Complexity from 4.8 to about 5.7/10.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity4.1 / 10Weak✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.1 / 10 · rule-coverage 100% · ceiling Prevented

23 method(s) exceeded the cognitive complexity threshold of 15; the worst was Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen at 733.

Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cognitive 733)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb:27
Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cognitive 491)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb:25
Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cognitive 491)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb:25
Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cognitive 433)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb:25
Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cognitive 432)VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb:25

+ 18 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 11 bodies over 30 down to 30 or less in Cognitive Complexity — start with Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cognitive 733), Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cognitive 491), Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cognitive 491). — 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 11 together lifts Cognitive Complexity from 4.1 to about 7.4/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes7.6 / 10Strong✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Prevented

42 god class(es) detected.

MethodTooLong: Modul_XML.Datensatz_Lesen · ×15VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:792
FileTooLong: Module/Modul_PDF.vb · ×13VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb
ClassTooLong: Modul_XML · ×12VB-NET-BBSR-Drucktool/Module/Modul_XML.vb
TooManyMethods: Modul_PDF · ×2VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb

What to do

  1. Resolve the 15 MethodTooLong finding(s) in God Classes — start with Modul_XML.vb (3), Klasse_Energieausweis_NWB_2024.vb, Klasse_Energieausweis_NWB_2020.vb. — One of this dimension's main actionable groups (15 warning-level).
  2. Resolve the 13 FileTooLong finding(s) in God Classes — start with Modul_PDF.vb, Modul_XML.vb, Klasse_Energieausweis_NWB_2024.vb. — One of this dimension's main actionable groups (13 warning-level).
  3. Resolve the 12 ClassTooLong finding(s) in God Classes — start with Modul_XML.vb, Klasse_Energieausweis_NWB_2024.vb, Klasse_Energieausweis_NWB_2020.vb. — One of this dimension's main actionable groups (12 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication7.7 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 7.7 / 10 · rule-coverage 100% · ceiling Verified

18 duplicated block group(s) detected. 5.6 % of the production lines (1,563 of 27,676) are in a reported copy. A further 13 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×3VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5682
Duplicated block (8 lines × 2) · ×2VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5125
Edited copy of a member (142 corresponding lines)VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:10
Edited copy of a member (31 corresponding lines)VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5103
Edited copy of a member (28 corresponding lines)VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:282

+ 23 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 3 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with Modul_XML.vb (2), Modul_PDF.vb. — One of this dimension's main actionable groups (3 warning-level).
  2. Resolve the 2 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Modul_PDF.vb, Modul_Image.vb. — One of this dimension's main actionable groups (2 warning-level).
  3. Resolve the 1 Edited copy of a member (142 corresponding lines) finding(s) in Code Duplication — start with Modul_Berechnungen.vb. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

1 projects, 0 dependency cycle(s), 0 unstable depended-on project(s).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt9.7 / 10Adequategated by 5 critical findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

5 deducted debt markers + unmeasured dead symbols across 27676 LoC in the .NET projects (0.2/KLoC) → score 9.7. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.

OnErrorResumeSwallow · ×5VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3376

What to do

  1. Resolve the 5 OnErrorResumeSwallow finding(s) in Explicit Debt — start with Modul_PDF.vb (5). — One of this dimension's main actionable groups (5 issue-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D18 · Solution Shape10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether the solution is laid out in a sensible, conventional structure.

Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

1 projects, 22 source files, 27676 hand-written lines of code (27676 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), plus 521 generated (machine-written code — designer, scaffolded and tool-emitted files — excluded from quality), 0 inter-project edges (build status unknown — did not finish).

Solution references a project that does not existVB-NET-BBSR-Drucktool/VB-NET-BBSR-Drucktool.sln

What to do

  1. Resolve the 1 Solution references a project that does not exist finding(s) in Solution Shape — start with VB-NET-BBSR-Drucktool.sln. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d18_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundVB-NET-BBSR-Drucktool/BBSR-Energieausweis.vbproj:8

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with BBSR-Energieausweis.vbproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value9.5 8.6 / 10Strong✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 90% · ceiling Documented

5 of 1082 judged comments only repeat the code they sit on (0.5 %). 206 comment(s) in another language or script were not judged.

redundant comment · ×5VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:278

What to do

  1. Resolve the 5 redundant comment finding(s) in Comment Value — start with Modul_PDF.vb (4), Modul_Berechnungen.vb. — One of this dimension's main actionable groups (5 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

One project, `BBSR-Energieausweis` (27676 LoC, 324 public types across 2 namespaces): over its size bounds, but its parts reference each other, so it reads as one coherent unit.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

21 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)10.0 / 10Exemplary○ Nothing flagged

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

semgrep found no security issues.

✓ On the Gold path — maintain.

Detailed fixes: d29_recommendation.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure3.0 / 10Weak✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

  • ~27.7k production LoC (387 types) across 1 project(s) / 5 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.

What to do

  • Introduce deliberate module boundaries — by feature (vertical slices) if your team prefers, or by layer (domain/application/infrastructure). Even splitting into a few cohesive projects with a clear dependency direction would help.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

M1 · Documentation (README)6.7 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

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 documentation0.0 / 10Critical✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • 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 structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

  • No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

  • Add a CI workflow that builds and runs the test suite on every push/PR.
P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

  • Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the `catch` blocks that emit nothing — a discarded exception is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Run what this repository's stack ships: a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • 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.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health81%StrongSolid.
Architecture74%Adequate — gated by AX5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity55%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness12%Critical — gated by D8, P1, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security100%Checked 2 of 9Strongest area.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • 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 — 79 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • 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
  • 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 — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured
  • D14 License Compliance — Licence collector did not produce a result
  • D16 Bus Factor — too few commits for a meaningful bus factor
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D21 Naming Consistency — Naming consistency does not read Visual Basic yet; not measured.
  • D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
  • D23 Boundary Type-Coupling — single shared-core project — no cross-context coupling to assess
  • D25 ADR Conformance — no ADRs to check
  • D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
  • 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.
  • D34 Knowledge Freshness — too few commits to judge knowledge freshness
  • D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 20 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (18 with fewer than two methods, 2 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
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • 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 — 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 — no CI workflow found
  • 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 — Not applicable: no benchmark suite was found. This check searched for a BenchmarkDotNet reference in an .fsproj or .vbproj, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
  • 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.
  • 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 — 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
  • X12 Unreachable branch — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X13 Undrained process stream — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X14 Bypassable address classification — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X15 Unvalidated length from an untrusted reader — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X16 Unfloored truncation loop — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X17 Uncapped recursion over a caller-supplied document — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X18 Disposal-pattern correctness — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X19 Unrestored process-global state — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • 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 reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X21 Side-effecting pattern guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X22 Contradicted release guard — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X23 Unguarded diagnostic materialisation — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X24 Document value interpolated into markup unescaped — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X25 Inert configuration knob — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X26 Unsynchronised callback handoff — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X27 Collection changed while being enumerated — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • 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 — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X3 Exception handling — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X30 Support guard that admits what it rejects — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check reads C# syntax; no C# was loaded for this repository, so it has nothing to report. That is a limit of the analyzer, not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — 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
  • X7 Silent fallback defaults — 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

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 6 finding(s)
D17 · Explicit Debt · OnErrorResumeSwallow · ×5
  • OnErrorResumeSwallow VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3376 — On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
  • OnErrorResumeSwallow VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3416 — On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
  • OnErrorResumeSwallow VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3424 — On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
  • OnErrorResumeSwallow VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3439 — On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
  • OnErrorResumeSwallow VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:3444 — On Error Resume Next silently swallows every runtime error until the enclosing method returns — scope it with a paired `On Error GoTo 0` and check `Err.Number`, or convert to a `Try…Catch`.
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
Serious — 117 finding(s)
D3 · God Classes · MethodTooLong · ×15
  • MethodTooLong: Modul_XML.Datensatz_Lesen VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:792 — MethodTooLong — Datensatz_Lesen runs 1182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1082 over it, 11.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb:27 — MethodTooLong — Energieausweis_erzeugen runs 1121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1021 over it, 11.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 837 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 737 over it, 8.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 837 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 737 over it, 8.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 737 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 637 over it, 7.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 723 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 623 over it, 7.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 532 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 432 over it, 5.32× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 530 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 430 over it, 5.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb:25 — MethodTooLong — Energieausweis_erzeugen runs 507 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 407 over it, 5.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Modul_XML.XML_Kontrolldatei_einlesen VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:349 — MethodTooLong — XML_Kontrolldatei_einlesen runs 359 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 259 over it, 3.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Fenster_Start.Kompletter_Ablauf VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:74 — MethodTooLong — Kompletter_Ablauf runs 231 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 131 over it, 2.31× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Modul_Image.Image_Diagram_NWB_Energieaufteilung VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:905 — MethodTooLong — Image_Diagram_NWB_Energieaufteilung runs 110 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 10 over it, 1.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Modul_PDF.GetIntFontInfo VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:8412 — MethodTooLong — GetIntFontInfo runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Modul_XML.XML_Steuerungsdatei_schreiben VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:126 — MethodTooLong — XML_Steuerungsdatei_schreiben runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: Modul_Ablauf_ohne_Oberflaeche.Main VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb:14 — MethodTooLong — Main runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · FileTooLong · ×13
  • FileTooLong: Module/Modul_PDF.vb VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb — FileTooLong — 8951 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8451 over it, 17.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Module/Modul_XML.vb VB-NET-BBSR-Drucktool/Module/Modul_XML.vb — FileTooLong — 2005 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1505 over it, 4.01× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2024/Klasse_Energieausweis_NWB_2024.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb — FileTooLong — 1128 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 628 over it, 2.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2020/Klasse_Energieausweis_NWB_2020.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb — FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 343 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2023/Klasse_Energieausweis_NWB_2023.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb — FileTooLong — 843 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 343 over it, 1.69× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Module/Modul_Image.vb VB-NET-BBSR-Drucktool/Module/Modul_Image.vb — FileTooLong — 800 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 300 over it, 1.60× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2024/Klasse_Energieausweis_WB_2024.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb — FileTooLong — 743 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 243 over it, 1.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2016/Klasse_Energieausweis_NWB_2016.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb — FileTooLong — 729 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 229 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Module/Modul_Variablen.vb VB-NET-BBSR-Drucktool/Module/Modul_Variablen.vb — FileTooLong — 704 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 204 over it, 1.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: Fenster/Fenster_Start.vb VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb — FileTooLong — 546 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 46 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2020/Klasse_Energieausweis_WB_2020.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb — FileTooLong — 538 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 38 over it, 1.08× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2023/Klasse_Energieausweis_WB_2023.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb — FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: 2016/Klasse_Energieausweis_WB_2016.vb VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb — FileTooLong — 513 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 13 over it, 1.03× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D3 · God Classes · ClassTooLong · ×12
  • ClassTooLong: Modul_XML VB-NET-BBSR-Drucktool/Module/Modul_XML.vb — ClassTooLong — 2001 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 1601 over it, 5.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_NWB_2024 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb — ClassTooLong — 1125 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 725 over it, 2.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_NWB_2020 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb — ClassTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 441 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_NWB_2023 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb — ClassTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 441 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Modul_Image VB-NET-BBSR-Drucktool/Module/Modul_Image.vb — ClassTooLong — 796 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 396 over it, 1.99× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_WB_2024 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb — ClassTooLong — 741 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 341 over it, 1.85× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_NWB_2016 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb — ClassTooLong — 727 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 327 over it, 1.82× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Modul_Variablen VB-NET-BBSR-Drucktool/Module/Modul_Variablen.vb — ClassTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 301 over it, 1.75× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Fenster_Start VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 143 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_WB_2020 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb — ClassTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 136 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_WB_2023 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb — ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: Klasse_Energieausweis_WB_2016 VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb — ClassTooLong — 511 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 111 over it, 1.28× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×3
  • Duplicated block (7 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5682 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5682-5688 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6192-6198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1503 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1503-1509 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1568-1574 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
  • Duplicated block (7 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1511 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1511-1517 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1576-1582 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D3 · God Classes · TooManyMethods · ×2
  • TooManyMethods: Modul_PDF VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb — TooManyMethods — 6017 significant lines (blank, comment-only and punctuation-only lines excluded), 953 methods. The bar is 30 methods; this is 923 over it, 31.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: CPDFTable VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb — TooManyMethods — 181 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 30 methods; this is 11 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5125 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5125-5132 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6242-6249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6253` calls `ToString` and `VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5133` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:645 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:645-652 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:713-720 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
AX5 · Architecture & structure · Appears unstructured (no recognised architecture) · ×1
  • Appears unstructured (no recognised architecture) — ~27.7k production LoC (387 types) across 1 project(s) / 5 namespace(s) with no recognised architectural style or layering — at this size, deliberate module boundaries would help. No DDD/clean/vertical-slice/CQRS/transaction-script organisation was detected — code is likely organised ad hoc, which makes change and onboarding harder as it grows.
D1 · Cyclomatic Complexity · Modul_XML.Datensatz_Lesen (cyclomatic 561) · ×1
  • Modul_XML.Datensatz_Lesen (cyclomatic 561) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:792 — Modul_XML.Datensatz_Lesen has cyclomatic complexity 561 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: VB-NET-BBSR-Drucktool/Module/Modul_XML.vb holds 4 of the 17 methods over the threshold — including the worst — and 639 of the 1663 points over it (38%), 3.2× the next-largest file (VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb at 199). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cyclomatic 214) · ×1
  • Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cyclomatic 214) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb:27 — Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen has cyclomatic complexity 214 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cyclomatic 158) · ×1
  • Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cyclomatic 158) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb:25 — Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen has cyclomatic complexity 158 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cyclomatic 158) · ×1
  • Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cyclomatic 158) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb:25 — Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen has cyclomatic complexity 158 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cyclomatic 141) · ×1
  • Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cyclomatic 141) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb:25 — Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen has cyclomatic complexity 141 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cyclomatic 139) · ×1
  • Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cyclomatic 139) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb:25 — Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen has cyclomatic complexity 139 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen (cyclomatic 103) · ×1
  • Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen (cyclomatic 103) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb:25 — Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen has cyclomatic complexity 103 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen (cyclomatic 100) · ×1
  • Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen (cyclomatic 100) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb:25 — Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen has cyclomatic complexity 100 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen (cyclomatic 100) · ×1
  • Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen (cyclomatic 100) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb:25 — Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen has cyclomatic complexity 100 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Modul_XML.XML_Kontrolldatei_einlesen (cyclomatic 91) · ×1
  • Modul_XML.XML_Kontrolldatei_einlesen (cyclomatic 91) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:349 — Modul_XML.XML_Kontrolldatei_einlesen has cyclomatic complexity 91 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: VB-NET-BBSR-Drucktool/Module/Modul_XML.vb holds 4 of the 17 methods over the threshold — including the worst — and 639 of the 1663 points over it (38%), 3.2× the next-largest file (VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb at 199). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · Modul_XML.XML_Steuerungsdatei_einlesen (cyclomatic 30) · ×1
  • Modul_XML.XML_Steuerungsdatei_einlesen (cyclomatic 30) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:21 — Modul_XML.XML_Steuerungsdatei_einlesen has cyclomatic complexity 30 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: VB-NET-BBSR-Drucktool/Module/Modul_XML.vb holds 4 of the 17 methods over the threshold — including the worst — and 639 of the 1663 points over it (38%), 3.2× the next-largest file (VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb at 199). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · Fenster_Start.Energeiausweis_erstellen (cyclomatic 25) · ×1
  • Fenster_Start.Energeiausweis_erstellen (cyclomatic 25) VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:878 — Fenster_Start.Energeiausweis_erstellen has cyclomatic complexity 25 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen (cyclomatic 24) · ×1
  • Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen (cyclomatic 24) VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb:397 — Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen has cyclomatic complexity 24 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Fenster_Start.Kompletter_Ablauf (cyclomatic 22) · ×1
  • Fenster_Start.Kompletter_Ablauf (cyclomatic 22) VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:74 — Fenster_Start.Kompletter_Ablauf has cyclomatic complexity 22 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Modul_Image.Image_Diagram_NWB_Energieaufteilung (cyclomatic 18) · ×1
  • Modul_Image.Image_Diagram_NWB_Energieaufteilung (cyclomatic 18) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:905 — Modul_Image.Image_Diagram_NWB_Energieaufteilung has cyclomatic complexity 18 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Modul_Image.Image_Pfeil_WB (cyclomatic 17) · ×1
  • Modul_Image.Image_Pfeil_WB (cyclomatic 17) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:556 — Modul_Image.Image_Pfeil_WB has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
D1 · Cyclomatic Complexity · Modul_XML.XML_Steuerungsdatei_schreiben (cyclomatic 17) · ×1
  • Modul_XML.XML_Steuerungsdatei_schreiben (cyclomatic 17) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:126 — Modul_XML.XML_Steuerungsdatei_schreiben has cyclomatic complexity 17 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table. This file is where this pass's cyclomatic complexity CONCENTRATES: VB-NET-BBSR-Drucktool/Module/Modul_XML.vb holds 4 of the 17 methods over the threshold — including the worst — and 639 of the 1663 points over it (38%), 3.2× the next-largest file (VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb at 199). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D18 · Solution Shape · Solution references a project that does not exist · ×1
  • Solution references a project that does not exist VB-NET-BBSR-Drucktool/VB-NET-BBSR-Drucktool.sln — `VB-NET-BBSR-Drucktool/VB-NET-BBSR-Drucktool.sln` declares 1 project file(s) that are missing from the tree (`VB-NET-BBSR-Webservice/BBSR-Webservice/BBSR-Webservice.vbproj`). A solution-level restore or build fails on a dangling reference, so anyone building the solution rather than an individual project is blocked. Delete the stale entry from the solution, or restore the missing project file.
D2 · Cognitive Complexity · Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cognitive 733) · ×1
  • Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen (cognitive 733) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_NWB_2024.vb:27 — Klasse_Energieausweis_NWB_2024.Energieausweis_erzeugen has cognitive complexity 733 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cognitive 491) · ×1
  • Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen (cognitive 491) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_NWB_2020.vb:25 — Klasse_Energieausweis_NWB_2020.Energieausweis_erzeugen has cognitive complexity 491 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cognitive 491) · ×1
  • Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen (cognitive 491) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_NWB_2023.vb:25 — Klasse_Energieausweis_NWB_2023.Energieausweis_erzeugen has cognitive complexity 491 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cognitive 433) · ×1
  • Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen (cognitive 433) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_NWB_2016.vb:25 — Klasse_Energieausweis_NWB_2016.Energieausweis_erzeugen has cognitive complexity 433 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cognitive 432) · ×1
  • Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen (cognitive 432) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2024/Klasse_Energieausweis_WB_2024.vb:25 — Klasse_Energieausweis_WB_2024.Energieausweis_erzeugen has cognitive complexity 432 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen (cognitive 234) · ×1
  • Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen (cognitive 234) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2016/Klasse_Energieausweis_WB_2016.vb:25 — Klasse_Energieausweis_WB_2016.Energieausweis_erzeugen has cognitive complexity 234 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen (cognitive 219) · ×1
  • Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen (cognitive 219) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2020/Klasse_Energieausweis_WB_2020.vb:25 — Klasse_Energieausweis_WB_2020.Energieausweis_erzeugen has cognitive complexity 219 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen (cognitive 219) · ×1
  • Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen (cognitive 219) VB-NET-BBSR-Drucktool/Klassen-Energieausweis/2023/Klasse_Energieausweis_WB_2023.vb:25 — Klasse_Energieausweis_WB_2023.Energieausweis_erzeugen has cognitive complexity 219 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_XML.Datensatz_Lesen (cognitive 134) · ×1
  • Modul_XML.Datensatz_Lesen (cognitive 134) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:792 — Modul_XML.Datensatz_Lesen has cognitive complexity 134 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_XML.XML_Steuerungsdatei_schreiben (cognitive 35) · ×1
  • Modul_XML.XML_Steuerungsdatei_schreiben (cognitive 35) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:126 — Modul_XML.XML_Steuerungsdatei_schreiben has cognitive complexity 35 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Image.Image_Pfeil_WB (cognitive 33) · ×1
  • Modul_Image.Image_Pfeil_WB (cognitive 33) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:556 — Modul_Image.Image_Pfeil_WB has cognitive complexity 33 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_XML.XML_Datei_Datenregistratur_auswerten (cognitive 26) · ×1
  • Modul_XML.XML_Datei_Datenregistratur_auswerten (cognitive 26) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2409 — Modul_XML.XML_Datei_Datenregistratur_auswerten has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_XML.XML_Datei_ZusatzdatenErfassung_auswerten (cognitive 26) · ×1
  • Modul_XML.XML_Datei_ZusatzdatenErfassung_auswerten (cognitive 26) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2481 — Modul_XML.XML_Datei_ZusatzdatenErfassung_auswerten has cognitive complexity 26 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Berechnungen.Zusammenstellung_NWB_Verbrauchserfassung (cognitive 25) · ×1
  • Modul_Berechnungen.Zusammenstellung_NWB_Verbrauchserfassung (cognitive 25) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:158 — Modul_Berechnungen.Zusammenstellung_NWB_Verbrauchserfassung has cognitive complexity 25 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_XML.XML_Kontrolldatei_einlesen (cognitive 24) · ×1
  • Modul_XML.XML_Kontrolldatei_einlesen (cognitive 24) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:349 — Modul_XML.XML_Kontrolldatei_einlesen has cognitive complexity 24 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Berechnungen.Zusammenstellung_WB_Verbrauchserfassung (cognitive 22) · ×1
  • Modul_Berechnungen.Zusammenstellung_WB_Verbrauchserfassung (cognitive 22) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:8 — Modul_Berechnungen.Zusammenstellung_WB_Verbrauchserfassung has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_PDF.GetIntFontInfo (cognitive 22) · ×1
  • Modul_PDF.GetIntFontInfo (cognitive 22) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:8412 — Modul_PDF.GetIntFontInfo has cognitive complexity 22 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Image.PDF_erzeugen (cognitive 21) · ×1
  • Modul_Image.PDF_erzeugen (cognitive 21) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:1088 — Modul_Image.PDF_erzeugen has cognitive complexity 21 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Ablauf_Funktionen.Testdaten_anlegen (cognitive 19) · ×1
  • Modul_Ablauf_Funktionen.Testdaten_anlegen (cognitive 19) VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_Funktionen.vb:287 — Modul_Ablauf_Funktionen.Testdaten_anlegen has cognitive complexity 19 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Fenster_Start.Energeiausweis_erstellen (cognitive 18) · ×1
  • Fenster_Start.Energeiausweis_erstellen (cognitive 18) VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:878 — Fenster_Start.Energeiausweis_erstellen has cognitive complexity 18 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen (cognitive 17) · ×1
  • Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen (cognitive 17) VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb:397 — Modul_Ablauf_ohne_Oberflaeche.Energeiausweis_erstellen has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_PDF.GetIntColorSpaceObj (cognitive 17) · ×1
  • Modul_PDF.GetIntColorSpaceObj (cognitive 17) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:8219 — Modul_PDF.GetIntColorSpaceObj has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D2 · Cognitive Complexity · Modul_Image.Image_Diagram_NWB_Energieaufteilung (cognitive 17) · ×1
  • Modul_Image.Image_Diagram_NWB_Energieaufteilung (cognitive 17) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:905 — Modul_Image.Image_Diagram_NWB_Energieaufteilung has cognitive complexity 17 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
D4 · Code Duplication · Edited copy of a member (142 corresponding lines) · ×1
  • Edited copy of a member (142 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:10 — VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:10-151 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:160-329 — These two members are one piece of code written twice and then edited apart: 142 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (31 corresponding lines) · ×1
  • Edited copy of a member (31 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5103 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5103-5133 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6225-6255 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:282 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:282-313 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:326-353 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (84 corresponding lines) · ×1
  • Edited copy of a member (84 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb:399 — VB-NET-BBSR-Drucktool/Module/Modul_Ablauf_ohne_Oberflaeche.vb:399-482 | VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:880-963 — These two members are one piece of code written twice and then edited apart: 84 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (52 corresponding lines) · ×1
  • Edited copy of a member (52 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2411 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2411-2470 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2483-2534 — These two members are one piece of code written twice and then edited apart: 52 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (48 corresponding lines) · ×1
  • Edited copy of a member (48 corresponding lines) VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:712 — VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:712-760 | VB-NET-BBSR-Drucktool/Fenster/Fenster_Start.vb:769-816 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6259 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6259-6271 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6306-6320 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×1
  • Edited copy of a member (11 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5680 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5680-5692 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:6190-6200 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×1
  • Edited copy of a member (15 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5020 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5020-5034 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5574-5588 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (23 corresponding lines) · ×1
  • Edited copy of a member (23 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Webdienst.vb:68 — VB-NET-BBSR-Drucktool/Module/Modul_Webdienst.vb:68-90 | VB-NET-BBSR-Drucktool/Module/Modul_Webdienst.vb:124-146 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×1
  • Edited copy of a member (4 corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:7932 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:7932-7935 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:7939-7942 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 28+ corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:342 — VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:342-369 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:382-409 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:422-449 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:462-489 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:502-529 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:538-565 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:578-605 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:614-641 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 12+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 12+ corresponding lines) VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:4761 — VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:4761-4772 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5651-5664 | VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:5896-5909 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (46 lines × 2) · ×1
  • Duplicated block (46 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:59 — VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:59-104 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:235-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (41 lines × 2) · ×1
  • Duplicated block (41 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:10 — VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:10-50 | VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:160-200 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (29 lines × 3) · ×1
  • Duplicated block (29 lines × 3) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1143 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1143-1171 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1271-1299 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1407-1435 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×1
  • Duplicated block (23 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:404 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:404-426 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:435-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×1
  • Duplicated block (21 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1105 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1105-1125 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1229-1249 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1483 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1483-1501 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1548-1566 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (18 lines × 4) · ×1
  • Duplicated block (18 lines × 4) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1138 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1138-1155 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1266-1283 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1402-1419 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:1657-1674 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×1
  • Duplicated block (13 lines × 3) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2091 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2091-2103 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2112-2124 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2133-2145 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2091` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2061 — VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2061-2072 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2088-2099 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2109-2120 | VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2130-2141 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2087` calls `ImportBool` and `VB-NET-BBSR-Drucktool/Module/Modul_XML.vb:2060` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5–9 lines × 4) · ×1
  • Duplicated block (5–9 lines × 4) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:31 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:31-39 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:42-50 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:53-62 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:65-69 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:69` calls `DrawString` and `VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:39` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×1
  • Duplicated block (9 lines × 2) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:654 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:654-662 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:722-730 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:406 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:406-412 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:437-443 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:480-486 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
D4 · Code Duplication · Duplicated block (4–5 lines × 3) · ×1
  • Duplicated block (4–5 lines × 3) VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:237 — VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:237-240 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:242-246 | VB-NET-BBSR-Drucktool/Module/Modul_Image.vb:248-252 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
P1 · CI/CD gates · No CI pipeline · ×1
  • No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Minor — 10 finding(s)
D24 · Comment Value · redundant comment · ×5
  • redundant comment VB-NET-BBSR-Drucktool/Module/Modul_Berechnungen.vb:278 — "-------------------------------------------------- Leerstandszuschlag-thermisch-erzeugte-Kaelte --------------------------------------------------" repeats the code it sits on: 4 of its 4 words (leerstandszuschlag, thermisch, erzeugte, kaelte) are already in `If .Leerstandszuschlag_thermisch_erzeugte_Kaelte.Leerstandszuschlag_kWh.Wert <> 0 Then`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:2247 — "Color space of the border color" repeats the code it sits on: 3 of its 3 words (color, space, border) are already in `Dim BorderColorSP As TExtColorSpace ' Color space of the border color`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:2826 — "Fill color space" repeats the code it sits on: 3 of its 3 words (fill, color, space) are already in `Dim FillCS As TPDFColorSpace ' Fill color space`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:2827 — "Stroke color space" repeats the code it sits on: 3 of its 3 words (stroke, color, space) are already in `Dim StrokeCS As TPDFColorSpace ' Stroke color space`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment VB-NET-BBSR-Drucktool/Module/Modul_PDF.vb:8908 — "Color space of the border color" repeats the code it sits on: 3 of its 3 words (color, space, border) are already in `Dim BorderColorSP As TExtColorSpace ' Color space of the border color`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found VB-NET-BBSR-Drucktool/BBSR-Energieausweis.vbproj:8 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `VB-NET-BBSR-Drucktool/BBSR-Energieausweis.vbproj` makes this repository a deployable product (line 8).
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — 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.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add a Roslyn security analyzer package referenced from the project (the analyzer packages do analyse VB.NET), plus gitleaks for committed secrets — CodeQL has no VB.NET extractor, so its csharp pack would extract nothing from this tree and then report it clean — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — 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.)

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-d7b581c5499a402c929b13a4d797e23d/history.json --exit-code 0 --source .0artifacts/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-d7b581c5499a402c929b13a4d797e23d/tree.json --exit-code 0 --source .0artifacts/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 .0artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnuget—nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a1dd25-33f2-762e-b0db-0da4942f6706 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md