Public report of CSBiology/ProteomIQon, published 31 October 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 reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). 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, 31 October 2026, 13:26 UTC · Survey ID cd_a7e121989db84242bf90dd524d18cde9
CSBiology/ProteomIQon
Measured 31 October 2026, 13:26 UTC, at code version e5abce1
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: No coverage collector is wired up.
Test reliability is not measured: No test run produced results.
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
Up 3 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: 22,742 lines of product code in 32 projects, tests not counted · Estimated rebuild effort: about 0.2 person-years · Weakest lens: Production Readiness, 53
Findings by how serious they are
7 critical202 serious21 minor
48 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
31 October 2026, 13:26 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 Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
The score is deterministic, which means the same code always gets the same score. Watchdog works 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 ▸
36of 36 dimensions measured by tools.
220of 230 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
36dimensions across 7 lenses, read from 22,742 lines of product code in 32 projects.
CSBiology/ProteomIQon falls short of our standard for a preview release because we found no automated security scanning of the code, its secrets or its dependencies. It scores 61 out of 100 and is rated Adequate, and all seven of its critical findings are security problems in the build pipeline.
Production Readiness, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 5 points. Fixing the part of the code only one person knows comes next, also worth about 5. Raising Production Readiness to 62 would lift the score to about 64.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 22,742 lines, about €31,000 to rebuild. Two of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
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 forThe 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.
Watchdog compares 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.
Fixed since the last survey: 71 findings
These 71 critical or serious findings were in the previous survey, on 17 October 2026, and are gone from this one.
€10,000 to €51,000, for 169 to 537 hours of work, about 0.2 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.8 at a score of 61. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 22,742 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices 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.
Raises the score by about 5 points · Low effort · ADR Quality
2
Resolve the 1 Off-boarding risk finding(s) in Bus Factor.
Raises the score by about 5 points · Low effort · Bus Factor
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.
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 €31,000 to build again, about 0.2 person-years of work. Its weakest lens is Production Readiness, at 53 (Adequate). 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 5 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 6.4 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 4% to 9% on every change.
How this is estimated: It rests on an assumption of Watchdog's 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. The result is a range for planning, not a measurement.
Based on: Code Duplication
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 — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
105 modules, with 78 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 65 more are left out to keep it readable.
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.
ProteomIQon.Common.LabelFreeQuantification uses ProteomIQon.Common, so a change to ProteomIQon.Common can break ProteomIQon.Common.LabelFreeQuantification, while a change to ProteomIQon.Common.LabelFreeQuantification can't break ProteomIQon.Common.
Position
Below the diagonal: ProteomIQon.Common.LabelFreeQuantification uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ProteomIQon.Common.LabelFreeQuantification.AggregationParams uses a type in ProteomIQon.Domain.LabelFreeQuantification.
ProteomIQon.Common.LabelFreeQuantification.AggregationParams uses ProteomIQon.Domain.LabelFreeQuantification, so a change to ProteomIQon.Domain.LabelFreeQuantification can break ProteomIQon.Common.LabelFreeQuantification.AggregationParams, while a change to ProteomIQon.Common.LabelFreeQuantification.AggregationParams can't break ProteomIQon.Domain.LabelFreeQuantification.
Position
Below the diagonal: ProteomIQon.Common.LabelFreeQuantification.AggregationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Common.LabeledProteinQuantification uses ProteomIQon.Common, so a change to ProteomIQon.Common can break ProteomIQon.Common.LabeledProteinQuantification, while a change to ProteomIQon.Common.LabeledProteinQuantification can't break ProteomIQon.Common.
Position
Below the diagonal: ProteomIQon.Common.LabeledProteinQuantification uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ProteomIQon.Common.LabeledProteinQuantification.AggregationParams uses a type in ProteomIQon.Domain.LabeledProteinQuantification.
ProteomIQon.Common.LabeledProteinQuantification.AggregationParams uses ProteomIQon.Domain.LabeledProteinQuantification, so a change to ProteomIQon.Domain.LabeledProteinQuantification can break ProteomIQon.Common.LabeledProteinQuantification.AggregationParams, while a change to ProteomIQon.Common.LabeledProteinQuantification.AggregationParams can't break ProteomIQon.Domain.LabeledProteinQuantification.
Position
Below the diagonal: ProteomIQon.Common.LabeledProteinQuantification.AggregationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Domain uses ProteomIQon.Common, so a change to ProteomIQon.Common can break ProteomIQon.Domain, while a change to ProteomIQon.Domain can't break ProteomIQon.Common.
Position
Below the diagonal: ProteomIQon.Domain uses a module listed above it, which is the healthy direction.
ProteomIQon.Domain uses ProteomIQon.Common.MassMode, so a change to ProteomIQon.Common.MassMode can break ProteomIQon.Domain, while a change to ProteomIQon.Domain can't break ProteomIQon.Common.MassMode.
Position
Below the diagonal: ProteomIQon.Domain uses a module listed above it, which is the healthy direction.
ProteomIQon.Domain uses ProteomIQon.Domain.LabeledProteinQuantification, so a change to ProteomIQon.Domain.LabeledProteinQuantification can break ProteomIQon.Domain, while a change to ProteomIQon.Domain can't break ProteomIQon.Domain.LabeledProteinQuantification.
Position
Below the diagonal: ProteomIQon.Domain uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in ProteomIQon.Drafo.Core uses a type in Deedle.Frame.
The types involved
ProteomIQon.Drafo.Core.Core → Deedle.Frame.Frame
Direction
ProteomIQon.Drafo.Core uses Deedle.Frame, so a change to Deedle.Frame can break ProteomIQon.Drafo.Core, while a change to ProteomIQon.Drafo.Core can't break Deedle.Frame.
Position
Below the diagonal: ProteomIQon.Drafo.Core uses a module listed above it, which is the healthy direction.
ProteomIQon.LabelEfficiencyCalculator uses Deedle.Frame, so a change to Deedle.Frame can break ProteomIQon.LabelEfficiencyCalculator, while a change to ProteomIQon.LabelEfficiencyCalculator can't break Deedle.Frame.
Position
Below the diagonal: ProteomIQon.LabelEfficiencyCalculator uses a module listed above it, which is the healthy direction.
ProteomIQon.SpectrumSearch uses ProteomIQon.PeptideIndex, so a change to ProteomIQon.PeptideIndex can break ProteomIQon.SpectrumSearch, while a change to ProteomIQon.SpectrumSearch can't break ProteomIQon.PeptideIndex.
Position
Below the diagonal: ProteomIQon.SpectrumSearch uses a module listed above it, which is the healthy direction.
ProteomIQon.AlignmentBasedQuantStatistics uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.AlignmentBasedQuantStatistics, while a change to ProteomIQon.AlignmentBasedQuantStatistics can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.AlignmentBasedQuantStatistics uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto uses ProteomIQon.Common, so a change to ProteomIQon.Common can break ProteomIQon.Dto, while a change to ProteomIQon.Dto can't break ProteomIQon.Common.
Position
Below the diagonal: ProteomIQon.Dto uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto uses ProteomIQon.Common.MassMode, so a change to ProteomIQon.Common.MassMode can break ProteomIQon.Dto, while a change to ProteomIQon.Dto can't break ProteomIQon.Common.MassMode.
Position
Below the diagonal: ProteomIQon.Dto uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto uses ProteomIQon.Domain.LabeledProteinQuantification, so a change to ProteomIQon.Domain.LabeledProteinQuantification can break ProteomIQon.Dto, while a change to ProteomIQon.Dto can't break ProteomIQon.Domain.LabeledProteinQuantification.
Position
Below the diagonal: ProteomIQon.Dto uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto uses ProteomIQon.Ontologies, so a change to ProteomIQon.Ontologies can break ProteomIQon.Dto, while a change to ProteomIQon.Dto can't break ProteomIQon.Ontologies.
Position
Below the diagonal: ProteomIQon.Dto uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto, while a change to ProteomIQon.Dto can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.AlignmentBasedQuantStatisticsParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.AlignmentBasedQuantStatisticsParams, while a change to ProteomIQon.Dto.AlignmentBasedQuantStatisticsParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.AlignmentBasedQuantStatisticsParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.AlignmentBasedQuantificationParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.AlignmentBasedQuantificationParams, while a change to ProteomIQon.Dto.AlignmentBasedQuantificationParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.AlignmentBasedQuantificationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.ConsensusSpectralLibraryParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.ConsensusSpectralLibraryParams, while a change to ProteomIQon.Dto.ConsensusSpectralLibraryParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.ConsensusSpectralLibraryParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.LabelEfficiencyCalculationParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.LabelEfficiencyCalculationParams, while a change to ProteomIQon.Dto.LabelEfficiencyCalculationParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.LabelEfficiencyCalculationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.LabelFreeQuantificationParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.LabelFreeQuantificationParams, while a change to ProteomIQon.Dto.LabelFreeQuantificationParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.LabelFreeQuantificationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.LabeledQuantificationParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.LabeledQuantificationParams, while a change to ProteomIQon.Dto.LabeledQuantificationParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.LabeledQuantificationParams uses a module listed above it, which is the healthy direction.
ProteomIQon.Dto.MzTABParams uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.Dto.MzTABParams, while a change to ProteomIQon.Dto.MzTABParams can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.Dto.MzTABParams uses a module listed above it, which is the healthy direction.
ProteomIQon.LabelFreeProteinQuantification uses ProteomIQon.Domain.LabelFreeQuantification, so a change to ProteomIQon.Domain.LabelFreeQuantification can break ProteomIQon.LabelFreeProteinQuantification, while a change to ProteomIQon.LabelFreeProteinQuantification can't break ProteomIQon.Domain.LabelFreeQuantification.
Position
Below the diagonal: ProteomIQon.LabelFreeProteinQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.LabelFreeProteinQuantification uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.LabelFreeProteinQuantification, while a change to ProteomIQon.LabelFreeProteinQuantification can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.LabelFreeProteinQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.LabeledProteinQuantification uses ProteomIQon.Domain.LabeledProteinQuantification, so a change to ProteomIQon.Domain.LabeledProteinQuantification can break ProteomIQon.LabeledProteinQuantification, while a change to ProteomIQon.LabeledProteinQuantification can't break ProteomIQon.Domain.LabeledProteinQuantification.
Position
Below the diagonal: ProteomIQon.LabeledProteinQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.LabeledProteinQuantification uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.LabeledProteinQuantification, while a change to ProteomIQon.LabeledProteinQuantification can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.LabeledProteinQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.MzMLIonMobilityToMzLite uses ProteomIQon.Dto.MzMLtoMzLiteParams, so a change to ProteomIQon.Dto.MzMLtoMzLiteParams can break ProteomIQon.MzMLIonMobilityToMzLite, while a change to ProteomIQon.MzMLIonMobilityToMzLite can't break ProteomIQon.Dto.MzMLtoMzLiteParams.
Position
Below the diagonal: ProteomIQon.MzMLIonMobilityToMzLite uses a module listed above it, which is the healthy direction.
ProteomIQon.MzMLIonMobilityToMzLite uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.MzMLIonMobilityToMzLite, while a change to ProteomIQon.MzMLIonMobilityToMzLite can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.MzMLIonMobilityToMzLite uses a module listed above it, which is the healthy direction.
ProteomIQon.MzMLToMzLite uses ProteomIQon.Dto.MzMLtoMzLiteParams, so a change to ProteomIQon.Dto.MzMLtoMzLiteParams can break ProteomIQon.MzMLToMzLite, while a change to ProteomIQon.MzMLToMzLite can't break ProteomIQon.Dto.MzMLtoMzLiteParams.
Position
Below the diagonal: ProteomIQon.MzMLToMzLite uses a module listed above it, which is the healthy direction.
ProteomIQon.MzMLToMzLite uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.MzMLToMzLite, while a change to ProteomIQon.MzMLToMzLite can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.MzMLToMzLite uses a module listed above it, which is the healthy direction.
ProteomIQon.TableSort uses Deedle.Frame, so a change to Deedle.Frame can break ProteomIQon.TableSort, while a change to ProteomIQon.TableSort can't break Deedle.Frame.
Position
Below the diagonal: ProteomIQon.TableSort uses a module listed above it, which is the healthy direction.
ProteomIQon.TableSort uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.TableSort, while a change to ProteomIQon.TableSort can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.TableSort uses a module listed above it, which is the healthy direction.
ProteomIQon.AlignmentBasedQuantification uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.AlignmentBasedQuantification, while a change to ProteomIQon.AlignmentBasedQuantification can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.AlignmentBasedQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.AlignmentBasedQuantification uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.AlignmentBasedQuantification, while a change to ProteomIQon.AlignmentBasedQuantification can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.AlignmentBasedQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.ConsensusSpectralLibrary uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.ConsensusSpectralLibrary, while a change to ProteomIQon.ConsensusSpectralLibrary can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.ConsensusSpectralLibrary uses a module listed above it, which is the healthy direction.
ProteomIQon.ConsensusSpectralLibrary uses ProteomIQon.LabelEfficiencyCalculator, so a change to ProteomIQon.LabelEfficiencyCalculator can break ProteomIQon.ConsensusSpectralLibrary, while a change to ProteomIQon.ConsensusSpectralLibrary can't break ProteomIQon.LabelEfficiencyCalculator.
Position
Below the diagonal: ProteomIQon.ConsensusSpectralLibrary uses a module listed above it, which is the healthy direction.
ProteomIQon.ConsensusSpectralLibrary uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.ConsensusSpectralLibrary, while a change to ProteomIQon.ConsensusSpectralLibrary can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.ConsensusSpectralLibrary uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABAux uses Deedle.Frame, so a change to Deedle.Frame can break ProteomIQon.MzTABAux, while a change to ProteomIQon.MzTABAux can't break Deedle.Frame.
Position
Below the diagonal: ProteomIQon.MzTABAux uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABAux uses ProteomIQon.Ontologies, so a change to ProteomIQon.Ontologies can break ProteomIQon.MzTABAux, while a change to ProteomIQon.MzTABAux can't break ProteomIQon.Ontologies.
Position
Below the diagonal: ProteomIQon.MzTABAux uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABAux uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.MzTABAux, while a change to ProteomIQon.MzTABAux can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.MzTABAux uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABAux uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.MzTABAux, while a change to ProteomIQon.MzTABAux can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.MzTABAux uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMBasedQuantification uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.PSMBasedQuantification, while a change to ProteomIQon.PSMBasedQuantification can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.PSMBasedQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMBasedQuantification uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.PSMBasedQuantification, while a change to ProteomIQon.PSMBasedQuantification can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.PSMBasedQuantification uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMBasedQuantificationTIMs uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.PSMBasedQuantificationTIMs, while a change to ProteomIQon.PSMBasedQuantificationTIMs can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.PSMBasedQuantificationTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMBasedQuantificationTIMs uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.PSMBasedQuantificationTIMs, while a change to ProteomIQon.PSMBasedQuantificationTIMs can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.PSMBasedQuantificationTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMStatistics uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.PSMStatistics, while a change to ProteomIQon.PSMStatistics can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.PSMStatistics uses a module listed above it, which is the healthy direction.
ProteomIQon.PSMStatistics uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.PSMStatistics, while a change to ProteomIQon.PSMStatistics can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.PSMStatistics uses a module listed above it, which is the healthy direction.
ProteomIQon.PeptideSpectrumMatchingTIMs uses ProteomIQon.PeptideIndex, so a change to ProteomIQon.PeptideIndex can break ProteomIQon.PeptideSpectrumMatchingTIMs, while a change to ProteomIQon.PeptideSpectrumMatchingTIMs can't break ProteomIQon.PeptideIndex.
Position
Below the diagonal: ProteomIQon.PeptideSpectrumMatchingTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.PeptideSpectrumMatchingTIMs uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.PeptideSpectrumMatchingTIMs, while a change to ProteomIQon.PeptideSpectrumMatchingTIMs can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.PeptideSpectrumMatchingTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.PeptideSpectrumMatchingTIMs uses ProteomIQon.SpectrumSearch, so a change to ProteomIQon.SpectrumSearch can break ProteomIQon.PeptideSpectrumMatchingTIMs, while a change to ProteomIQon.PeptideSpectrumMatchingTIMs can't break ProteomIQon.SpectrumSearch.
Position
Below the diagonal: ProteomIQon.PeptideSpectrumMatchingTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.PeptideSpectrumMatchingTIMs uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.PeptideSpectrumMatchingTIMs, while a change to ProteomIQon.PeptideSpectrumMatchingTIMs can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.PeptideSpectrumMatchingTIMs uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABFormater uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.MzTABFormater, while a change to ProteomIQon.MzTABFormater can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.MzTABFormater uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABFormater uses ProteomIQon.MzTABAux, so a change to ProteomIQon.MzTABAux can break ProteomIQon.MzTABFormater, while a change to ProteomIQon.MzTABFormater can't break ProteomIQon.MzTABAux.
Position
Below the diagonal: ProteomIQon.MzTABFormater uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABSections uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.MzTABSections, while a change to ProteomIQon.MzTABSections can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.MzTABSections uses a module listed above it, which is the healthy direction.
ProteomIQon.MzTABSections uses ProteomIQon.MzTABAux, so a change to ProteomIQon.MzTABAux can break ProteomIQon.MzTABSections, while a change to ProteomIQon.MzTABSections can't break ProteomIQon.MzTABAux.
Position
Below the diagonal: ProteomIQon.MzTABSections uses a module listed above it, which is the healthy direction.
ProteomIQon.SwathAnalysis uses ProteomIQon.Domain, so a change to ProteomIQon.Domain can break ProteomIQon.SwathAnalysis, while a change to ProteomIQon.SwathAnalysis can't break ProteomIQon.Domain.
Position
Below the diagonal: ProteomIQon.SwathAnalysis uses a module listed above it, which is the healthy direction.
ProteomIQon.SwathAnalysis uses ProteomIQon.LabelEfficiencyCalculator, so a change to ProteomIQon.LabelEfficiencyCalculator can break ProteomIQon.SwathAnalysis, while a change to ProteomIQon.SwathAnalysis can't break ProteomIQon.LabelEfficiencyCalculator.
Position
Below the diagonal: ProteomIQon.SwathAnalysis uses a module listed above it, which is the healthy direction.
ProteomIQon.SwathAnalysis uses ProteomIQon.Dto, so a change to ProteomIQon.Dto can break ProteomIQon.SwathAnalysis, while a change to ProteomIQon.SwathAnalysis can't break ProteomIQon.Dto.
Position
Below the diagonal: ProteomIQon.SwathAnalysis uses a module listed above it, which is the healthy direction.
ProteomIQon.SwathAnalysis uses ProteomIQon.ConsensusSpectralLibrary, so a change to ProteomIQon.ConsensusSpectralLibrary can break ProteomIQon.SwathAnalysis, while a change to ProteomIQon.SwathAnalysis can't break ProteomIQon.ConsensusSpectralLibrary.
Position
Below the diagonal: ProteomIQon.SwathAnalysis uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
7
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 1 Off-boarding risk finding(s) in Bus Factor; 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 this
Helps
Effort
Dimension
Resolve the 1 No ADRs found finding(s) in ADR Quality.
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.
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Raise allocation-aware density on the hot paths — currently 21 use(s) across 24,720 production line(s) (~0.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
God Classes: FileTooLong: QuantBasedAlignment/QuantBasedAlignment.fs
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 — 7
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 — 202
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 — 21
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 48
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
Watchdog 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. 36 of 36 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.7 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 36 dimensions across the health lenses
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
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, 220 of 230 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.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D1 Cyclomatic Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.fs) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D2 Cognitive Complexity — not measured this run — Watchdog 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. Most of this repository's production source (.fs) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D6 Cohesion (LCOM4) — not measured this run — Watchdog 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. 3 of 3 class(es) with two or more methods were found, but the language model this pass loaded exposed none of their method bodies, so which method touches which field could not be seen.
D8 Code Coverage — 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. Coverage NOT MEASURED: `--collect:"XPlat Code Coverage"` names a data collector that ships in the `coverlet.collector` package, and this repository wires up none — no test project references it and no runsettings declares one. The absence of coverage here is therefore not evidence about the suite or about our analyzer environment: without a collector, `--collect` produces nothing even from a suite that builds and passes. Add a `coverlet.collector` PackageReference to the test project(s) (or commit the Cobertura/OpenCover/lcov report your CI produces) and real coverage will be measured. It is excluded from the score rather than counted as a near-zero defect. You can widen what we reach: add the `coverlet.collector` package to the test projects to enable coverage (or commit the Cobertura/OpenCover/lcov report your CI produces).
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the test run produced no results for any test tier, so no test ever ran and flakiness could not be exercised. The cause could not be attributed, so it is excluded from the score rather than read as an absence of tests.
D12 Dependency Hygiene — not measured this run — Watchdog 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. The NuGet registry this repository's packages resolve from could not be reached on this run, so no outdated, vulnerable or deprecated package could be read. The tool said: NU1301: Unable to load the service index for source https://nuget.pkg.github.com/CSBiology/index.json. [ProteomIQon.sln] The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'." [ProteomIQon.sln]. This is OUR side and an ENVIRONMENT fault — the collector exists and ran — so the remedy is the scan's network path to nuget.pkg.github.com, and a re-run with it reachable measures this repository.
D15 Churn × Complexity Hotspots — not measured this run — Watchdog 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. A hotspot is churn × complexity. Churn was measured (27290 line(s) across the 90-day window), but no complexity could be computed for .fs, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
D21 Naming Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — evaluation did not complete — Navigability not included (check did not complete) — excluded from the score.
D30 Dependency Vulnerabilities — not measured this run — Watchdog 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. Nuget: nuget.pkg.github.com could not be reached (NU1301: Unable to load the service index for source https://nuget.pkg.github.com/CSBiology/index.json. The proxy tunnel request to proxy 'http://egress:3128/' failed with status code '403'.). The scanner exists and ran; what failed is the scan's network path to the registry, so nothing was read and nothing here is a statement about the repository. A re-run with the registry reachable measures it.
D34 Knowledge Freshness — not measured this run — Watchdog 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. File-level freshness contradicts repo activity: 89 commits in the last 90 days, yet 42 of 64 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
D39 IL Efficiency — not measured this run — Watchdog 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. IL NOT MEASURED: the analyzer's build of this repository exited 1 and the cause could not be attributed, so no assemblies were produced and there was no IL to read. We do not read it as a defect in the repository: an unattributed failure leans OURS. D18 owns the question of whether this repository builds; it was not answered here.
AX6 Interface segregation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
C1 Data Protection — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
DM10 One transaction, one aggregate — not measured this run — Watchdog 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. One transaction, one aggregate could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository. Engine failure: InvalidOperationException: The entity or value 'System.Int32' does not exist or is in an unresolved assembly. You may need to add a reference to assembly 'netstandard'.
DM8 Value-object opportunities — not measured this run — Watchdog 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 finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither.
IC1 Incompleteness & stubs — not measured this run — Watchdog 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.
P8 Schema migrations — not measured this run — Watchdog 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 EF Core usage in C# and the schema tooling its file scan recognises only, and no .NET project was loaded, and this repository's language is not one the scan models, 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.
S1 Web-Security Posture — not measured this run — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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 — Watchdog 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.
Package restore incomplete — third-party types were unresolved in part of the solution — NuGet restore did not complete for src/ProteomIQon/ProteomIQon.fsproj, src/Preprocessing/Preprocessing.fsproj, src/PeptideDB/PeptideDB.fsproj, src/PeptideSpectrumMatching/PeptideSpectrumMatching.fsproj, src/PSMStatistics/PSMStatistics.fsproj and 25 more, so those projects were analysed with framework references only: every check keyed on a third-party type saw an error type there and reported nothing. Findings on those projects are a lower bound; run `dotnet restore` on them and rescan.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
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.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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.
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.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D3 · God Classes8.2 / 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.
Resolve the 9 FileTooLong finding(s) in God Classes — start with PSMBasedQuantificationTIMs.fs, DTO.fs, AlignmentBasedQuantification.fs. — One of this dimension's main actionable groups (9 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
176 duplicated block group(s) detected. A further 13 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 108 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AlignmentBasedQuantification.fs (3), PSMBasedQuantification.fs (3), Program.fs (2). — One of this dimension's main actionable groups (12 warning-level).
Resolve the 7 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with AlignmentBasedQuantification.fs (2), Program.fs, PSMBasedQuantificationTIMs.fs. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with Program.fs (2), AlignmentBasedQuantification.fs, MzMLToMzLite.fs. — One of this dimension's main actionable groups (6 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
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.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 336 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 39 direct `PackageReference`(s), and 34 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
✓ On the Gold path — maintain.
Detailed fixes: d14_recommendation.md.
Do you agree with this assessment?
D16 · Bus Factor6.6 / 10Adequate✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
21 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs. Counted over 62 of the 100 production source files in this repository: 36 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
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.
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).
7 finding(s): 0 critical, 7 high, 0 medium, 0 low. 7 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `docs/_template.ipynb` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
What to do
No action in Static Analysis (SAST) — all 7 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (7 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 32 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with ProteomIQonConsole.fsproj. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
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.
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.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Code Health — Unreviewed-generation residue in this repository's F#: bindings whose whole body still raises a "not implemented" error (NotImplementedException, failwith "not implemented"), and placeholder text (lorem ipsum, changeme/replace_me…) left in string literals of 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.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
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.
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.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
Only 27/30 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `src/QuantBasedAlignment_linux-x64`, `src/QuantBasedAlignment_win-x64`, `src/RatioLFQ`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2044 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. — REDACTED:6
`ConsoleTemplate/template/ProteomIQonConsole.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — ConsoleTemplate/template/ProteomIQonConsole.fsproj:39
What to do
Add a SAST step to CI running what this repository's stack ships: `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) — 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.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 21 use(s) across 24,720 production line(s) (~0.8/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
F#: on hot paths, work through Span/Memory (AsSpan/AsMemory) instead of copies, rent buffers from ArrayPool, make small records, unions and tuples [<Struct>]/struct (…) and options voption, mark lambda parameters of inline functions [<InlineIfLambda>], use valueTask for completions that are usually synchronous, and presize ResizeArray/StringBuilder.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`Trace` at line 99 is called with an argument built by `Array.map (fun x -> string x)` (line 101), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on. (×2) — src/ProteomIQon/pepValueCalculation.fs:99, src/ProteomIQon/pepValue/pepValueCalculation.fs:99
`Trace` at line 105 is called with an argument built by `Array.map (fun x -> string x)` (line 107), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on. (×2) — src/ProteomIQon/pepValueCalculation.fs:105, src/ProteomIQon/pepValue/pepValueCalculation.fs:105
`Trace` at line 111 is called with an argument built by `Array.map (fun x -> string x)` (line 113), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on. — src/ProteomIQon/pepValueCalculation.fs:111
`Trace` at line 93 is called with an argument built by `Array.map (fun x -> string x)` (line 95), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on. — src/ProteomIQon/pepValue/pepValueCalculation.fs:93
`Trace` at line 197 is called with an argument built by `List.map (fun x -> x.DecoyTheoSpec.Length, x.TheoSpec.Length)` (line 197), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on. — src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:197
What to do
In F#, put the construction behind the logger's own check (`if logger.IsEnabled LogLevel.Debug then` for Microsoft.Extensions.Logging, `if Log.IsEnabled LogEventLevel.Debug then` for Serilog), or pass the collection itself as a message-template argument (`logger.LogDebug("Items {Items}", items)`) so the framework renders it only when the line is written. Formatting the message with `sprintf` does not defer it either: the arguments are built before the logger is entered.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for … in` loop leaves the mutable .NET collection it is walking alone — F#'s own lists, arrays, maps and sets cannot be changed by a loop body, but a `ResizeArray`, `Dictionary`, `Queue` or other BCL collection walked by `for x in c do` is walked through its enumerator, so a body that adds to or removes from `c` makes the next `MoveNext` throw `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 88 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.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's F# imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No F# function in this code takes an ASP.NET Core or Suave HttpContext (a Giraffe, Saturn, Falco, Oxpecker or Suave handler) and no F# class is an ASP.NET Core controller, so no request handler shares module state between request threads.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
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.
D1 Cyclomatic Complexity — cyclomatic complexity not measured — .fs exposed no member bodies
D10 Test Quality — ~1624 lines of test source are present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not measured — no test run produced results
D12 Dependency Hygiene — Dependency hygiene not measured — nuget.pkg.github.com could not be reached
D15 Churn × Complexity Hotspots — complexity unreadable for .fs — churn × complexity hotspots could not be measured
D17 Explicit Debt — the C# workspace loaded 0 projects, so explicit-debt density could not be measured
D18 Solution Shape — D18 scores the shape of a C#/VB .NET solution; this repository's .NET projects are all F# (.fsproj), which the C#/VB workspace does not load, so the dimension does not apply.
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.
D2 Cognitive Complexity — cognitive complexity not measured — .fs exposed no member bodies
D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; F# not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .fs, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — Navigability not included (check did not complete)
D30 Dependency Vulnerabilities — Not measured — a package registry could not be reached
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 — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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.
D39 IL Efficiency — IL not measured — the analyzer's build of the target did not succeed
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D6 Cohesion (LCOM4) — cohesion (LCOM4) not measured — the code model exposed no member bodies
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
D8 Code Coverage — Coverage not measured — no coverage collector is wired up
D9 Test Distribution — Test source is present (.fs) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM10 One transaction, one aggregate — One transaction, one aggregate could not be assessed in this run — the check did not complete, so it is not scored. This is a gap in the analyzer, not a finding about this repository.
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 0 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
DM9 Scattered domain decisions — not measured — scattered-decision detection needs expression-level symbol resolution: a comparison operand bound to the member it judges (arm one) and a construction bound to the type it produces (arm two). A Roslyn compilation carries both; arm two alone also runs on any frontend that declares whether a construction is produced or passed, and this target loaded neither
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 — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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.
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
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
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.
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.
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
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
Duplicated block (9 lines × 2) src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:259— src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:259-267 | src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:286-294 — 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 (9 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:437— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:437-445 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:470-478 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:437` it does not close everything it opens, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:446` calls `Point` and `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:479` 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.
Duplicated block (9 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:931— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:931-939 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1084-1092 — 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 (9 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1171— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1171-1179 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1226-1234 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1171` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) src/AlignmentBasedQuantification/Program.fs:8— src/AlignmentBasedQuantification/Program.fs:8-16 | src/SWATHAnalysis/Program.fs:8-16 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:256— src/PSMBasedQuantification/PSMBasedQuantification.fs:256-264 | src/ProteomIQon/BioFSharp.Mz_Temp.fs:321-329 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ProteomIQon/BioFSharp.Mz_Temp.fs:321` 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. 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.
Duplicated block (9 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:730— src/PSMBasedQuantification/PSMBasedQuantification.fs:730-738 | src/PSMBasedQuantification/PSMBasedQuantification.fs:877-885 — 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 (9 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:961— src/PSMBasedQuantification/PSMBasedQuantification.fs:961-969 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1014-1022 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:961` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2605— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2605-2613 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2752-2760 — 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 (9 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2836— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2836-2844 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2889-2897 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2836` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) src/PSMStatistics/PSMStatistics.fs:342— src/PSMStatistics/PSMStatistics.fs:342-350 | src/PSMStatistics/PSMStatistics.fs:446-454 — 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 (9 lines × 2) src/PSMStatistics/Program.fs:51— src/PSMStatistics/Program.fs:51-59 | src/PeptideSpectrumMatching/Program.fs:49-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMStatistics/Program.fs:51` 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.
FileTooLong: PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs— FileTooLong — 2472 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 74 functions. The bar is 500 significant lines; this is 1972 over it, 4.94× 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: ProteomIQon/DTO.fs src/ProteomIQon/DTO.fs— FileTooLong — 1322 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 822 over it, 2.64× 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: AlignmentBasedQuantification/AlignmentBasedQuantification.fs src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs— FileTooLong — 1194 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 694 over it, 2.39× 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: MzTAB/MzTABSections.fs src/MzTAB/MzTABSections.fs— FileTooLong — 1046 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 546 over it, 2.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: PSMBasedQuantification/PSMBasedQuantification.fs src/PSMBasedQuantification/PSMBasedQuantification.fs— FileTooLong — 1012 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 512 over it, 2.02× 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: QuantBasedAlignment/QuantBasedAlignment.fs src/QuantBasedAlignment/QuantBasedAlignment.fs— FileTooLong — 808 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 308 over it, 1.62× 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: ProteomIQon/BioFSharp.Mz_Temp.fs src/ProteomIQon/BioFSharp.Mz_Temp.fs— FileTooLong — 670 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 170 over it, 1.34× 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: PeptideSpectrumMatchingTIMs/PeptideSpectrumMatchingTIMs.fs src/PeptideSpectrumMatchingTIMs/PeptideSpectrumMatchingTIMs.fs— FileTooLong — 662 significant lines (blank, comment-only and punctuation-only lines excluded), declaring 37 functions. The bar is 500 significant lines; this is 162 over it, 1.32× 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: PSMStatistics/PSMStatistics.fs src/PSMStatistics/PSMStatistics.fs— FileTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 24 over it, 1.05× 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.
Duplicated block (7 lines × 2) ConsoleTemplate/template/Program.fs:19— ConsoleTemplate/template/Program.fs:19-25 | src/LabelEfficiencyCalculator/Program.fs:18-24 — before extracting anything, compare `ConsoleTemplate/template/Program.fs` and `src/LabelEfficiencyCalculator/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:22— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:22-28 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:20-26 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:837— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:837-843 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:904-910 — 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) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2319— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2319-2325 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2506-2512 — 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) src/ProteomIQon/pepValue/pepValueCalculation.fs:210— src/ProteomIQon/pepValue/pepValueCalculation.fs:210-216 | src/ProteomIQon/pepValueCalculation.fs:223-229 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:211— src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:211-217 | src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:221-227 — 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) src/PSMBasedQuantification/PSMBasedQuantification.fs:705— src/PSMBasedQuantification/PSMBasedQuantification.fs:705-711 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2580-2586 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:687— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:687-694 | src/PSMBasedQuantification/PSMBasedQuantification.fs:528-535 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) src/MzMLToMzLite/MzMLToMzLite.fs:57— src/MzMLToMzLite/MzMLToMzLite.fs:57-64 | src/Preprocessing/Preprocessing.fs:61-68 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/Preprocessing/Preprocessing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) src/PeptideSpectrumMatching/Program.fs:20— src/PeptideSpectrumMatching/Program.fs:20-27 | src/PeptideSpectrumMatchingTIMs/Program.fs:19-26 — `src/PeptideSpectrumMatching/Program.fs` and `src/PeptideSpectrumMatchingTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 31 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 2) src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:371— src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:371-378 | src/SpectralLibrary/SpectralLibrary.fs:144-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/PeptideSpectrumMatching/CLIArgumentParsing.fs:19— src/PeptideSpectrumMatching/CLIArgumentParsing.fs:19-26 | src/PeptideSpectrumMatchingTIMs/CLIArgumentParsing.fs:19-26 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) src/AlignmentBasedQuantification/Program.fs:88— src/AlignmentBasedQuantification/Program.fs:88-95 | src/SWATHAnalysis/Program.fs:71-78 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:36— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:36-41 | src/PSMBasedQuantification/PSMBasedQuantification.fs:30-35 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) src/AlignmentBasedQuantification/Program.fs:25— src/AlignmentBasedQuantification/Program.fs:25-30 | src/SWATHAnalysis/Program.fs:23-28 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:181— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:181-186 | src/SWATHAnalysis/SWATHAnalysis.fs:109-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:181` 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.
Duplicated block (6 lines × 2) src/LabeledProteinQuantification/LabeledProteinQuantification.fs:32— src/LabeledProteinQuantification/LabeledProteinQuantification.fs:32-37 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:122-127 — 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 before the matched lines, `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:29` calls `zip` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:118` 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.
Duplicated block (6 lines × 2) src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs:128— src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs:128-133 | src/ProteomIQon/Core.fs:145-150 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) src/ProteomIQon/DeedleExtensionsTemp.fs:239— src/ProteomIQon/DeedleExtensionsTemp.fs:239-244 | src/ProteomIQon/DeedleExtensionsTemp.fs:255-260 — 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. 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, `src/ProteomIQon/DeedleExtensionsTemp.fs:261` calls `r` and `src/ProteomIQon/DeedleExtensionsTemp.fs:244` 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.
Duplicated block (5 lines × 2) src/LabeledProteinQuantification/LabeledProteinQuantification.fs:76— src/LabeledProteinQuantification/LabeledProteinQuantification.fs:76-80 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:116-121 — 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 (5 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:271— src/PSMBasedQuantification/PSMBasedQuantification.fs:271-275 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1742-1746 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 2) src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:252— src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:252-256 | src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:279-283 — 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 (5 lines × 2) src/QuantBasedAlignment/QuantBasedAlignment.fs:670— src/QuantBasedAlignment/QuantBasedAlignment.fs:670-674 | src/QuantBasedAlignment/QuantBasedAlignment.fs:682-686 — 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 (5 lines × 2) src/PeptideSpectrumMatchingTIMs/SpectrumSearch.fs:416— src/PeptideSpectrumMatchingTIMs/SpectrumSearch.fs:416-420 | src/PeptideSpectrumMatchingTIMs/SpectrumSearch.fs:428-432 — 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 (5 lines × 2) src/ProteomIQon/Core.fs:114— src/ProteomIQon/Core.fs:114-118 | src/ProteomIQon/Core.fs:123-127 — 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· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×4
Members sharing a duplicated core (6 members, 50+ identical tokens) ConsoleTemplate/template/Program.fs:1— ConsoleTemplate/template/Program.fs:1-40 | src/LabelEfficiencyCalculator/Program.fs:1-37 | src/MzMLToMzLite/Program.fs:1-62 | src/MzMLToMzLiteIonMobility/Program.fs:1-63 | src/PeptideSpectrumMatching/Program.fs:1-63 | src/PeptideSpectrumMatchingTIMs/Program.fs:1-84 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/AlignmentBasedQuantification/Program.fs:1— src/AlignmentBasedQuantification/Program.fs:1-104 | src/PSMBasedQuantification/Program.fs:1-90 | src/PSMBasedQuantificationTIMs/Program.fs:1-90 | src/PeptideSpectrumMatching/Program.fs:1-63 | src/PeptideSpectrumMatchingTIMs/Program.fs:1-84 | src/SWATHAnalysis/Program.fs:1-87 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/AlignmentBasedQuantification/Program.fs:1— src/AlignmentBasedQuantification/Program.fs:1-104 | src/ConsensusSpectralLibrary/Program.fs:1-50 | src/MzliteToMzML/Program.fs:1-61 | src/Preprocessing/Program.fs:1-61 | src/SWATHAnalysis/Program.fs:1-87 | src/SpectralLibrary/Program.fs:1-100 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) src/ConsensusSpectralLibrary/Program.fs:1— src/ConsensusSpectralLibrary/Program.fs:1-50 | src/MzTAB/Program.fs:1-41 | src/PeptideDB/Program.fs:1-32 | src/Preprocessing/Program.fs:1-61 | src/ProteinInference/Program.fs:1-55 | src/SpectralLibrary/Program.fs:1-100 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (18 lines × 2) ConsoleTemplate/template/CLIArgumentParsing.fs:1— ConsoleTemplate/template/CLIArgumentParsing.fs:1-18 | src/LabelEfficiencyCalculator/CLIArgumentParsing.fs:1-18 — before extracting anything, compare `ConsoleTemplate/template/CLIArgumentParsing.fs` and `src/LabelEfficiencyCalculator/CLIArgumentParsing.fs` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) src/AlignmentBasedQuantStatistics/Program.fs:57— src/AlignmentBasedQuantStatistics/Program.fs:57-74 | src/AlignmentBasedQuantStatistics/Program.fs:142-159 — 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 (18 lines × 2) src/LabelFreeProteinQuantification/CLIArgumentParsing.fs:1— src/LabelFreeProteinQuantification/CLIArgumentParsing.fs:1-18 | src/LabeledProteinQuantification/CLIArgumentParsing.fs:1-18 — `src/LabelFreeProteinQuantification/CLIArgumentParsing.fs` and `src/LabeledProteinQuantification/CLIArgumentParsing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 18 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (18 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:31— src/ProteomIQon/pepValue/pepValueCalculation.fs:31-48 | src/ProteomIQon/pepValueCalculation.fs:31-48 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:87— src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:87-102 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:189-204 — `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:87` it does not close everything it opens, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:103` calls `filter` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:205` 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.
Duplicated block (16 lines × 2) src/MzMLToMzLiteIonMobility/Program.fs:1— src/MzMLToMzLiteIonMobility/Program.fs:1-16 | src/RatioLFQ/Program.fs:1-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) src/ProteomIQon/DTO.fs:1056— src/ProteomIQon/DTO.fs:1056-1071 | src/ProteomIQon/DTO.fs:1074-1089 — 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 (16 lines × 2) src/QuantBasedAlignment/QuantBasedAlignment.fs:252— src/QuantBasedAlignment/QuantBasedAlignment.fs:252-267 | src/QuantBasedAlignment/QuantBasedAlignment.fs:306-321 — 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 (13 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:311— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:311-323 | src/SWATHAnalysis/SWATHAnalysis.fs:376-388 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:311` it does not close everything it opens, 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.
Duplicated block (13 lines × 2) src/MzMLToMzLite/MzMLToMzLite.fs:131— src/MzMLToMzLite/MzMLToMzLite.fs:131-143 | src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs:185-197 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:815— src/PSMBasedQuantification/PSMBasedQuantification.fs:815-827 | src/PSMBasedQuantification/PSMBasedQuantification.fs:962-974 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:815` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (13 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2690— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2690-2702 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2837-2849 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2690` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) src/MzMLToMzLite/Program.fs:43— src/MzMLToMzLite/Program.fs:43-54 | src/MzMLToMzLiteIonMobility/Program.fs:44-55 — `src/MzMLToMzLite/Program.fs` and `src/MzMLToMzLiteIonMobility/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/MzMLToMzLite/Program.fs:43` 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.
Duplicated block (12 lines × 2) src/MzTAB/MzTABSections.fs:710— src/MzTAB/MzTABSections.fs:710-721 | src/MzTAB/MzTABSections.fs:723-734 — 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 (12 lines × 2) src/MzTAB/MzTABSections.fs:312— src/MzTAB/MzTABSections.fs:312-323 | src/MzTAB/MzTABSections.fs:349-360 — 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 (12 lines × 2) src/MzTAB/MzTABSections.fs:288— src/MzTAB/MzTABSections.fs:288-299 | src/MzTAB/MzTABSections.fs:325-336 — 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 (10 lines × 2) ConsoleTemplate/template/Program.fs:27— ConsoleTemplate/template/Program.fs:27-36 | src/LabelEfficiencyCalculator/Program.fs:26-35 — before extracting anything, compare `ConsoleTemplate/template/Program.fs` and `src/LabelEfficiencyCalculator/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `ConsoleTemplate/template/Program.fs:37` calls `GetAllResults` and `src/LabelEfficiencyCalculator/Program.fs:36` 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 (10 lines × 2) src/LabelEfficiencyCalculator/LabelEfficiencyCalculator.fs:134— src/LabelEfficiencyCalculator/LabelEfficiencyCalculator.fs:134-143 | src/LabelEfficiencyCalculator/LabelEfficiencyCalculator.fs:147-156 — 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 (10 lines × 2) src/ProteinInference/Program.fs:37— src/ProteinInference/Program.fs:37-46 | src/SpectralLibrary/Program.fs:34-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:602— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:602-612 | src/SWATHAnalysis/SWATHAnalysis.fs:450-459 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. 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.
Duplicated block (9 lines × 4) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:152— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:152-160 | src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:457-465 | src/PSMBasedQuantification/PSMBasedQuantification.fs:100-108 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:151-159 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:152` 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.
Duplicated block (9 lines × 4) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:165— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:165-173 | src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:474-482 | src/PSMBasedQuantification/PSMBasedQuantification.fs:113-121 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:164-172 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 4) src/MzMLToMzLite/Program.fs:46— src/MzMLToMzLite/Program.fs:46-54 | src/MzMLToMzLiteIonMobility/Program.fs:47-55 | src/MzliteToMzML/Program.fs:43-51 | src/Preprocessing/Program.fs:43-51 — `src/MzMLToMzLite/Program.fs` and `src/MzMLToMzLiteIonMobility/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 4) src/PSMBasedQuantification/Program.fs:9— src/PSMBasedQuantification/Program.fs:9-17 | src/PSMBasedQuantificationTIMs/Program.fs:9-17 | src/PeptideSpectrumMatching/Program.fs:9-17 | src/PeptideSpectrumMatchingTIMs/Program.fs:8-16 — `src/PSMBasedQuantification/Program.fs` and `src/PSMBasedQuantificationTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 108 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1-1388 | src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:1-667 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1-1180 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1-3063 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1-1388 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1-1180 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1-3063 | src/PSMStatistics/PSMStatistics.fs:1-609 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) src/MzMLToMzLite/Program.fs:1— src/MzMLToMzLite/Program.fs:1-62 | src/MzMLToMzLiteIonMobility/Program.fs:1-63 | src/MzliteToMzML/Program.fs:1-61 | src/Preprocessing/Program.fs:1-61 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (15 lines × 2) src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:170— src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:170-184 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:278-292 — `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) src/MzTAB/MzTABSections.fs:585— src/MzTAB/MzTABSections.fs:585-599 | src/MzTAB/MzTABSections.fs:603-617 — 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 (15 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:339— src/PSMBasedQuantification/PSMBasedQuantification.fs:339-353 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1814-1828 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) src/LabelFreeProteinQuantification/Program.fs:17— src/LabelFreeProteinQuantification/Program.fs:17-30 | src/LabeledProteinQuantification/Program.fs:17-30 — `src/LabelFreeProteinQuantification/Program.fs` and `src/LabeledProteinQuantification/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 2) src/LabeledProteinQuantification/LabeledProteinQuantification.fs:61— src/LabeledProteinQuantification/LabeledProteinQuantification.fs:61-74 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:98-111 — 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 (14 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2328— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2328-2341 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2400-2413 — 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 (11 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:652— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:652-662 | src/PSMBasedQuantification/PSMBasedQuantification.fs:509-519 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1986-1996 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 3) src/MzTAB/MzTABSections.fs:200— src/MzTAB/MzTABSections.fs:200-210 | src/MzTAB/MzTABSections.fs:214-224 | src/MzTAB/MzTABSections.fs:228-238 — 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.
Duplicated block (11 lines × 3) src/MzTAB/MzTABSections.fs:710— src/MzTAB/MzTABSections.fs:710-720 | src/MzTAB/MzTABSections.fs:723-733 | src/MzTAB/MzTABSections.fs:736-746 — 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.
Duplicated block (11 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:905— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:905-915 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1246-1256 — 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 (11 lines × 2) src/MzMLToMzLite/MzMLToMzLite.fs:153— src/MzMLToMzLite/MzMLToMzLite.fs:153-163 | src/Preprocessing/Preprocessing.fs:179-189 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/Preprocessing/Preprocessing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2307— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2307-2317 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2494-2504 — 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· Members sharing a duplicated core (8 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (8 members, 50+ identical tokens) ConsoleTemplate/template/Program.fs:1— ConsoleTemplate/template/Program.fs:1-40 | src/AddDeducedPeptides/Program.fs:1-40 | src/AlignmentBasedQuantStatistics/Program.fs:1-233 | src/JoinQuantPepIonsWithProteins/Program.fs:1-56 | src/LabelEfficiencyCalculator/Program.fs:1-37 | src/LabelFreeProteinQuantification/Program.fs:1-38 | src/LabeledProteinQuantification/Program.fs:1-38 | src/MzliteToMzML/Program.fs:1-61 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Members sharing a duplicated core (8 members, 50+ identical tokens) src/AlignmentBasedQuantification/CLIArgumentParsing.fs:1— src/AlignmentBasedQuantification/CLIArgumentParsing.fs:1-37 | src/PSMBasedQuantification/CLIArgumentParsing.fs:1-34 | src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs:1-34 | src/PSMStatistics/CLIArgumentParsing.fs:1-32 | src/PeptideSpectrumMatching/CLIArgumentParsing.fs:1-30 | src/PeptideSpectrumMatchingTIMs/CLIArgumentParsing.fs:1-34 | src/QuantBasedAlignment/CLIArgumentParsing.fs:1-28 | src/SWATHAnalysis/CLIArgumentParsing.fs:1-33 — These 8 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 8 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 8 times.
Duplicated block (46 lines × 2) src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:99— src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:99-144 | src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:162-207 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantStatistics/AlignmentBasedQuantStatistics.fs:99` it does not close everything it opens, 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.
Duplicated block (46 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:77— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:77-122 | src/ProteomIQon/DTO.fs:1173-1218 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:77` it does not close everything it opens, 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.
Duplicated block (24 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1044— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1044-1067 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1287-1310 — 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 (24 lines × 2) src/MzMLToMzLite/Program.fs:18— src/MzMLToMzLite/Program.fs:18-41 | src/MzMLToMzLiteIonMobility/Program.fs:19-42 — `src/MzMLToMzLite/Program.fs` and `src/MzMLToMzLiteIonMobility/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:305— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:305-324 | src/PSMBasedQuantification/PSMBasedQuantification.fs:216-235 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:333-352 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20 lines × 3) src/PSMBasedQuantification/Program.fs:65— src/PSMBasedQuantification/Program.fs:65-84 | src/PSMBasedQuantificationTIMs/Program.fs:65-84 | src/SWATHAnalysis/Program.fs:59-78 — `src/PSMBasedQuantification/Program.fs` and `src/PSMBasedQuantificationTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 108 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19 lines × 2) src/PSMBasedQuantification/CLIArgumentParsing.fs:16— src/PSMBasedQuantification/CLIArgumentParsing.fs:16-34 | src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs:16-34 — `src/PSMBasedQuantification/CLIArgumentParsing.fs` and `src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (19 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:218— src/ProteomIQon/pepValue/pepValueCalculation.fs:218-236 | src/ProteomIQon/pepValueCalculation.fs:231-249 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:548— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:548-563 | src/PSMBasedQuantification/PSMBasedQuantification.fs:322-337 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1797-1812 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (16 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:993— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:993-1008 | src/PSMBasedQuantification/PSMBasedQuantification.fs:789-804 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2664-2679 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:560— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:560-574 | src/PSMBasedQuantification/PSMBasedQuantification.fs:423-437 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1900-1914 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:423` 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.
Duplicated block (15 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:696— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:696-710 | src/PSMBasedQuantification/PSMBasedQuantification.fs:556-570 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2048-2062 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 2) src/PSMStatistics/PSMStatistics.fs:516— src/PSMStatistics/PSMStatistics.fs:516-528 | src/PSMStatistics/PSMStatistics.fs:586-599 — 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. 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.
Duplicated block (13–14 lines × 2) src/ProteomIQon/BioFSharp.Mz_Temp.fs:227— src/ProteomIQon/BioFSharp.Mz_Temp.fs:227-240 | src/ProteomIQon/BioFSharp.Mz_Temp.fs:248-260 — 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 (4–11 lines × 4) src/AlignmentBasedQuantification/CLIArgumentParsing.fs:14— src/AlignmentBasedQuantification/CLIArgumentParsing.fs:14-17 | src/PSMBasedQuantification/CLIArgumentParsing.fs:1-11 | src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs:1-11 | src/SWATHAnalysis/CLIArgumentParsing.fs:12-15 — `src/PSMBasedQuantification/CLIArgumentParsing.fs` and `src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (4–11 lines × 4) src/PSMBasedQuantification/PSMBasedQuantification.fs:725— src/PSMBasedQuantification/PSMBasedQuantification.fs:725-735 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1049-1052 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2600-2609 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2924-2927 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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 before the matched lines, `src/PSMBasedQuantification/PSMBasedQuantification.fs:724` calls `Trace`, `sprintf`, `filter` and `src/PSMBasedQuantification/PSMBasedQuantification.fs:1049` 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.
Duplicated block (9 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:619— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:619-627 | src/PSMBasedQuantification/PSMBasedQuantification.fs:482-490 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1959-1967 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:629— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:629-638 | src/PSMBasedQuantification/PSMBasedQuantification.fs:492-500 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1969-1977 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (7 lines × 3) src/MzMLToMzLite/MzMLToMzLite.fs:66— src/MzMLToMzLite/MzMLToMzLite.fs:66-72 | src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs:61-67 | src/Preprocessing/Preprocessing.fs:70-76 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 3) src/PSMBasedQuantification/PSMBasedQuantification.fs:513— src/PSMBasedQuantification/PSMBasedQuantification.fs:513-519 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1990-1996 | src/PSMStatistics/PSMStatistics.fs:203-209 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:851— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:851-855 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:918-922 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1259-1263 — 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.
Duplicated block (5 lines × 3) src/LabeledProteinQuantification/LabeledProteinQuantification.fs:33— src/LabeledProteinQuantification/LabeledProteinQuantification.fs:33-37 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:83-87 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:123-127 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:29` calls `zip` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:78` 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 (4–5 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:859— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:859-863 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:926-929 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1267-1271 — 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. 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.
Duplicated block (4–5 lines × 3) src/LabeledProteinQuantification/LabeledProteinQuantification.fs:54— src/LabeledProteinQuantification/LabeledProteinQuantification.fs:54-57 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:92-96 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:132-137 — 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. 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.
Near-duplicate member pair (268 shared lines) src/ProteomIQon/pepValue/pepValueCalculation.fs:18— src/ProteomIQon/pepValue/pepValueCalculation.fs:18-390 | src/ProteomIQon/pepValueCalculation.fs:18-437 — These two members are variants of one another: 268 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (115 shared lines) src/MzMLToMzLite/MzMLToMzLite.fs:1— src/MzMLToMzLite/MzMLToMzLite.fs:1-230 | src/Preprocessing/Preprocessing.fs:1-245 — These two members are variants of one another: 115 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (48 shared lines) src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:1— src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:1-187 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:1-295 — These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) src/AlignmentBasedQuantification/Program.fs:1— src/AlignmentBasedQuantification/Program.fs:1-104 | src/JoinQuantPepIonsWithProteins/Program.fs:1-56 | src/PSMBasedQuantification/Program.fs:1-90 | src/PSMBasedQuantificationTIMs/Program.fs:1-90 | src/SWATHAnalysis/Program.fs:1-87 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. 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. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (97–102 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:241— src/ProteomIQon/pepValue/pepValueCalculation.fs:241-337 | src/ProteomIQon/pepValueCalculation.fs:254-355 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (82 lines × 2) src/ProteomIQon/DTO.fs:876— src/ProteomIQon/DTO.fs:876-957 | src/ProteomIQon/DTO.fs:1314-1395 — 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 (75–76 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:126— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:126-201 | src/PSMBasedQuantification/PSMBasedQuantification.fs:75-149 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:126-200 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:75` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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.
Duplicated block (66–67 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:628— src/PSMBasedQuantification/PSMBasedQuantification.fs:628-694 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2120-2185 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:628` 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. 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.
Duplicated block (61–62 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:59— src/ProteomIQon/pepValue/pepValueCalculation.fs:59-120 | src/ProteomIQon/pepValueCalculation.fs:66-126 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (56 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:188— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:188-243 | src/SWATHAnalysis/SWATHAnalysis.fs:118-173 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (53 lines × 2) src/PSMBasedQuantification/Program.fs:19— src/PSMBasedQuantification/Program.fs:19-71 | src/PSMBasedQuantificationTIMs/Program.fs:19-71 — `src/PSMBasedQuantification/Program.fs` and `src/PSMBasedQuantificationTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 108 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/Program.fs:19` it does not close everything it opens, 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.
Duplicated block (48–49 lines × 2) src/ProteinInference/ProteinInference.fs:320— src/ProteinInference/ProteinInference.fs:320-368 | src/ProteinInference/ProteinInference.fs:442-489 — 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. 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.
Duplicated block (46–48 lines × 2) src/ProteomIQon/DTO.fs:596— src/ProteomIQon/DTO.fs:596-643 | src/ProteomIQon/DTO.fs:763-808 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/ProteomIQon/DTO.fs:596` it does not close everything it opens, 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.
Duplicated block (40–41 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:1141— src/PSMBasedQuantification/PSMBasedQuantification.fs:1141-1180 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:3023-3063 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:1141` 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.
Duplicated block (40 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:492— src/PSMBasedQuantification/PSMBasedQuantification.fs:492-531 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1969-2008 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (39 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2360— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2360-2398 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2432-2470 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2360` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (38 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:576— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:576-613 | src/PSMBasedQuantification/PSMBasedQuantification.fs:439-476 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1916-1953 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:576` it does not close everything it opens, 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.
Duplicated block (38 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:537— src/PSMBasedQuantification/PSMBasedQuantification.fs:537-574 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2029-2066 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (36 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:977— src/PSMBasedQuantification/PSMBasedQuantification.fs:977-1012 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2852-2887 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (35–36 lines × 2) src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:237— src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:237-271 | src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:274-309 — 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 (35 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:503— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:503-537 | src/PSMBasedQuantification/PSMBasedQuantification.fs:372-406 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1847-1881 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:503` it does not close everything it opens, 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.
Duplicated block (34 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:775— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:775-808 | src/PSMBasedQuantification/PSMBasedQuantification.fs:600-633 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2092-2125 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (34 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:125— src/ProteomIQon/pepValue/pepValueCalculation.fs:125-158 | src/ProteomIQon/pepValueCalculation.fs:131-164 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (31–32 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:404— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:404-435 | src/PSMBasedQuantification/PSMBasedQuantification.fs:291-321 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1766-1796 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (31 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:959— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:959-989 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1112-1142 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:959` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (3–31 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1163— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1163-1165 | src/PSMBasedQuantification/PSMBasedQuantification.fs:924-954 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2799-2829 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (29–30 lines × 2) src/MzMLToMzLite/MzMLToMzLite.fs:101— src/MzMLToMzLite/MzMLToMzLite.fs:101-129 | src/Preprocessing/Preprocessing.fs:134-163 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/Preprocessing/Preprocessing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (29 lines × 3) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2347— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2347-2375 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2419-2447 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2520-2548 — 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 `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2347` it does not close everything it opens, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2417` calls `quantMzHeavy` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2345` 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 (28 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:235— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:235-262 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:283-310 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:235` 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. 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.
Duplicated block (27 lines × 4) src/PSMBasedQuantification/PSMBasedQuantification.fs:758— src/PSMBasedQuantification/PSMBasedQuantification.fs:758-784 | src/PSMBasedQuantification/PSMBasedQuantification.fs:905-931 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2633-2659 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2780-2806 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:758` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (25–26 lines × 2) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:48— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:48-73 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:33-57 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 575 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (26 lines × 2) src/MzMLToMzLite/CLIArgumentParsing.fs:1— src/MzMLToMzLite/CLIArgumentParsing.fs:1-26 | src/MzMLToMzLiteIonMobility/CLIArgumentParsing.fs:1-26 — `src/MzMLToMzLite/CLIArgumentParsing.fs` and `src/MzMLToMzLiteIonMobility/CLIArgumentParsing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 26 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (25 lines × 6) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:948— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:948-972 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1101-1125 | src/PSMBasedQuantification/PSMBasedQuantification.fs:747-771 | src/PSMBasedQuantification/PSMBasedQuantification.fs:894-918 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2622-2646 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2769-2793 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (22–23 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:324— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:324-345 | src/PSMBasedQuantification/PSMBasedQuantification.fs:235-256 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1705-1727 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 3) src/MzMLToMzLite/MzMLToMzLite.fs:31— src/MzMLToMzLite/MzMLToMzLite.fs:31-53 | src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs:29-51 | src/Preprocessing/Preprocessing.fs:35-57 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/MzMLToMzLiteIonMobility/MzMLToMzLiteIonMobility.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 43 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (23 lines × 2) src/MzMLToMzLite/MzMLToMzLite.fs:66— src/MzMLToMzLite/MzMLToMzLite.fs:66-88 | src/Preprocessing/Preprocessing.fs:70-92 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/Preprocessing/Preprocessing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (22 lines × 4) src/PSMBasedQuantification/PSMBasedQuantification.fs:837— src/PSMBasedQuantification/PSMBasedQuantification.fs:837-858 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1067-1088 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2712-2733 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2942-2963 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (21–22 lines × 3) src/MzMLToMzLite/MzMLToMzLite.fs:183— src/MzMLToMzLite/MzMLToMzLite.fs:183-203 | src/MzliteToMzML/MzliteToMzML.fs:49-70 | src/Preprocessing/Preprocessing.fs:203-223 — `src/MzMLToMzLite/MzMLToMzLite.fs` and `src/Preprocessing/Preprocessing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 7 separate duplicated blocks between them, totalling at least 124 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (22 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:164— src/ProteomIQon/pepValue/pepValueCalculation.fs:164-185 | src/ProteomIQon/pepValueCalculation.fs:170-191 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (20–21 lines × 6) src/PSMBasedQuantification/PSMBasedQuantification.fs:777— src/PSMBasedQuantification/PSMBasedQuantification.fs:777-796 | src/PSMBasedQuantification/PSMBasedQuantification.fs:830-850 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1060-1080 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2652-2671 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2705-2725 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2935-2955 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (20–21 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:981— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:981-1000 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1037-1057 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1280-1300 — 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.
Duplicated block (19–20 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:274— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:274-292 | src/PSMBasedQuantification/PSMBasedQuantification.fs:190-209 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:306-325 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:274` 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. 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.
Duplicated block (19–20 lines × 2) src/ProteinInference/ProteinInference.fs:299— src/ProteinInference/ProteinInference.fs:299-318 | src/ProteinInference/ProteinInference.fs:422-440 — 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 (9–19 lines × 2) src/ProteomIQon/pepValue/pepValueCalculation.fs:198— src/ProteomIQon/pepValue/pepValueCalculation.fs:198-206 | src/ProteomIQon/pepValueCalculation.fs:204-222 — before extracting anything, compare `src/ProteomIQon/pepValue/pepValueCalculation.fs` and `src/ProteomIQon/pepValueCalculation.fs` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 283 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Duplicated block (17–18 lines × 2) src/AlignmentBasedQuantStatistics/Program.fs:76— src/AlignmentBasedQuantStatistics/Program.fs:76-92 | src/AlignmentBasedQuantStatistics/Program.fs:188-205 — 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 (16–17 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1030— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1030-1045 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1181-1197 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1273-1288 — 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 `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1030` it does not close everything it opens, 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.
Duplicated block (17 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:9— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:9-25 | src/SWATHAnalysis/SWATHAnalysis.fs:11-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 6) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1049— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1049-1064 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1292-1307 | src/PSMBasedQuantification/PSMBasedQuantification.fs:842-857 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1072-1087 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2717-2732 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2947-2962 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15–16 lines × 5) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:977— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:977-991 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1033-1047 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1130-1145 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1185-1200 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1276-1290 — all 5 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 `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:977` it does not close everything it opens, 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. 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.
Duplicated block (15–16 lines × 2) src/PSMBasedQuantification/PSMBasedQuantification.fs:1113— src/PSMBasedQuantification/PSMBasedQuantification.fs:1113-1128 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2991-3005 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/PSMBasedQuantification/PSMBasedQuantification.fs:1113` it does not close everything it opens, 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.
Duplicated block (15 lines × 5) src/PSMBasedQuantification/PSMBasedQuantification.fs:846— src/PSMBasedQuantification/PSMBasedQuantification.fs:846-860 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1076-1090 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2542-2556 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2721-2735 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2951-2965 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 4) src/LabelEfficiencyCalculator/Program.fs:1— src/LabelEfficiencyCalculator/Program.fs:1-15 | src/LabelFreeProteinQuantification/Program.fs:1-15 | src/LabeledProteinQuantification/Program.fs:1-15 | src/MzliteToMzML/Program.fs:1-15 — `src/LabelFreeProteinQuantification/Program.fs` and `src/LabeledProteinQuantification/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 36 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14–15 lines × 2) src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:401— src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:401-414 | src/SpectralLibrary/SpectralLibrary.fs:245-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:401` it does not close everything it opens, 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. 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.
Duplicated block (5–15 lines × 2) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2480— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2480-2494 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2904-2908 — 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. 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.
Duplicated block (13–14 lines × 10) src/PSMBasedQuantification/PSMBasedQuantification.fs:775— src/PSMBasedQuantification/PSMBasedQuantification.fs:775-787 | src/PSMBasedQuantification/PSMBasedQuantification.fs:828-840 | src/PSMBasedQuantification/PSMBasedQuantification.fs:922-935 | src/PSMBasedQuantification/PSMBasedQuantification.fs:975-988 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1058-1070 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2650-2662 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2703-2715 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2797-2810 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2850-2863 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2933-2945 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 6) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1067— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1067-1079 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1310-1322 | src/PSMBasedQuantification/PSMBasedQuantification.fs:860-873 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1090-1103 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2735-2747 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2965-2977 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13–14 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1011— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1011-1023 | src/PSMBasedQuantification/PSMBasedQuantification.fs:807-820 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2682-2694 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (14 lines × 3) src/MzTAB/Program.fs:1— src/MzTAB/Program.fs:1-14 | src/PeptideDB/Program.fs:1-14 | src/Preprocessing/Program.fs:1-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5–14 lines × 4) src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:67— src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:67-78 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:140-144 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:147-151 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:155-168 — `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:67` it does not close everything it opens, 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. 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.
Duplicated block (4–13 lines × 5) src/AlignmentBasedQuantStatistics/Program.fs:104— src/AlignmentBasedQuantStatistics/Program.fs:104-116 | src/AlignmentBasedQuantStatistics/Program.fs:122-134 | src/AlignmentBasedQuantStatistics/Program.fs:168-180 | src/AlignmentBasedQuantStatistics/Program.fs:214-226 | src/AlignmentBasedQuantification/Program.fs:68-71 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantStatistics/Program.fs:104` 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. 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 before the matched lines, `src/AlignmentBasedQuantStatistics/Program.fs:103` calls `tryFind` and `src/AlignmentBasedQuantification/Program.fs:68` 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.
Duplicated block (12–13 lines × 2) src/PSMStatistics/PSMStatistics.fs:503— src/PSMStatistics/PSMStatistics.fs:503-514 | src/PSMStatistics/PSMStatistics.fs:573-585 — 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. 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.
Duplicated block (11–12 lines × 2) src/AlignmentBasedQuantification/Program.fs:41— src/AlignmentBasedQuantification/Program.fs:41-51 | src/SWATHAnalysis/Program.fs:39-50 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (10 lines × 4) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:447— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:447-456 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:479-488 | src/PSMBasedQuantification/PSMBasedQuantification.fs:347-356 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1822-1831 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:447` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:444` calls `Point` and `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:476` 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 (9–10 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:640— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:640-649 | src/PSMBasedQuantification/PSMBasedQuantification.fs:501-509 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1978-1986 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (10 lines × 3) src/PSMBasedQuantification/Program.fs:8— src/PSMBasedQuantification/Program.fs:8-17 | src/PSMBasedQuantificationTIMs/Program.fs:8-17 | src/PeptideSpectrumMatching/Program.fs:8-17 — `src/PSMBasedQuantification/Program.fs` and `src/PSMBasedQuantificationTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 108 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (9–10 lines × 2) src/ProteomIQon/DTO.fs:1585— src/ProteomIQon/DTO.fs:1585-1593 | src/ProteomIQon/Domain.fs:550-559 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `src/ProteomIQon/DTO.fs:1585` it does not close everything it opens, 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.
Duplicated block (7–8 lines × 6) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1170— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1170-1176 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1225-1231 | src/PSMBasedQuantification/PSMBasedQuantification.fs:960-967 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1013-1020 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2835-2841 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2888-2894 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 6) src/AlignmentBasedQuantification/Program.fs:9— src/AlignmentBasedQuantification/Program.fs:9-16 | src/PSMBasedQuantification/Program.fs:10-17 | src/PSMBasedQuantificationTIMs/Program.fs:10-17 | src/PeptideSpectrumMatching/Program.fs:10-17 | src/PeptideSpectrumMatchingTIMs/Program.fs:9-16 | src/SWATHAnalysis/Program.fs:9-16 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (8 lines × 5) src/ConsensusSpectralLibrary/Program.fs:8— src/ConsensusSpectralLibrary/Program.fs:8-15 | src/MzTAB/Program.fs:7-14 | src/PeptideDB/Program.fs:7-14 | src/Preprocessing/Program.fs:7-14 | src/SpectralLibrary/Program.fs:9-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Duplicated block (4–8 lines × 6) src/AlignmentBasedQuantification/Program.fs:18— src/AlignmentBasedQuantification/Program.fs:18-21 | src/ConsensusSpectralLibrary/Program.fs:17-20 | src/MzliteToMzML/Program.fs:17-24 | src/Preprocessing/Program.fs:16-23 | src/SWATHAnalysis/Program.fs:18-21 | src/SpectralLibrary/Program.fs:18-21 — `src/AlignmentBasedQuantification/Program.fs` and `src/SWATHAnalysis/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 51 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (7 lines × 7) src/AlignmentBasedQuantification/CLIArgumentParsing.fs:19— src/AlignmentBasedQuantification/CLIArgumentParsing.fs:19-25 | src/PSMBasedQuantification/CLIArgumentParsing.fs:17-23 | src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs:17-23 | src/PSMStatistics/CLIArgumentParsing.fs:18-24 | src/PeptideSpectrumMatching/CLIArgumentParsing.fs:17-23 | src/QuantBasedAlignment/CLIArgumentParsing.fs:14-20 | src/SWATHAnalysis/CLIArgumentParsing.fs:17-23 — `src/PSMBasedQuantification/CLIArgumentParsing.fs` and `src/PSMBasedQuantificationTIMs/CLIArgumentParsing.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 37 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/PSMBasedQuantification/CLIArgumentParsing.fs:14` calls `AltCommandLine` and `src/AlignmentBasedQuantification/CLIArgumentParsing.fs:16` 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 (7 lines × 6) src/ConsensusSpectralLibrary/Program.fs:9— src/ConsensusSpectralLibrary/Program.fs:9-15 | src/MzTAB/Program.fs:8-14 | src/PeptideDB/Program.fs:8-14 | src/Preprocessing/Program.fs:8-14 | src/ProteinInference/Program.fs:10-16 | src/SpectralLibrary/Program.fs:10-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times.
Duplicated block (6 lines × 8) ConsoleTemplate/template/Program.fs:10— ConsoleTemplate/template/Program.fs:10-16 | src/AddDeducedPeptides/Program.fs:10-16 | src/AlignmentBasedQuantStatistics/Program.fs:10-16 | src/JoinQuantPepIonsWithProteins/Program.fs:10-15 | src/LabelEfficiencyCalculator/Program.fs:9-15 | src/LabelFreeProteinQuantification/Program.fs:9-15 | src/LabeledProteinQuantification/Program.fs:9-15 | src/MzliteToMzML/Program.fs:9-15 — before extracting anything, compare `ConsoleTemplate/template/Program.fs` and `src/LabelEfficiencyCalculator/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 6) ConsoleTemplate/template/Program.fs:18— ConsoleTemplate/template/Program.fs:18-23 | src/LabelEfficiencyCalculator/Program.fs:17-22 | src/MzMLToMzLite/Program.fs:17-22 | src/MzMLToMzLiteIonMobility/Program.fs:18-23 | src/PeptideSpectrumMatching/Program.fs:19-24 | src/PeptideSpectrumMatchingTIMs/Program.fs:18-23 — before extracting anything, compare `ConsoleTemplate/template/Program.fs` and `src/LabelEfficiencyCalculator/Program.fs` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 4) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:459— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:459-464 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:491-496 | src/PSMBasedQuantification/PSMBasedQuantification.fs:360-365 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1835-1840 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:459` 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.
Duplicated block (6 lines × 3) src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2382— src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2382-2387 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2454-2459 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2555-2560 — 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.
Duplicated block (5 lines × 9) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1011— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1011-1015 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1067-1071 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1310-1314 | src/PSMBasedQuantification/PSMBasedQuantification.fs:807-811 | src/PSMBasedQuantification/PSMBasedQuantification.fs:860-864 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1090-1094 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2682-2686 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2735-2739 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2965-2969 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 6) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:941— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:941-945 | src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:1094-1098 | src/PSMBasedQuantification/PSMBasedQuantification.fs:740-744 | src/PSMBasedQuantification/PSMBasedQuantification.fs:887-891 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2615-2619 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2762-2766 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 4) src/PSMBasedQuantification/PSMBasedQuantification.fs:717— src/PSMBasedQuantification/PSMBasedQuantification.fs:717-721 | src/PSMBasedQuantification/PSMBasedQuantification.fs:1043-1047 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2592-2596 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:2918-2922 — `src/PSMBasedQuantification/PSMBasedQuantification.fs` and `src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 46 separate duplicated blocks between them, totalling at least 929 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (2–5 lines × 4) src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:60— src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:60-64 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:134-138 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:145-146 | src/LabeledProteinQuantification/LabeledProteinQuantification.fs:152-153 — `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 50 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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, `src/LabelFreeProteinQuantification/LabelFreeProteinQuantification.fs:64` calls `aggregate` and `src/LabeledProteinQuantification/LabeledProteinQuantification.fs:146` 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.
Duplicated block (8 lines × 3) src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:665— src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:665-674 | src/PSMBasedQuantification/PSMBasedQuantification.fs:514-521 | src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs:1991-1998 — `src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs` and `src/PSMBasedQuantification/PSMBasedQuantification.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 31 separate duplicated blocks between them, totalling at least 556 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (8 lines × 4) src/JoinQuantPepIonsWithProteins/Program.fs:43— src/JoinQuantPepIonsWithProteins/Program.fs:43-50 | src/PSMBasedQuantification/Program.fs:68-75 | src/PSMBasedQuantificationTIMs/Program.fs:68-75 | src/SWATHAnalysis/Program.fs:62-69 — `src/PSMBasedQuantification/Program.fs` and `src/PSMBasedQuantificationTIMs/Program.fs` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 6 separate duplicated blocks between them, totalling at least 108 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. 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.
Duplicated block (7 lines × 5) src/AlignmentBasedQuantStatistics/Program.fs:108— src/AlignmentBasedQuantStatistics/Program.fs:108-115 | src/AlignmentBasedQuantStatistics/Program.fs:126-133 | src/AlignmentBasedQuantStatistics/Program.fs:172-179 | src/AlignmentBasedQuantStatistics/Program.fs:218-225 | src/AlignmentBasedQuantification/Program.fs:80-86 — there are 5 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/AlignmentBasedQuantStatistics/Program.fs:108` 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.
End-of-life runtime: .NET net5.0 ConsoleTemplate/template/ProteomIQonConsole.fsproj:4— ConsoleTemplate/template/ProteomIQonConsole.fsproj declares .NET net5.0 as this project's target framework, and .NET 5, support ended 2022-05-10. An unsupported runtime receives no security patches, so every vulnerability disclosed in it since 2022-05-10 is present and unfixable without moving off it. This is a migration rather than an upgrade: there is no newer release of a runtime that has ended.
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Minor — 21 finding(s)
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×7
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValueCalculation.fs:99— `Trace` at line 99 is called with an argument built by `Array.map (fun x -> string x)` (line 101), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValueCalculation.fs:105— `Trace` at line 105 is called with an argument built by `Array.map (fun x -> string x)` (line 107), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValueCalculation.fs:111— `Trace` at line 111 is called with an argument built by `Array.map (fun x -> string x)` (line 113), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValue/pepValueCalculation.fs:93— `Trace` at line 93 is called with an argument built by `Array.map (fun x -> string x)` (line 95), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValue/pepValueCalculation.fs:99— `Trace` at line 99 is called with an argument built by `Array.map (fun x -> string x)` (line 101), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/ProteomIQon/pepValue/pepValueCalculation.fs:105— `Trace` at line 105 is called with an argument built by `Array.map (fun x -> string x)` (line 107), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Diagnostic log message is built whether or not it is wanted src/PeptideSpectrumMatching/PeptideSpectrumMatching.fs:197— `Trace` at line 197 is called with an argument built by `List.map (fun x -> x.DecoyTheoSpec.Length, x.TheoSpec.Length)` (line 197), whose cost grows with the collection it walks. F# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because Trace is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no `#if DEBUG` region, no `fun` or `lazy` the logger runs only when the level is on.
Duplicated predicate src/PSMBasedQuantification/PSMBasedQuantification.fs:598— `(d <= borders.Upper && d >= borders.Lower) && d < 0.1` appears character-identically in 2 files — src/PSMBasedQuantification/PSMBasedQuantification.fs, src/PSMBasedQuantificationTIMs/PSMBasedQuantificationTIMs.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs:219— `(qualR > lowerBorder && qualR < upperBorder) || (nan.Equals(qualR) )` appears character-identically in 2 files — src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs, src/PSMBasedQuantification/PSMBasedQuantification.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ProteomIQon/pepValue/pepValueCalculation.fs:250— `init || ((step > stepEpsilon || step < 0.) && iter < 20)` appears character-identically in 2 files — src/ProteomIQon/pepValue/pepValueCalculation.fs, src/ProteomIQon/pepValueCalculation.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs:233— `p1d.Mz > mzRange.HighValue || p1d.Mz < mzRange.LowValue` appears character-identically in 2 files — src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs, src/SWATHAnalysis/SWATHAnalysis.fs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 21 significant file(s) lose their only recent owner: src/AlignmentBasedQuantification/AlignmentBasedQuantification.fs, src/ProteomIQon/DTO.fs, src/PSMBasedQuantification/PSMBasedQuantification.fs, src/PeptideSpectrumMatchingTIMs/PeptideSpectrumMatchingTIMs.fs, src/ProteomIQon/BioFSharp.Mz_Temp.fs, src/PSMStatistics/PSMStatistics.fs, src/ConsensusSpectralLibrary/ConsensusSpectralLibrary.fs, src/PeptideSpectrumMatchingTIMs/SpectrumSearch.fs (+13 more). Pair on, review, or document these before any departure.
No ADRs found — 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/`.
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.
Logging is not universal — Only 27/30 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `src/QuantBasedAlignment_linux-x64`, `src/QuantBasedAlignment_win-x64`, `src/RatioLFQ`.
No SAST REDACTED:6— No static application security testing detected. For this repository's stack, add `semgrep --config=auto` plus gitleaks for committed secrets (F# is not a CodeQL language and has no language-specific SAST engine) as a CI step. What was searched, so you can tell an absence from a miss: the 2044 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.
No dependency-update automation ConsoleTemplate/template/ProteomIQonConsole.fsproj:39— `ConsoleTemplate/template/ProteomIQonConsole.fsproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
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.
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.
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.
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.
Run 01a19224-2ef9-7972-92ca-5b29a08e21ac · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 7 · Warnings: 202 · Recommendations: 21 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 31-10-2026 @ 13:26 UTC.
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.