Public report of robbiebyrd/classicy, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 20:41 UTC · Survey ID cd_5ae7ed8c4b574be5b705f8889ee1789f
robbiebyrd/classicy
Measured 16 November 2026, 20:36 UTC, at code version c36af8d
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
Bus factor is not measured: One contributor carries this repository.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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: 64,213 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 1.2 person-years · Weakest lens: Accessibility, 56.0
Findings by how serious they are
23 critical458 serious76 minor
5 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 20:36 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
72of 72 dimensions measured by tools.
535of 557 findings point to an exact file and line, so you can open each one in the code. The other 22 concern the repository as a whole, such as missing documentation.
72dimensions across 7 lenses, read from 64,213 lines of product code in 3 projects.
robbiebyrd/classicy falls short of our standard for production because it has controls that only work with a mouse. It scores 60.2 out of 100 and is rated Adequate, and two of its 23 critical findings are leaked passwords or keys.
Accessibility, at 56.0, is the weakest lens and counts most in the score. The best first steps are making the controls keyboard-usable and fixing focus, motion and contrast, each worth about 2.3 points. Raising Accessibility to 70 would lift the score to about 63.3.
Five controls can't be used without a mouse. Two passwords or keys are open to anyone who can read the repository, and fourteen form fields can't be read by a screen reader. Making the controls work with a keyboard, replacing each exposed password or key and labelling the form fields would close these risks. The two loops of files that import each other need breaking.
The product code is 64,213 lines, about €180,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts 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.
If Accessibility rose from 56.0 to 70, the lowest score rated Strong, the score would rise from 60.2 to about 63.3.
Code composition: what the lines of code are
Product code 39%Tests 61%
Rebuild cost: about €180,000 · Estimate
Cost to rebuild
€59,000 to €290,000, for 977 to 3,100 hours of work, about 1.2 person-years for 1 to 3 engineers
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 60. 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: 64,213 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: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 2.3 points · Medium effort · Keyboard semantics
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 2.2 points · Medium effort · Forms & labels
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €180,000 to build again, about 1.2 person-years of work. Its weakest lens is Accessibility, at 56.0 (Adequate). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 2.3 points for medium effort. 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 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 18% on every change. The history of the code shows how much it changes: about 179,816 lines over the last 90 days, which is about 729,254 lines a year. At that pace, the extra work comes to an estimated 149.2 to 895.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — 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.
229 modules, with 129 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; 189 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.
1 pair of types, where a type in SystemFolder.ControlPanels.AppManager.ClassicyAppManager uses a type in SystemFolder.SystemResources.File.ClassicyFileSystemModel.
SystemFolder.ControlPanels.AppManager.ClassicyAppManager uses SystemFolder.SystemResources.File.ClassicyFileSystemModel, so a change to SystemFolder.SystemResources.File.ClassicyFileSystemModel can break SystemFolder.ControlPanels.AppManager.ClassicyAppManager, while a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can't break SystemFolder.SystemResources.File.ClassicyFileSystemModel.
Position
Below the diagonal: SystemFolder.ControlPanels.AppManager.ClassicyAppManager uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor.HyperCardEditorUtils uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.Editor.HyperCardEditorUtils, while a change to SystemFolder.HyperCard.Editor.HyperCardEditorUtils can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardEditorUtils uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.HyperCardPlugins uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.HyperCardPlugins, while a change to SystemFolder.HyperCard.HyperCardPlugins can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.HyperCardPlugins uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.HyperCardUtils uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.HyperCardUtils, while a change to SystemFolder.HyperCard.HyperCardUtils can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.HyperCardUtils uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.App uses SystemFolder.SystemResources.Menu.ClassicyMenu, so a change to SystemFolder.SystemResources.Menu.ClassicyMenu can break SystemFolder.SystemResources.App, while a change to SystemFolder.SystemResources.App can't break SystemFolder.SystemResources.Menu.ClassicyMenu.
Position
Below the diagonal: SystemFolder.SystemResources.App uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.SystemResources.BevelButton uses a type in SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp.
SystemFolder.SystemResources.BevelButton uses SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp, so a change to SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp can break SystemFolder.SystemResources.BevelButton, while a change to SystemFolder.SystemResources.BevelButton can't break SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp.
Position
Below the diagonal: SystemFolder.SystemResources.BevelButton uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.SystemResources.Desktop.ClassicyDesktopManager uses a type in SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp.
SystemFolder.SystemResources.Desktop.ClassicyDesktopManager uses SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp, so a change to SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp can break SystemFolder.SystemResources.Desktop.ClassicyDesktopManager, while a change to SystemFolder.SystemResources.Desktop.ClassicyDesktopManager can't break SystemFolder.SystemResources.BalloonHelp.useClassicyBalloonHelp.
Position
Below the diagonal: SystemFolder.SystemResources.Desktop.ClassicyDesktopManager uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in SystemFolder.SystemResources.File.ClassicyFileSystem uses a type in SystemFolder.SystemResources.File.ClassicyFileSystemAdapter.
SystemFolder.SystemResources.File.ClassicyFileSystem uses SystemFolder.SystemResources.File.ClassicyFileSystemAdapter, so a change to SystemFolder.SystemResources.File.ClassicyFileSystemAdapter can break SystemFolder.SystemResources.File.ClassicyFileSystem, while a change to SystemFolder.SystemResources.File.ClassicyFileSystem can't break SystemFolder.SystemResources.File.ClassicyFileSystemAdapter.
Position
Below the diagonal: SystemFolder.SystemResources.File.ClassicyFileSystem uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.Menu uses SystemFolder.SystemResources.Menu.ClassicyMenu, so a change to SystemFolder.SystemResources.Menu.ClassicyMenu can break SystemFolder.SystemResources.Menu, while a change to SystemFolder.SystemResources.Menu can't break SystemFolder.SystemResources.Menu.ClassicyMenu.
Position
Below the diagonal: SystemFolder.SystemResources.Menu uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in SystemFolder.SystemResources.Meter.ClassicyMeter uses a type in SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
SystemFolder.SystemResources.Meter.ClassicyMeter uses SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel, so a change to SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel can break SystemFolder.SystemResources.Meter.ClassicyMeter, while a change to SystemFolder.SystemResources.Meter.ClassicyMeter can't break SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
Position
Below the diagonal: SystemFolder.SystemResources.Meter.ClassicyMeter uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in SystemFolder.SystemResources.Slider.ClassicySlider uses a type in SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
SystemFolder.SystemResources.Slider.ClassicySlider uses SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel, so a change to SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel can break SystemFolder.SystemResources.Slider.ClassicySlider, while a change to SystemFolder.SystemResources.Slider.ClassicySlider can't break SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
Position
Below the diagonal: SystemFolder.SystemResources.Slider.ClassicySlider uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in SystemFolder.SystemResources.TimePicker.ClassicyTimePicker uses a type in SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
SystemFolder.SystemResources.TimePicker.ClassicyTimePicker uses SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel, so a change to SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel can break SystemFolder.SystemResources.TimePicker.ClassicyTimePicker, while a change to SystemFolder.SystemResources.TimePicker.ClassicyTimePicker can't break SystemFolder.SystemResources.ControlLabel.ClassicyControlLabel.
Position
Below the diagonal: SystemFolder.SystemResources.TimePicker.ClassicyTimePicker uses a module listed above it, which is the healthy direction.
Appearance uses Appearance.ClassicyAssetRegistry, so a change to Appearance.ClassicyAssetRegistry can break Appearance, while a change to Appearance can't break Appearance.ClassicyAssetRegistry.
Position
Below the diagonal: Appearance uses a module listed above it, which is the healthy direction.
Appearance uses SystemFolder.ControlPanels.SoundManager.ClassicySoundManagerUtils, so a change to SystemFolder.ControlPanels.SoundManager.ClassicySoundManagerUtils can break Appearance, while a change to Appearance can't break SystemFolder.ControlPanels.SoundManager.ClassicySoundManagerUtils.
Position
Below the diagonal: Appearance uses a module listed above it, which is the healthy direction.
Appearance uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break Appearance, while a change to Appearance can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: Appearance uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppManager uses SystemFolder.ControlPanels.AppManager.ClassicyActionTrust, so a change to SystemFolder.ControlPanels.AppManager.ClassicyActionTrust can break SystemFolder.ControlPanels.AppManager, while a change to SystemFolder.ControlPanels.AppManager can't break SystemFolder.ControlPanels.AppManager.ClassicyActionTrust.
Position
Below the diagonal: SystemFolder.ControlPanels.AppManager uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppManager uses SystemFolder.SystemResources.File.ClassicyFileSystemModel, so a change to SystemFolder.SystemResources.File.ClassicyFileSystemModel can break SystemFolder.ControlPanels.AppManager, while a change to SystemFolder.ControlPanels.AppManager can't break SystemFolder.SystemResources.File.ClassicyFileSystemModel.
Position
Below the diagonal: SystemFolder.ControlPanels.AppManager uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppManager uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.ControlPanels.AppManager, while a change to SystemFolder.ControlPanels.AppManager can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.ControlPanels.AppManager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.ControlPanels.DateAndTimeManager uses a type in SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
SystemFolder.ControlPanels.DateAndTimeManager uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.ControlPanels.DateAndTimeManager, while a change to SystemFolder.ControlPanels.DateAndTimeManager can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.ControlPanels.DateAndTimeManager uses a module listed above it, which is the healthy direction.
SystemFolder.Extensions.ScreenSaver uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.Extensions.ScreenSaver, while a change to SystemFolder.Extensions.ScreenSaver can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.Extensions.ScreenSaver uses a module listed above it, which is the healthy direction.
SystemFolder.Finder uses SystemFolder.ControlPanels.AppManager.ClassicyActionTrust, so a change to SystemFolder.ControlPanels.AppManager.ClassicyActionTrust can break SystemFolder.Finder, while a change to SystemFolder.Finder can't break SystemFolder.ControlPanels.AppManager.ClassicyActionTrust.
Position
Below the diagonal: SystemFolder.Finder uses a module listed above it, which is the healthy direction.
SystemFolder.Finder uses SystemFolder.SystemResources.Tabs.ClassicyTabs, so a change to SystemFolder.SystemResources.Tabs.ClassicyTabs can break SystemFolder.Finder, while a change to SystemFolder.Finder can't break SystemFolder.SystemResources.Tabs.ClassicyTabs.
Position
Below the diagonal: SystemFolder.Finder uses a module listed above it, which is the healthy direction.
SystemFolder.Finder uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.Finder, while a change to SystemFolder.Finder can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.Finder uses a module listed above it, which is the healthy direction.
SystemFolder.Finder uses SystemFolder.SystemResources.File.ClassicyFileSystem, so a change to SystemFolder.SystemResources.File.ClassicyFileSystem can break SystemFolder.Finder, while a change to SystemFolder.Finder can't break SystemFolder.SystemResources.File.ClassicyFileSystem.
Position
Below the diagonal: SystemFolder.Finder uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.HyperCard.Editor.HyperCardEditorOverlay uses a type in SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
SystemFolder.HyperCard.Editor.HyperCardEditorOverlay uses SystemFolder.HyperCard.Editor.HyperCardEditorUtils, so a change to SystemFolder.HyperCard.Editor.HyperCardEditorUtils can break SystemFolder.HyperCard.Editor.HyperCardEditorOverlay, while a change to SystemFolder.HyperCard.Editor.HyperCardEditorOverlay can't break SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardEditorOverlay uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor.HyperCardScriptBuilder uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.Editor.HyperCardScriptBuilder, while a change to SystemFolder.HyperCard.Editor.HyperCardScriptBuilder can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardScriptBuilder uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.HyperCard.Editor.HyperCardScriptBuilder uses a type in SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
SystemFolder.HyperCard.Editor.HyperCardScriptBuilder uses SystemFolder.HyperCard.Editor.HyperCardEditorUtils, so a change to SystemFolder.HyperCard.Editor.HyperCardEditorUtils can break SystemFolder.HyperCard.Editor.HyperCardScriptBuilder, while a change to SystemFolder.HyperCard.Editor.HyperCardScriptBuilder can't break SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardScriptBuilder uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor.HyperCardScriptJson uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.Editor.HyperCardScriptJson, while a change to SystemFolder.HyperCard.Editor.HyperCardScriptJson can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardScriptJson uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor.HyperCardScriptJson uses SystemFolder.HyperCard.Editor.HyperCardEditorUtils, so a change to SystemFolder.HyperCard.Editor.HyperCardEditorUtils can break SystemFolder.HyperCard.Editor.HyperCardScriptJson, while a change to SystemFolder.HyperCard.Editor.HyperCardScriptJson can't break SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
Position
Below the diagonal: SystemFolder.HyperCard.Editor.HyperCardScriptJson uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.HyperCardCard uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.HyperCardCard, while a change to SystemFolder.HyperCard.HyperCardCard can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.HyperCardCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.HyperCardCard uses SystemFolder.HyperCard.HyperCardUtils, so a change to SystemFolder.HyperCard.HyperCardUtils can break SystemFolder.HyperCard.HyperCardCard, while a change to SystemFolder.HyperCard.HyperCardCard can't break SystemFolder.HyperCard.HyperCardUtils.
Position
Below the diagonal: SystemFolder.HyperCard.HyperCardCard uses a module listed above it, which is the healthy direction.
SystemFolder.QuickTime.MoviePlayer uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.QuickTime.MoviePlayer, while a change to SystemFolder.QuickTime.MoviePlayer can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.QuickTime.MoviePlayer uses a module listed above it, which is the healthy direction.
SystemFolder.QuickTime.MoviePlayer uses SystemFolder.SystemResources.File.ClassicyFileSystem, so a change to SystemFolder.SystemResources.File.ClassicyFileSystem can break SystemFolder.QuickTime.MoviePlayer, while a change to SystemFolder.QuickTime.MoviePlayer can't break SystemFolder.SystemResources.File.ClassicyFileSystem.
Position
Below the diagonal: SystemFolder.QuickTime.MoviePlayer uses a module listed above it, which is the healthy direction.
SystemFolder.QuickTime.PictureViewer uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.QuickTime.PictureViewer, while a change to SystemFolder.QuickTime.PictureViewer can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.QuickTime.PictureViewer uses a module listed above it, which is the healthy direction.
SystemFolder.QuickTime.PictureViewer uses SystemFolder.SystemResources.File.ClassicyFileSystem, so a change to SystemFolder.SystemResources.File.ClassicyFileSystem can break SystemFolder.QuickTime.PictureViewer, while a change to SystemFolder.QuickTime.PictureViewer can't break SystemFolder.SystemResources.File.ClassicyFileSystem.
Position
Below the diagonal: SystemFolder.QuickTime.PictureViewer uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.Desktop uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.SystemResources.Desktop, while a change to SystemFolder.SystemResources.Desktop can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.SystemResources.Desktop uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.Desktop uses SystemFolder.SystemResources.Desktop.ClassicyDesktopManager, so a change to SystemFolder.SystemResources.Desktop.ClassicyDesktopManager can break SystemFolder.SystemResources.Desktop, while a change to SystemFolder.SystemResources.Desktop can't break SystemFolder.SystemResources.Desktop.ClassicyDesktopManager.
Position
Below the diagonal: SystemFolder.SystemResources.Desktop uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.Desktop.MenuBar uses SystemFolder.SystemResources.Menu.ClassicyMenu, so a change to SystemFolder.SystemResources.Menu.ClassicyMenu can break SystemFolder.SystemResources.Desktop.MenuBar, while a change to SystemFolder.SystemResources.Desktop.MenuBar can't break SystemFolder.SystemResources.Menu.ClassicyMenu.
Position
Below the diagonal: SystemFolder.SystemResources.Desktop.MenuBar uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.Desktop.MenuBar uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.SystemResources.Desktop.MenuBar, while a change to SystemFolder.SystemResources.Desktop.MenuBar can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.SystemResources.Desktop.MenuBar uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.File uses SystemFolder.SystemResources.File.ClassicyFileSystemAdapter, so a change to SystemFolder.SystemResources.File.ClassicyFileSystemAdapter can break SystemFolder.SystemResources.File, while a change to SystemFolder.SystemResources.File can't break SystemFolder.SystemResources.File.ClassicyFileSystemAdapter.
Position
Below the diagonal: SystemFolder.SystemResources.File uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.File uses SystemFolder.SystemResources.Desktop.ClassicyDesktopManager, so a change to SystemFolder.SystemResources.Desktop.ClassicyDesktopManager can break SystemFolder.SystemResources.File, while a change to SystemFolder.SystemResources.File can't break SystemFolder.SystemResources.Desktop.ClassicyDesktopManager.
Position
Below the diagonal: SystemFolder.SystemResources.File uses a module listed above it, which is the healthy direction.
SystemFolder.SystemResources.File uses SystemFolder.SystemResources.File.ClassicyFileSystem, so a change to SystemFolder.SystemResources.File.ClassicyFileSystem can break SystemFolder.SystemResources.File, while a change to SystemFolder.SystemResources.File can't break SystemFolder.SystemResources.File.ClassicyFileSystem.
Position
Below the diagonal: SystemFolder.SystemResources.File uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options uses Appearance, so a change to Appearance can break SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options, while a change to SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options can't break Appearance.
Position
Below the diagonal: SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard, while a change to SystemFolder.HyperCard can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.HyperCard, while a change to SystemFolder.HyperCard can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.HyperCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard uses SystemFolder.HyperCard.HyperCardPlugins, so a change to SystemFolder.HyperCard.HyperCardPlugins can break SystemFolder.HyperCard, while a change to SystemFolder.HyperCard can't break SystemFolder.HyperCard.HyperCardPlugins.
Position
Below the diagonal: SystemFolder.HyperCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard uses SystemFolder.HyperCard.HyperCardUtils, so a change to SystemFolder.HyperCard.HyperCardUtils can break SystemFolder.HyperCard, while a change to SystemFolder.HyperCard can't break SystemFolder.HyperCard.HyperCardUtils.
Position
Below the diagonal: SystemFolder.HyperCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard uses SystemFolder.HyperCard.HyperCardCard, so a change to SystemFolder.HyperCard.HyperCardCard can break SystemFolder.HyperCard, while a change to SystemFolder.HyperCard can't break SystemFolder.HyperCard.HyperCardCard.
Position
Below the diagonal: SystemFolder.HyperCard uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.HyperCardModel, so a change to SystemFolder.HyperCard.HyperCardModel can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.HyperCardModel.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.ControlPanels.AppManager.ClassicyAppManager, so a change to SystemFolder.ControlPanels.AppManager.ClassicyAppManager can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.ControlPanels.AppManager.ClassicyAppManager.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.Editor.HyperCardEditorUtils, so a change to SystemFolder.HyperCard.Editor.HyperCardEditorUtils can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.Editor.HyperCardEditorUtils.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.HyperCardPlugins, so a change to SystemFolder.HyperCard.HyperCardPlugins can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.HyperCardPlugins.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.HyperCardUtils, so a change to SystemFolder.HyperCard.HyperCardUtils can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.HyperCardUtils.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.Editor.HyperCardEditorOverlay, so a change to SystemFolder.HyperCard.Editor.HyperCardEditorOverlay can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.Editor.HyperCardEditorOverlay.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.HyperCard.Editor uses SystemFolder.HyperCard.Editor.HyperCardScriptBuilder, so a change to SystemFolder.HyperCard.Editor.HyperCardScriptBuilder can break SystemFolder.HyperCard.Editor, while a change to SystemFolder.HyperCard.Editor can't break SystemFolder.HyperCard.Editor.HyperCardScriptBuilder.
Position
Below the diagonal: SystemFolder.HyperCard.Editor uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppearanceManager uses SystemFolder.SystemResources.Tabs.ClassicyTabs, so a change to SystemFolder.SystemResources.Tabs.ClassicyTabs can break SystemFolder.ControlPanels.AppearanceManager, while a change to SystemFolder.ControlPanels.AppearanceManager can't break SystemFolder.SystemResources.Tabs.ClassicyTabs.
Position
Below the diagonal: SystemFolder.ControlPanels.AppearanceManager uses a module listed above it, which is the healthy direction.
SystemFolder.ControlPanels.AppearanceManager uses Appearance, so a change to Appearance can break SystemFolder.ControlPanels.AppearanceManager, while a change to SystemFolder.ControlPanels.AppearanceManager can't break Appearance.
Position
Below the diagonal: SystemFolder.ControlPanels.AppearanceManager uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in SystemFolder.ControlPanels.AppearanceManager uses a type in SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options.
SystemFolder.ControlPanels.AppearanceManager uses SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options, so a change to SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options can break SystemFolder.ControlPanels.AppearanceManager, while a change to SystemFolder.ControlPanels.AppearanceManager can't break SystemFolder.ControlPanels.AppearanceManager.ClassicyAppearanceManager_Options.
Position
Below the diagonal: SystemFolder.ControlPanels.AppearanceManager uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 61.5 · Adequate · gated by D1, D2 ·
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
A03:2025 — Software Supply Chain Failures
7
Medium
A07:2025 — Authentication Failures
3
High / Critical
A05:2025 — Injection
3
Medium
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with ClassicyWindow.ClassicyWindow (cyclomatic 209), HyperCardEditorContext.classicyHyperCardEditorEventHandler (cyclomatic 156).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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 — 23
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 — 458
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 — 76
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 5
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 72 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, 535 of 557 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 or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 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 an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D28 Secrets (history) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The newest 1290 of 2127 commits were scanned for secrets, back to commit f2d20f89a5e0; older commits were not. `gitleaks` TIMED OUT after 69.7s against a 69.5s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. The working tree WAS scanned in full, and every row of the scanned ranges is reported. Nothing about the unscanned commits is asserted by the absence of a result; the budget is ours to raise.
D31 IaC & Container Security — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Checkov ran but its report could not be read (checkov produced no output — not a clean result). Every misconfiguration only checkov reports — most of its Terraform, CloudFormation, Bicep and Ansible policies — is absent from this card, so its absence here is not evidence those resources are configured correctly.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/appearance/platinum/src/screenSavers/platinumScreenSavers.stories.tsx`, `src/Appearance/ClassicyAppearancePackageSchema.ts`, `src/Appearance/ClassicyAssetRegistry.ts`, `src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx`, `src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts`, … (+69 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 8 further occurrence(s) are not listed individually; the score already reflects all 48.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (example/docker-compose.yml). compose up failed (exit 14 — a file the compose project references is missing) — env file example/.env not found: stat example/.env: no such file or directory; runtime evidence skipped.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
R10 Code Duplication — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 62 further occurrence(s) are not listed individually; the score already reflects all 102.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 61 further occurrence(s) are not listed individually; the score already reflects all 101.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 343 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
74 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ClassicyWindow.ClassicyWindow at 209. A further 6 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ClassicyAppearancePackageSchema.isUnsafeCodePoint at 24 — they are counted neither in the figure above nor in this dimension's score. 4 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/Appearance/ClassicyAppearancePackageSchema.ts (ClassicyAppearancePackageSchema.isUnsafeCodePoint at 24), src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts (ClassicyThemeMetricTargets.getThemeMetric at 21), src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeColorTargets.ts (ClassicyThemeColorTargets.getThemeColor at 17), src/SystemFolder/HyperCard/HyperCardCard.tsx (HyperCardCard.renderPart at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 69 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with ClassicyWindow.ClassicyWindow (cyclomatic 209), HyperCardEditorContext.classicyHyperCardEditorEventHandler (cyclomatic 156). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 2.2 to about 3.4/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 89 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 60 down to 60 or less in Cognitive Complexity — start with HyperCardEditorContext.classicyHyperCardEditorEventHandler (cognitive 214), HyperCard.HyperCard (cognitive 148), ClassicyDesktopManager.classicyDesktopEventHandler (cognitive 135). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 12 together lifts Cognitive Complexity from 2.0 to about 4.1/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.5 / 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 29 FunctionTooLong finding(s) in God Classes — start with Finder.tsx (2), ClassicyTree.tsx (2), HyperCardEditorContext.ts. — One of this dimension's main actionable groups (29 warning-level).
Resolve the 7 FileTooLong finding(s) in God Classes — start with ClassicyWindow.tsx, HyperCard.tsx, ClassicyDesktop.tsx. — One of this dimension's main actionable groups (7 warning-level).
Resolve the 2 ClassTooLong finding(s) in God Classes — start with ClassicyWindow.tsx, HyperCard.tsx. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling7.3 / 10Strong✓ 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.
3 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @classicy/appearance-platinum
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality10.0 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 5200 tests.
No assertions: is MDXEditor's MDXEditorMethods · ×2src/SystemFolder/SystemResources/RichTextEditor/ClassicyRichTextEditor.test.ts:11
Mock-dominated test: clicks and keys each control box to its handler · ×20src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.test.tsx:117
What to do
Resolve the 20 Mock-dominated test finding(s) in Test Quality — start with ClassicyFileDrag.test.ts (5), ClassicyFileBrowserViewTable.test.tsx (3), ClassicyPointerStreamLost.test.tsx (3). — One of this dimension's main actionable groups (20 recommendation-level).
Resolve the 2 No assertions finding(s) in Test Quality — start with ClassicyRichTextEditor.test.ts, FinderOpenWithTrust.test.ts. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in packages/appearance/platinum/ (516 tests)): measured (0 flaky).
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
10 outdated direct production npm dependency(ies) of 19 graded, 0 pinning defect(s), across 4 package.json (3 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
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: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 39 Hotspot finding(s) in Churn × Complexity Hotspots — start with ClassicyWindow.tsx, ClassicyDesktopManager.tsx, HyperCard.tsx. — One of this dimension's main actionable groups (39 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
2 deducted task-comment markers across 64213 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 2 TodoComment finding(s) in Explicit Debt — start with ClassicyDesktopIconContext.tsx, FinderContext.tsx. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
1 of 185 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
ADR Consequences section is emptydocs/stories/0148-wf3-bugs-host-defaultstate-theme-tweaks-do-not-persist.md:62detected by adr-integrity
✓ On the Gold path — maintain.
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 23 declarations measured against a convention their peers follow.
`setBackgroundURL` spells `URL` where 22 names in the project spell it `Url`src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Desktop.tsx:53
What to do
Resolve the 1 `setBackgroundURL` spells `URL` where 22 names in the project spell it… finding(s) in Naming Consistency — start with ClassicyAppearanceManager.Desktop.tsx. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 3 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpackage.json:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
3 % of calls cross a namespace and 0 % go through an interface, but 98 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
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.
2 finding(s): 0 critical, 2 high, 0 medium, 0 low. History coverage: The newest 1290 of 2127 commits were scanned for secrets, back to commit f2d20f89a5e0; older commits were not. `gitleaks` TIMED OUT after 69.7s against a 69.5s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 2 High secret finding(s) in Secrets (history) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 285 of the 417 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 4 Change coupling finding(s) in Change Coupling — start with ClassicyAppearanceManager.tsx, ClassicyDateAndTimeManager.tsx, MoviePlayer.tsx. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 2 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. Reported 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. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 16 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.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives7.1 / 10Strong✓ Tool-verified
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorWheel.tsx:157
What to do
Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
Do you agree with this assessment?
AC2 · Forms & labels5.1 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×11) — src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx:327, src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:304, src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:321, …
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×3) — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:391, src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:219, src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:319
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — src/SystemFolder/SystemResources/AboutWindow/ClassicyAboutWindow.tsx:114
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×2) — src/SystemFolder/ControlPanels/DriveSetup/DriveSetupList.tsx:44, src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:364
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButtonPopup.tsx:205
A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}. (×2) — src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:545, src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:620
This <div> binds mousedown and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click. — src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:113
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`.classicyTimePicker input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.scss:35
`.classicyTimePicker input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.scss:30
`.classicySpinner:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/Spinner/ClassicySpinner.scss:31
`.classicySpinner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/Spinner/ClassicySpinner.scss:26
`.classicySlider` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/Slider/ClassicySlider.scss:31
`.quickTimePlayerVideoControlsProgressBar:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/QuickTime/QuickTimeMovieEmbed.scss:128
`.classicyListBoxOption` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/ListBox/ClassicyListBox.scss:31
`.classicyKeyboardEquivalentDialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalent.scss:41
`.classicyFileBrowserViewTableContainer.classicyTableContainer:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.scss:26
`.classicyFileBrowserFill.classicyFileDropTarget` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/File/ClassicyFileDrag.scss:35
`.classicyIcon.classicyFileDropTarget` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/File/ClassicyFileDrag.scss:50
`.classicyDesktopIcon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.scss:17
`.classicyDesktop .classicyDesktopIcon:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.scss:42
`.classicyDatePicker input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.scss:33
`.classicyDatePicker input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.scss:30
`.classicyHyperCardEditorOverlay` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/SystemFolder/HyperCard/HyperCard.scss:170
`.classicyProgressChasingArrows .classicyProgressChasingArrowsSpinner` moves (`animation: classicyChasingArrowsSpin 1s steps(8, end) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/SystemFolder/SystemResources/ProgressBar/ClassicyProgressBar.scss:97
`.classicyColorPickerCrayon` moves (`transition: transform 0.07s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPicker.scss:212
`.classicySaverWarpStars` moves (`animation: classicySaverWarpZoom 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Warp/_ClassicyScreenSaverWarp.scss:11
`.classicySaverSpotlightMask` moves (`animation: classicySaverSpotlightMoveX 5s linear 0s infinite alternate,
classicySaverSpotlightMoveY 5.6s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Spotlight/_ClassicyScreenSaverSpotlight.scss:8
`.classicySaverRainstormRain` moves (`animation-name: classicySaverRainstormFall`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Rainstorm/_ClassicyScreenSaverRainstorm.scss:19
`.classicySaverMessages2Text` moves (`animation: classicySaverMessages2MoveX 8s linear 0s infinite alternate,
classicySaverMessages2MoveY 17.3s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Messages2/_ClassicyScreenSaverMessages2.scss:14
`.classicySaverMessagesText` moves (`animation: classicySaverMessagesMarquee var(--classicy-saver-messages-speed, 10s)
linear infinite,
classicySaverMessagesMove 30s steps(3) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Messages/_ClassicyScreenSaverMessages.scss:11
`.classicySaverLogoMark` moves (`animation: classicySaverLogoMoveX 5s linear 0s infinite alternate,
classicySaverLogoMoveY 6.3s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Logo/_ClassicyScreenSaverLogo.scss:16
`.classicySaverHardRainDrop` moves (`animation: classicySaverHardRainDrip 4.5s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/HardRain/_ClassicyScreenSaverHardRain.scss:23
`.classicySaverGlobeBall` moves (`animation: classicySaverGlobeMoveX 3s linear 0s infinite alternate,
classicySaverGlobeMoveY 3.4s linear 0s infinite alternate,
classicySaverGlobeSpin 1.4s steps(21) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Globe/_ClassicyScreenSaverGlobe.scss:14
`.classicySaverFlyingToastersVariant-t1` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:25
`.classicySaverFlyingToastersVariant-t2` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:30
`.classicySaverFlyingToastersVariant-t3` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:35
`.classicySaverFlyingToastersVariant-t4` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 10s 5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:40
`.classicySaverFlyingToastersVariant-t5` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 4s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:45
`.classicySaverFlyingToastersVariant-t6` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s 8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:50
`.classicySaverFlyingToastersVariant-t7` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 12s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:55
`.classicySaverFlyingToastersVariant-t8` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:60
`.classicySaverFlyingToastersVariant-t9` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:65
`.classicySaverFlyingToastersVariant-tst1` moves (`animation: classicySaverFlyingToastersFly 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:71
`.classicySaverFlyingToastersVariant-tst2` moves (`animation: classicySaverFlyingToastersFly 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:74
`.classicySaverFlyingToastersVariant-tst3` moves (`animation: classicySaverFlyingToastersFly 24s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:77
`.classicySaverFlyingToastersVariant-tst4` moves (`animation: classicySaverFlyingToastersFly 24s 12s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:80
`.classicySaverFishBubbles` moves (`animation: classicySaverFishRise 13s linear infinite,
classicySaverFishReappear 39s steps(3) linear infinite,
classicySaverFishBubbleAlt 0.2s steps(2) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — packages/appearance/platinum/src/screenSavers/Fish/_ClassicyScreenSaverFish.scss:18
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX 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.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`dispatch` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/SystemFolder/SystemResources/Analytics/useClassicyAnalytics.ts:17
`defaultFileOnClick` has an empty body — confirm it's an intentional no-op and not an unfinished method. — src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx:128
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
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 CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4 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. — .github/workflows/ci.yml:19
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
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.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
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 each language's code 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.
`readFileSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parity.ts:80
`writeFileSync` in `stableShot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityApp.ts:175
`mkdirSync` in `shootApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityApp.ts:246
`mkdirSync` in `shootStories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityShoot.ts:125
`writeFileSync` in `shootStories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — bin/parity/parityShoot.ts:126, bin/parity/parityShoot.ts:201
`writeFileSync` in `callback to onStory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityShoot.ts:167
`writeFileSync` in `callback to runPool` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityShoot.ts:188
`readFileSync` in `resolveStoryIds` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — bin/parity/parityStories.ts:36
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
29 duplicated blocks under src/SystemFolder/SystemResources/ have copies in at least two of the sibling directories Alert, Assistant, BalloonHelp, Button, ButtonToolbar, ComboBox (+26 more sibling(s) not listed) — 20 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 29 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130
13 duplicated blocks under src/SystemFolder/ have copies in at least two of the sibling directories ControlPanels, Extensions, Finder, HyperCard, PDFViewer, QuickTime (+3 more sibling(s) not listed) — 9 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/SystemFolder/PDFViewer/PDFViewerContext.tsx:47
9 duplicated blocks under src/SystemFolder/ControlPanels/ have copies in at least two of the sibling directories AppManager, AppearanceManager, ControlStripManager, DateAndTimeManager, DriveSetup, ScreenSaverManager (+1 more sibling(s) not listed) — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40
6 of the duplicated blocks reported below have copies in at least two of the sibling directories MoviePlayer, PictureViewer under src/SystemFolder/QuickTime/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172
5 duplicated blocks under packages/appearance/platinum/src/screenSavers/ have copies in at least two of the sibling directories BouncingBall, Fish, FlyingToasters, Globe, HardRain, Messages (+3 more sibling(s) not listed) — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/appearance/platinum/src/screenSavers/FlyingToasters/ClassicyScreenSaverFlyingToasters.tsx:115
src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130 · src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:193 — the two spans are one implementation copied and then locally edited — 1278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130
src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:39 · src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:50 — the two spans are one implementation copied and then locally edited — 1204 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:39
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:134 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172
src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40 · src/SystemFolder/ControlPanels/ScreenSaverManager/ClassicyScreenSaverManager.tsx:51 — the two spans are one implementation copied and then locally edited — 339 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:36 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx:38 — the two spans are one implementation copied and then locally edited — 386 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:36
src/SystemFolder/SystemResources/Input/ClassicyInput.tsx:49 · src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:59 — the two spans are one implementation copied and then locally edited — 262 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/Input/ClassicyInput.tsx:49
src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:62 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHSV.tsx:62 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:62
src/SystemFolder/SystemResources/File/ClassicyFileSystemApplications.ts:98 · src/SystemFolder/SystemResources/File/ClassicyFileSystemExtensions.ts:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/SystemFolder/SystemResources/File/ClassicyFileSystemApplications.ts:98
src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.tsx:161 · src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:170 — the two spans are one implementation copied and then locally edited — 199 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.tsx:161
src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:12 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHSV.tsx:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:12
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:259 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:218 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:259
src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:42 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:106 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:42
src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:500 · src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:612 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:500
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Colors.tsx:38 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Metrics.tsx:54 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Colors.tsx:38
src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1133 · src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1322 — the two spans are one implementation copied and then locally edited — 193 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1133
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:585 · src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx:129 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:585
src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:236 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:326 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:381 — 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. — src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:236
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:127 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:89 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:127
src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:176 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:250 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:340 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:395 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:176
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:448 · src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx:84 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:448
src/SystemFolder/HyperCard/HyperCard.tsx:241 · src/SystemFolder/HyperCard/HyperCard.tsx:683 — the two spans are one implementation copied and then locally edited — 128 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/HyperCard/HyperCard.tsx:241
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:453 · src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:193 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:453
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerUtils.tsx:19 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerUtils.tsx:5 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerUtils.tsx:19
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:464 · src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:202 · src/SystemFolder/ControlPanels/DriveSetup/ClassicyDriveSetup.tsx:97 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:464
src/SystemFolder/PDFViewer/PDFViewer.tsx:46 · src/SystemFolder/WebViewer/WebViewer.tsx:68 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/PDFViewer/PDFViewer.tsx:46
src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:47 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:71 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerRGB.tsx:47 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:47
src/SystemFolder/PDFViewer/PDFViewerContext.tsx:17 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/PDFViewer/PDFViewerContext.tsx:17
src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:10 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:75 — the two spans are one implementation copied and then locally edited — 179 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:10
src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:161 · src/SystemFolder/SystemResources/Placard/ClassicyPlacard.tsx:129 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:161
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:60 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:79 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:101 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:120 · +1 more site(s) not listed — all 5 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:60
src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:49 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:49
src/SystemFolder/SystemResources/Meter/ClassicyMeter.tsx:176 · src/SystemFolder/SystemResources/ProgressBar/ClassicyProgressBar.tsx:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/SystemResources/Meter/ClassicyMeter.tsx:176
src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:199 · src/SystemFolder/SystemResources/TextEditor/ClassicyTextEditor.tsx:122 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:199
src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:94 · src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:138 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:94
src/SystemFolder/PDFViewer/PDFViewer.tsx:82 · src/SystemFolder/WebViewer/WebViewer.tsx:104 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/SystemFolder/PDFViewer/PDFViewer.tsx:82
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
src/Appearance/__tests__/appearanceProbe.tsx:21 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — src/Appearance/__tests__/appearanceProbe.tsx:21
src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:8 imports pdfjs-dist/build/pdf.worker.min.mjs?url, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:8
src/__tests__/testAppsPackage.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — src/__tests__/testAppsPackage.ts:8
src/__tests__/testMirrorPackage.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — src/__tests__/testMirrorPackage.ts:7
src/__tests__/testRenamePackage.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — src/__tests__/testRenamePackage.ts:5
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
classicyDesktopEventHandler has cyclomatic complexity 119 and cognitive complexity 149; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:223
(anonymous) has cyclomatic complexity 116 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:90
classicyFinderEventHandler has cyclomatic complexity 74 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/Finder/FinderContext.tsx:182
ClassicyWindow has cyclomatic complexity 71 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:539
(anonymous) has cyclomatic complexity 61 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCardContext.tsx:89
classicyDesktopIconEventHandler has cyclomatic complexity 52 and cognitive complexity 112; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:264
(anonymous) has cyclomatic complexity 50 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:255
classicyWindowEventHandler has cyclomatic complexity 48 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140
execAction has cyclomatic complexity 48 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCardEngine.ts:159
classicyAppEventHandler has cyclomatic complexity 41 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:288
handleKeyDown has cyclomatic complexity 38 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:407
ClassicyFileDialog has cyclomatic complexity 36 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:155
(anonymous) has cyclomatic complexity 35 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaverContext.tsx:96
ClassicyBevelButton has cyclomatic complexity 35 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:252
HyperCard has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCard.tsx:119
move has cyclomatic complexity 31 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:820
renderPart has cyclomatic complexity 28 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCardCard.tsx:159
(anonymous) has cyclomatic complexity 27 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:478
ClassicyTreeNodeItem has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:190
(anonymous) has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:737
(anonymous) has cyclomatic complexity 24 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Appearance/ClassicyAppearancePackageSchema.ts:109
onButtonKeyDown has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:434
visit has cyclomatic complexity 22 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/__tests__/platinumCoreImports.test.ts:44
ClassicySlider has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:195
(anonymous) has cyclomatic complexity 21 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/Appearance/ClassicyStructureWithoutPackage.test.tsx:207
ClassicyPopUpMenu has cyclomatic complexity 21 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:166
traceClassicyDragOutline has cyclomatic complexity 20 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:37
(anonymous) has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:441
(anonymous) has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts:101
parsePrimary has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCardExpression.ts:215
(anonymous) has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1549
(anonymous) has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/Extensions/AppleGuide/AppleGuideContext.tsx:94
handler has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyShortcutDispatcher.ts:32
ClassicyControlStrip has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:251
(anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:258
classicyDateTimeManagerEventHandler has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeEventHandler.ts:35
onKeyDown has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:120
(anonymous) has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/HyperCard/HyperCard.tsx:327
moveClassicyFileSystemItems has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/File/ClassicyFileMove.ts:149
(anonymous) has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:364
Do you agree with this assessment?
R3 · Large Files6.2 / 10Adequate✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx has 1976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1
src/SystemFolder/HyperCard/HyperCard.tsx has 1163 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/HyperCard/HyperCard.tsx:1
src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts has 1012 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx has 895 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts:1
src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx has 790 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:1
src/SystemFolder/Finder/Finder.tsx has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/Finder/Finder.tsx:1
src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:1
src/Appearance/ClassicyAssetRegistry.ts has 659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Appearance/ClassicyAssetRegistry.ts:1
src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:1
src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:1
src/SystemFolder/SystemResources/Table/ClassicyTable.tsx has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:1
src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:1
src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx has 612 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx has 601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:1
src/SystemFolder/Finder/FinderContext.tsx has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/Finder/FinderContext.tsx:1
src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:1
src/SystemFolder/HyperCard/HyperCardEngine.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/HyperCard/HyperCardEngine.ts:1
src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx has 551 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:1
src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:1
src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx:1
src/SystemFolder/SimpleText/SimpleText.tsx has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SimpleText/SimpleText.tsx:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts:1
src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx has 511 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:1
src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx:1
src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts:1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts:1
src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:1
src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx:1
src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx:1
src/Appearance/ClassicyWallpaperIndex.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/Appearance/ClassicyWallpaperIndex.ts:1
src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:1
src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×2) — src/Appearance/ClassicyAppearancePackageSchema.ts:44, src/Appearance/ClassicyAppearancePackageSchema.ts:261
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. 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 `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document1.8 / 10Critical✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`deepMergeReplacingArrays` is exported, takes a document from its caller (line 57) and hands it to `mergeInto`, which calls itself at line 71 (`mergeInto`) with a piece of `target` — and nowhere in `mergeInto` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeInto` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/SystemFolder/SystemResources/Utils/deepMerge.ts:71
`validateHandlers` is exported, takes a document from its caller (line 58) and hands it to `validateActionList`, which calls itself at line 104 (`validateActionList`) with a piece of `actions` — and nowhere in `validateActionList` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validateActionList` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/SystemFolder/HyperCard/Editor/HyperCardScriptModel.ts:104
`getTheme` is exported, takes a document from its caller (line 368) and hands it to `mergeDeep`, which calls itself at line 401 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearance.ts:401
`registerClassicyAssets` is exported, takes a document from its caller (line 261) and hands it to `mergeInto`, which calls itself at line 196 (`mergeInto`) with a piece of `target` — and nowhere in `mergeInto` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeInto` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/Appearance/ClassicyAssetRegistry.ts:196
`registerClassicyAssets` is exported, takes a document from its caller (line 261) and hands it to `validLeaves`, which calls itself at line 238 (`validLeaves`) with a piece of `tree` — and nowhere in `validLeaves` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validLeaves` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/Appearance/ClassicyAssetRegistry.ts:238
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. 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 question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`readHyperCardStackFileText` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/SystemFolder/HyperCard/HyperCardStackFile.ts:14
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. 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?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×12) — src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:398, src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:201, src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:268, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~0.1 `!` null assertions per 1k TypeScript source lines — 4 assertion(s) across the 66395 source line(s) of the 343 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts (3), src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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 — 3 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.
P12 CI test-gate honesty — 2 observation(s) recorded · 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'.
X10 Duplicated predicate — 19 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 54 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.
AX1 Captive dependencies — Not applicable: this repository's TypeScript 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 — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
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
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 14 — a file the compose project references is missing) — env file example/.env not found: stat example/.env: no such file or directory; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D14 License Compliance — Not scored — this repository's 100 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 4 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
D16 Bus Factor — bus factor 1 — one contributor carries this repository
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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"]`.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D32 Data Compliance (PII/GDPR) — 74 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P2 Observability — This repository's JavaScript/TypeScript source (2 module(s), 333 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
S1 Web-Security Posture — Not assessed: 343 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Critical — 23 finding(s)
AC2 · Forms & labels· <input> without a programmatic label · ×12
<input> without a programmatic label src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:391— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:304— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:321— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:338— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/FileInput/ClassicyFileInput.tsx:189— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/QuickTime/QuickTimeSeekBar.tsx:43— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/QuickTime/QuickTimeVolumeControl.tsx:24— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/RadioInput/ClassicyRadioInput.tsx:220— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:219— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:319— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:342— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:358— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <tr> · ×2
Click handler on a non-interactive <tr> src/SystemFolder/ControlPanels/DriveSetup/DriveSetupList.tsx:44— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <tr> src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:620— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx:327— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label src/SystemFolder/SystemResources/TextEditor/ClassicyTextEditor.tsx:141— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:364— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC4 · Keyboard semantics· Click handler on a non-interactive <th> · ×1
Click handler on a non-interactive <th> src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:545— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabIndex={0}.
AC4 · Keyboard semantics· Double-click handler on a non-interactive <div> · ×1
Double-click handler on a non-interactive <div> src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:113— This <div> binds mousedown and double-click — pointer gestures with no keyboard form, a double-click among them. No click, no key handler, and no tabIndex={0}, so it cannot even take focus. Nothing synthesises a double-click from the keyboard: Enter and Space fire a single click, and only on a native <button> or <a href>. So this behaviour has no keyboard path at all. Expose the same action on a real control, or add role + tabIndex={0} + a key handler alongside the double-click.
Hotspot: src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:539— src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 209 in ClassicyWindow.ClassicyWindow at line 539. 3 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:223— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 120 in ClassicyDesktopManager.classicyDesktopEventHandler at line 223. 1 of those changes was a fix/bug commit, and the other 12 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/HyperCard/HyperCard.tsx src/SystemFolder/HyperCard/HyperCard.tsx:119— src/SystemFolder/HyperCard/HyperCard.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 107 in HyperCard.HyperCard at line 119. 1 of those changes was a fix/bug commit, and the other 8 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/HyperCard/HyperCard.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:160— src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in ClassicyDesktop.ClassicyDesktopInner at line 160. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:155— src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in ClassicyFileDialog.ClassicyFileDialog at line 155. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:252— src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in ClassicyBevelButton.ClassicyBevelButton at line 252. 1 of those changes was a fix/bug commit, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx:178— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 58 in ClassicyDesktopIcon.ClassicyDesktopIcon at line 178. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:166— src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 75 in ClassicyPopUpMenu.ClassicyPopUpMenu at line 166. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/App/ClassicyApp.tsx src/SystemFolder/SystemResources/App/ClassicyApp.tsx:129— src/SystemFolder/SystemResources/App/ClassicyApp.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in ClassicyApp.ClassicyApp at line 129. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/App/ClassicyApp.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:108— src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in ClassicyTimePicker.ClassicyTimePicker at line 108. 2 of those changes were fix/bug commits, and the other 4 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Table/ClassicyTable.tsx src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:183— src/SystemFolder/SystemResources/Table/ClassicyTable.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 77 in ClassicyTable.ClassicyTable at line 183. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Table/ClassicyTable.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/Finder/FinderContext.tsx src/SystemFolder/Finder/FinderContext.tsx:182— src/SystemFolder/Finder/FinderContext.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in FinderContext.classicyFinderEventHandler at line 182. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/Finder/FinderContext.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx:106— src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in ClassicyFileBrowserViewTable.ClassicyFileBrowserViewTable at line 106. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 49 in ClassicyDesktopWindowManagerContext.classicyWindowEventHandler at line 140. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/Finder/Finder.tsx src/SystemFolder/Finder/Finder.tsx:343— src/SystemFolder/Finder/Finder.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in Finder.Finder at line 343. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/Finder/Finder.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:258— src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in ClassicyMenu.ClassicyMenuItemComponent at line 258. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SimpleText/SimpleText.tsx src/SystemFolder/SimpleText/SimpleText.tsx:77— src/SystemFolder/SimpleText/SimpleText.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in SimpleText.SimpleText at line 77. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SimpleText/SimpleText.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:251— src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 52 in ClassicyControlStrip.ClassicyControlStrip at line 251. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:264— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in ClassicyDesktopIconContext.classicyDesktopIconEventHandler at line 264. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:92— src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ClassicyDatePicker.ClassicyDatePicker at line 92. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:820— src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in ClassicyFileSystem.move at line 820. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:252— src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in ClassicySoundManagerUtils.ClassicySoundStateEventReducer at line 252. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:712— src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in ClassicyAppManagerUtils.sanitizeStateForPersistence at line 712. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx:165— src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ClassicyFileBrowser.ClassicyFileBrowser at line 165. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:116— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in Browser.Browser at line 116. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:06:20 +00:00' --until='2026-11-16 19:06:20 +00:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: HyperCardEditorContext.classicyHyperCardEditorEventHandler src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:87— FunctionTooLong — classicyHyperCardEditorEventHandler runs 369 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 269 over it, 3.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyAppearanceManager.ClassicyAppearanceManager src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:80— FunctionTooLong — ClassicyAppearanceManager runs 351 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 251 over it, 3.51× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyPopUpMenu.ClassicyPopUpMenu src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:166— FunctionTooLong — ClassicyPopUpMenu runs 350 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 250 over it, 3.50× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyTable.ClassicyTable src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:183— FunctionTooLong — ClassicyTable runs 346 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 246 over it, 3.46× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Finder.Finder src/SystemFolder/Finder/Finder.tsx:343— FunctionTooLong — Finder runs 277 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 177 over it, 2.77× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicySlider.ClassicySlider src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:195— FunctionTooLong — ClassicySlider runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyTabs.ClassicyTabs src/SystemFolder/SystemResources/Tabs/ClassicyTabs.tsx:136— FunctionTooLong — ClassicyTabs runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyDateAndTimeManager.ClassicyDateAndTimeManager src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:67— FunctionTooLong — ClassicyDateAndTimeManager runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyDesktopWindowManagerContext.classicyWindowEventHandler src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140— FunctionTooLong — classicyWindowEventHandler runs 168 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 68 over it, 1.68× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyListBox.ClassicyListBox src/SystemFolder/SystemResources/ListBox/ClassicyListBox.tsx:91— FunctionTooLong — ClassicyListBox runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyScreenSaverManager.ClassicyScreenSaverManager src/SystemFolder/ControlPanels/ScreenSaverManager/ClassicyScreenSaverManager.tsx:60— FunctionTooLong — ClassicyScreenSaverManager runs 156 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 56 over it, 1.56× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: Finder.FinderWindow src/SystemFolder/Finder/Finder.tsx:102— FunctionTooLong — FinderWindow runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: HyperCardEngine.execAction src/SystemFolder/HyperCard/HyperCardEngine.ts:159— FunctionTooLong — execAction runs 152 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 52 over it, 1.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyControlStripManager.ClassicyControlStripManager src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:51— FunctionTooLong — ClassicyControlStripManager runs 147 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 47 over it, 1.47× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyPlacard.ClassicyPlacard src/SystemFolder/SystemResources/Placard/ClassicyPlacard.tsx:72— FunctionTooLong — ClassicyPlacard runs 145 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 45 over it, 1.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyTree.ClassicyTreeNodeItem src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:190— FunctionTooLong — ClassicyTreeNodeItem runs 139 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 39 over it, 1.39× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: HyperCardContext.classicyHyperCardEventHandler src/SystemFolder/HyperCard/HyperCardContext.tsx:86— FunctionTooLong — classicyHyperCardEventHandler runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyAlert.ClassicyAlert src/SystemFolder/SystemResources/Alert/ClassicyAlert.tsx:179— FunctionTooLong — ClassicyAlert runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyColorPickerDialog.ClassicyColorPickerDialog src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerDialog.tsx:68— FunctionTooLong — ClassicyColorPickerDialog runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicySoundManager.ClassicySoundManager src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx:33— FunctionTooLong — ClassicySoundManager runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: MoviePlayer.MoviePlayer src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:129— FunctionTooLong — MoviePlayer runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyTree.ClassicyTree src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:388— FunctionTooLong — ClassicyTree runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyAppearanceManager.Fonts.useFontsTab src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:31— FunctionTooLong — useFontsTab runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: PictureViewer.QuickTimePictureViewer src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:91— FunctionTooLong — QuickTimePictureViewer runs 120 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 20 over it, 1.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: ClassicyDriveSetup.ClassicyDriveSetup src/SystemFolder/ControlPanels/DriveSetup/ClassicyDriveSetup.tsx:32— FunctionTooLong — ClassicyDriveSetup runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
+ 4 more in this group — see findings.md.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×24
Animation without a prefers-reduced-motion guard src/SystemFolder/SystemResources/ProgressBar/ClassicyProgressBar.scss:97— `.classicyProgressChasingArrows .classicyProgressChasingArrowsSpinner` moves (`animation: classicyChasingArrowsSpin 1s steps(8, end) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPicker.scss:212— `.classicyColorPickerCrayon` moves (`transition: transform 0.07s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Warp/_ClassicyScreenSaverWarp.scss:11— `.classicySaverWarpStars` moves (`animation: classicySaverWarpZoom 2s infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Spotlight/_ClassicyScreenSaverSpotlight.scss:8— `.classicySaverSpotlightMask` moves (`animation: classicySaverSpotlightMoveX 5s linear 0s infinite alternate,
classicySaverSpotlightMoveY 5.6s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Rainstorm/_ClassicyScreenSaverRainstorm.scss:19— `.classicySaverRainstormRain` moves (`animation-name: classicySaverRainstormFall`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Messages2/_ClassicyScreenSaverMessages2.scss:14— `.classicySaverMessages2Text` moves (`animation: classicySaverMessages2MoveX 8s linear 0s infinite alternate,
classicySaverMessages2MoveY 17.3s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Messages/_ClassicyScreenSaverMessages.scss:11— `.classicySaverMessagesText` moves (`animation: classicySaverMessagesMarquee var(--classicy-saver-messages-speed, 10s)
linear infinite,
classicySaverMessagesMove 30s steps(3) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Logo/_ClassicyScreenSaverLogo.scss:16— `.classicySaverLogoMark` moves (`animation: classicySaverLogoMoveX 5s linear 0s infinite alternate,
classicySaverLogoMoveY 6.3s linear 0s infinite alternate`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/HardRain/_ClassicyScreenSaverHardRain.scss:23— `.classicySaverHardRainDrop` moves (`animation: classicySaverHardRainDrip 4.5s ease-in-out infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Globe/_ClassicyScreenSaverGlobe.scss:14— `.classicySaverGlobeBall` moves (`animation: classicySaverGlobeMoveX 3s linear 0s infinite alternate,
classicySaverGlobeMoveY 3.4s linear 0s infinite alternate,
classicySaverGlobeSpin 1.4s steps(21) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:25— `.classicySaverFlyingToastersVariant-t1` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:30— `.classicySaverFlyingToastersVariant-t2` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:35— `.classicySaverFlyingToastersVariant-t3` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:40— `.classicySaverFlyingToastersVariant-t4` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 10s 5s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:45— `.classicySaverFlyingToastersVariant-t5` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 4s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:50— `.classicySaverFlyingToastersVariant-t6` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s 8s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:55— `.classicySaverFlyingToastersVariant-t7` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 12s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:60— `.classicySaverFlyingToastersVariant-t8` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate,
classicySaverFlyingToastersFly 24s 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:65— `.classicySaverFlyingToastersVariant-t9` moves (`animation: classicySaverFlyingToastersFlap 0.2s steps(4) infinite alternate-reverse,
classicySaverFlyingToastersFly 24s 20s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:71— `.classicySaverFlyingToastersVariant-tst1` moves (`animation: classicySaverFlyingToastersFly 10s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:74— `.classicySaverFlyingToastersVariant-tst2` moves (`animation: classicySaverFlyingToastersFly 16s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:77— `.classicySaverFlyingToastersVariant-tst3` moves (`animation: classicySaverFlyingToastersFly 24s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/FlyingToasters/_ClassicyScreenSaverFlyingToasters.scss:80— `.classicySaverFlyingToastersVariant-tst4` moves (`animation: classicySaverFlyingToastersFly 24s 12s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard packages/appearance/platinum/src/screenSavers/Fish/_ClassicyScreenSaverFish.scss:18— `.classicySaverFishBubbles` moves (`animation: classicySaverFishRise 13s linear infinite,
classicySaverFishReappear 39s steps(3) linear infinite,
classicySaverFishBubbleAlt 0.2s steps(2) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×16
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.scss:35— `.classicyTimePicker input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.scss:30— `.classicyTimePicker input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/Spinner/ClassicySpinner.scss:31— `.classicySpinner:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/Spinner/ClassicySpinner.scss:26— `.classicySpinner` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/Slider/ClassicySlider.scss:31— `.classicySlider` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/QuickTime/QuickTimeMovieEmbed.scss:128— `.quickTimePlayerVideoControlsProgressBar:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/ListBox/ClassicyListBox.scss:31— `.classicyListBoxOption` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalent.scss:41— `.classicyKeyboardEquivalentDialog` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.scss:26— `.classicyFileBrowserViewTableContainer.classicyTableContainer:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/File/ClassicyFileDrag.scss:35— `.classicyFileBrowserFill.classicyFileDropTarget` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/File/ClassicyFileDrag.scss:50— `.classicyIcon.classicyFileDropTarget` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.scss:17— `.classicyDesktopIcon` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.scss:42— `.classicyDesktop .classicyDesktopIcon:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.scss:33— `.classicyDatePicker input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.scss:30— `.classicyDatePicker input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/SystemFolder/HyperCard/HyperCard.scss:170— `.classicyHyperCardEditorOverlay` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:398— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:201— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:268— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:348— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:354— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:719— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/Boot/ClassicyStartupScreenSession.ts:15— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/Boot/ClassicyStartupScreenSession.ts:27— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/SystemResources/App/ClassicyEditCommands.ts:187— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:252— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/HyperCard/Editor/HyperCardEditorOverlay.tsx:96— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx:288— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Sync-over-async blocking bin/parity/parity.ts:80— `readFileSync` in `run` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityApp.ts:175— `writeFileSync` in `stableShot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityApp.ts:246— `mkdirSync` in `shootApp` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityShoot.ts:125— `mkdirSync` in `shootStories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityShoot.ts:126— `writeFileSync` in `shootStories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityShoot.ts:167— `writeFileSync` in `callback to onStory` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityShoot.ts:188— `writeFileSync` in `callback to runPool` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityShoot.ts:201— `writeFileSync` in `shootStories` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking bin/parity/parityStories.ts:36— `readFileSync` in `resolveStoryIds` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
FileTooLong: Window/ClassicyWindow.tsx src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx— FileTooLong — 1165 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: ClassicyWindow (539-2074). The bar is 500 significant lines; this is 665 over it, 2.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: HyperCard/HyperCard.tsx src/SystemFolder/HyperCard/HyperCard.tsx— FileTooLong — 812 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: HyperCard (119-1202). The bar is 500 significant lines; this is 312 over it, 1.62× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Desktop/ClassicyDesktop.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx— FileTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: ClassicyDesktopInner (160-871). The bar is 500 significant lines; this is 139 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: File/ClassicyFileSystem.ts src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts— FileTooLong — 626 significant lines (blank, comment-only and punctuation-only lines excluded), about 86% of them inside a single declaration: ClassicyFileSystem (155-1094). The bar is 500 significant lines; this is 126 over it, 1.25× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Finder/Finder.tsx src/SystemFolder/Finder/Finder.tsx— FileTooLong — 547 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 47 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: AppearanceManager/ClassicyThemeDerivations.ts src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts— FileTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 44 over it, 1.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Desktop/ClassicyDesktopManager.tsx src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx— FileTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: classicyDesktopEventHandler (223-807). The bar is 500 significant lines; this is 14 over it, 1.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Boundary violation [package:test-cross-package-internals] src/Appearance/__tests__/appearanceProbe.tsx:21— src/Appearance/__tests__/appearanceProbe.tsx:21 reaches past another workspace package's public entry into its internals with a relative path (../../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:third-party-deep-import] src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:8— src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:8 imports pdfjs-dist/build/pdf.worker.min.mjs?url, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:test-cross-package-internals] src/__tests__/testAppsPackage.ts:8— src/__tests__/testAppsPackage.ts:8 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] src/__tests__/testMirrorPackage.ts:7— src/__tests__/testMirrorPackage.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] src/__tests__/testRenamePackage.ts:5— src/__tests__/testRenamePackage.ts:5 reaches past another workspace package's public entry into its internals with a relative path (../../packages/appearance/platinum/src/assets/sounds/platinum) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×5
Recursive walk over a caller-supplied document has no depth cap src/SystemFolder/SystemResources/Utils/deepMerge.ts:71— `deepMergeReplacingArrays` is exported, takes a document from its caller (line 57) and hands it to `mergeInto`, which calls itself at line 71 (`mergeInto`) with a piece of `target` — and nowhere in `mergeInto` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeInto` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/SystemFolder/HyperCard/Editor/HyperCardScriptModel.ts:104— `validateHandlers` is exported, takes a document from its caller (line 58) and hands it to `validateActionList`, which calls itself at line 104 (`validateActionList`) with a piece of `actions` — and nowhere in `validateActionList` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validateActionList` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearance.ts:401— `getTheme` is exported, takes a document from its caller (line 368) and hands it to `mergeDeep`, which calls itself at line 401 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/Appearance/ClassicyAssetRegistry.ts:196— `registerClassicyAssets` is exported, takes a document from its caller (line 261) and hands it to `mergeInto`, which calls itself at line 196 (`mergeInto`) with a piece of `target` — and nowhere in `mergeInto` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeInto` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Recursive walk over a caller-supplied document has no depth cap src/Appearance/ClassicyAssetRegistry.ts:238— `registerClassicyAssets` is exported, takes a document from its caller (line 261) and hands it to `validLeaves`, which calls itself at line 238 (`validLeaves`) with a piece of `tree` — and nowhere in `validLeaves` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validLeaves` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
Change coupling: ClassicyAppearanceManager.tsx ↔ ClassicySoundManager.tsx src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:1— `src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx` and `src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e9b0cb9a` Housekeeping: HIG audit status, divider comments, InputDialog stories…; `c9531b40` feat(app): desktop icon balloons fall back to the app's manifest desc…; `84847b37` feat(desktop): wire icon balloon help through and migrate consumers — run `git show` on any of them.
Change coupling: ClassicyDateAndTimeManager.tsx ↔ ClassicySoundManager.tsx src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:1— `src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx` and `src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e9b0cb9a` Housekeeping: HIG audit status, divider comments, InputDialog stories…; `c9531b40` feat(app): desktop icon balloons fall back to the app's manifest desc…; `84847b37` feat(desktop): wire icon balloon help through and migrate consumers — run `git show` on any of them.
Change coupling: MoviePlayer.tsx ↔ PictureViewer.tsx src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:1— `src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx` and `src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `f55d2b2d` fix(analytics): keep media document names out of GA pageview paths; `7f9ae15c` feat(apps): hide desktop icons for the bundled apps; `0c82e092` Remove default opens — run `git show` on any of them.
Change coupling: ClassicyDatePicker.tsx ↔ ClassicyTimePicker.tsx src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:1— `src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx` and `src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `989345e1` Pickers follow prefillValue and the virtual clock; settle no-op props…; `60084291` Fix duplicate DOM ids and labels that point nowhere (#309, #310) (#322); `7d9be02a` Spinner fixes (#259) — run `git show` on any of them.
Duplicated block (19 lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:49— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:49 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:48 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) src/SystemFolder/SystemResources/Meter/ClassicyMeter.tsx:176— src/SystemFolder/SystemResources/Meter/ClassicyMeter.tsx:176 · src/SystemFolder/SystemResources/ProgressBar/ClassicyProgressBar.tsx:139 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:199— src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:199 · src/SystemFolder/SystemResources/TextEditor/ClassicyTextEditor.tsx:122 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:94— src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:94 · src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.tsx:138 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
No assertions: is MDXEditor's MDXEditorMethods src/SystemFolder/SystemResources/RichTextEditor/ClassicyRichTextEditor.test.ts:11— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: requires trust in the types src/SystemFolder/Finder/FinderOpenWithTrust.test.ts:346— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:314— // TODO: We need to separate onClickFunc from here; it's being stored in the localstorage cache which — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment src/SystemFolder/Finder/FinderContext.tsx:352— // TODO: What will this do? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
ClassicyTable.ClassicyTable::handleKeyDown (cognitive 36) src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:407— ClassicyTable.ClassicyTable::handleKeyDown has cognitive complexity 36 (threshold 15). Drivers by points: if/else 12 (20 pts), boolean chains 10, ternaries 3 (5 pts), match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ClassicyTable.ClassicyTable::applySelection) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassicyTable.ClassicyTable::applySelection (cognitive 19) src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:353— ClassicyTable.ClassicyTable::applySelection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), boolean chains 3 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function. This shape REPEATS in the file: one other method here (ClassicyTable.ClassicyTable::handleKeyDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassTooLong: ClassicyWindow src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1— ClassTooLong — 958 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 558 over it, 2.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HyperCard src/SystemFolder/HyperCard/HyperCard.tsx:1— ClassTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 323 over it, 1.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
P12 · CI test-gate honesty· Runner config excludes tests no gate runs · ×2
Runner config excludes tests no gate runs packages/appearance/platinum/vite.config.ts:90— `**/*.test.ts` removes 196 test(s) in 21 file(s) (e.g. `packages/appearance/platinum/src/ClassicyPlatinum.test.ts`, `packages/appearance/platinum/src/PlatinumJsonExport.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Runner config excludes tests no gate runs packages/appearance/platinum/vite.config.ts:91— `**/*.test.tsx` removes 49 test(s) in 8 file(s) (e.g. `packages/appearance/platinum/src/hooks.controls.test.tsx`, `packages/appearance/platinum/src/hooks.surfaces.test.tsx`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
Duplicated block (23 lines × 2 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:453— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:453 · src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:193 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (23 lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerUtils.tsx:19— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerUtils.tsx:19 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerUtils.tsx:5 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (22 lines × 3 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:464— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:464 · src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeManager.tsx:202 · src/SystemFolder/ControlPanels/DriveSetup/ClassicyDriveSetup.tsx:97 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (22 lines × 3 locations) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:47— src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:47 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerCMYK.tsx:71 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerRGB.tsx:47 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
AC1 · Text alternatives· <canvas> without a text alternative · ×1
<canvas> without a text alternative src/SystemFolder/SystemResources/ColorPicker/ClassicyColorWheel.tsx:157— A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC3 · Page structure· Heading level jumps from h1 to h5 · ×1
Heading level jumps from h1 to h5 src/SystemFolder/SystemResources/AboutWindow/ClassicyAboutWindow.tsx:114— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButtonPopup.tsx:205— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
ClassicyWindow.ClassicyWindow (cyclomatic 209) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:539— ClassicyWindow.ClassicyWindow has cyclomatic complexity 209 (threshold 15). Of this number, 71 points are the body's own statements and 138 belong to 45 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HyperCardEditorContext.classicyHyperCardEditorEventHandler (cyclomatic 156) src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:87— HyperCardEditorContext.classicyHyperCardEditorEventHandler has cyclomatic complexity 156 (threshold 15). Of this number, 108 points are the body's own statements and 48 belong to 13 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyDesktopManager.classicyDesktopEventHandler (cyclomatic 120) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:223— ClassicyDesktopManager.classicyDesktopEventHandler has cyclomatic complexity 120 (threshold 15). Of this number, 113 points are the body's own statements and 7 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HyperCard.HyperCard (cyclomatic 107) src/SystemFolder/HyperCard/HyperCard.tsx:119— HyperCard.HyperCard has cyclomatic complexity 107 (threshold 15). Of this number, 31 points are the body's own statements and 76 belong to 29 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyFileDialog.ClassicyFileDialog (cyclomatic 85) src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:155— ClassicyFileDialog.ClassicyFileDialog has cyclomatic complexity 85 (threshold 15). Of this number, 34 points are the body's own statements and 51 belong to 14 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicyBevelButton.ClassicyBevelButton (cyclomatic 73) src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:252— ClassicyBevelButton.ClassicyBevelButton has cyclomatic complexity 73 (threshold 15). Of this number, 31 points are the body's own statements and 42 belong to 14 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicyDesktop.ClassicyDesktopInner (cyclomatic 73) src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:160— ClassicyDesktop.ClassicyDesktopInner has cyclomatic complexity 73 (threshold 15). Most of this is not in the body itself: 14 of the 73 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 364, a function literal at line 284, a function literal at line 305, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FinderContext.classicyFinderEventHandler (cyclomatic 70) src/SystemFolder/Finder/FinderContext.tsx:182— FinderContext.classicyFinderEventHandler has cyclomatic complexity 70 (threshold 15). Of this number, 67 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyComboBox.ClassicyComboBox (cyclomatic 59) src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:105— ClassicyComboBox.ClassicyComboBox has cyclomatic complexity 59 (threshold 15). Most of this is not in the body itself: 15 of the 59 points are its own statements and the rest belongs to 16 function items inside it that branch (handleKeyDown, a function literal at line 159, a function literal at line 296, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyDesktopIcon.ClassicyDesktopIcon (cyclomatic 58) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx:178— ClassicyDesktopIcon.ClassicyDesktopIcon has cyclomatic complexity 58 (threshold 15). Most of this is not in the body itself: 14 of the 58 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 397, launchIcon, clickFocus, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyControlStrip.ClassicyControlStrip (cyclomatic 52) src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:251— ClassicyControlStrip.ClassicyControlStrip has cyclomatic complexity 52 (threshold 15). Most of this is not in the body itself: 11 of the 52 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 478, a function literal at line 427, a function literal at line 450, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyDesktopIconContext.classicyDesktopIconEventHandler (cyclomatic 51) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:264— ClassicyDesktopIconContext.classicyDesktopIconEventHandler has cyclomatic complexity 51 (threshold 15). Of this number, 49 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyDesktopWindowManagerContext.classicyWindowEventHandler (cyclomatic 49) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140— ClassicyDesktopWindowManagerContext.classicyWindowEventHandler has cyclomatic complexity 49 (threshold 15). Of this number, 47 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HyperCardContext.classicyHyperCardEventHandler (cyclomatic 46) src/SystemFolder/HyperCard/HyperCardContext.tsx:86— HyperCardContext.classicyHyperCardEventHandler has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicySoundManagerUtils.ClassicySoundStateEventReducer (cyclomatic 44) src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:252— ClassicySoundManagerUtils.ClassicySoundStateEventReducer has cyclomatic complexity 44 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
check-pixel-literals.sassBindingsOf (cyclomatic 41) bin/check-pixel-literals.ts:460— check-pixel-literals.sassBindingsOf has cyclomatic complexity 41 (threshold 15). Of this number, 17 points are the body's own statements and 24 belong to 6 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyTimePicker.ClassicyTimePicker (cyclomatic 41) src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:108— ClassicyTimePicker.ClassicyTimePicker has cyclomatic complexity 41 (threshold 15). Most of this is not in the body itself: 7 of the 41 points are its own statements and the rest belongs to 7 function items inside it that branch (handleTimePartChange, stepTimePart, handleDateChange, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileBrowserViewTable.ClassicyFileBrowserViewTable (cyclomatic 40) src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx:106— ClassicyFileBrowserViewTable.ClassicyFileBrowserViewTable has cyclomatic complexity 40 (threshold 15). Most of this is not in the body itself: 1 of the 40 points is its own statement and the rest belongs to 15 function items inside it that branch (a function literal at line 313, a function literal at line 241, a function literal at line 142, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
check-pixel-literals.scanMultiplierLevel (cyclomatic 39) bin/check-pixel-literals.ts:656— check-pixel-literals.scanMultiplierLevel has cyclomatic complexity 39 (threshold 15). Of this number, 35 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyAppManager.classicyAppEventHandler (cyclomatic 38) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:288— ClassicyAppManager.classicyAppEventHandler has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyTable.ClassicyTable::handleKeyDown (cyclomatic 38) src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:407— ClassicyTable.ClassicyTable::handleKeyDown has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyListBox.ClassicyListBox (cyclomatic 37) src/SystemFolder/SystemResources/ListBox/ClassicyListBox.tsx:91— ClassicyListBox.ClassicyListBox has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 7 of the 37 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, applySelection, a function literal at line 242, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyMenu.ClassicyMenuItemComponent (cyclomatic 36) src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:258— ClassicyMenu.ClassicyMenuItemComponent has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 11 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicySlider.ClassicySlider (cyclomatic 36) src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:195— ClassicySlider.ClassicySlider has cyclomatic complexity 36 (threshold 15). Of this number, 21 points are the body's own statements and 15 belong to 9 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HyperCardEngine.execAction (cyclomatic 35) src/SystemFolder/HyperCard/HyperCardEngine.ts:159— HyperCardEngine.execAction has cyclomatic complexity 35 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SimpleText.SimpleText (cyclomatic 34) src/SystemFolder/SimpleText/SimpleText.tsx:77— SimpleText.SimpleText has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 136, 281, 125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyTabs.ClassicyTabs (cyclomatic 34) src/SystemFolder/SystemResources/Tabs/ClassicyTabs.tsx:136— ClassicyTabs.ClassicyTabs has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 5 of the 34 points are its own statements and the rest belongs to 9 function items inside it that branch (handleTabKeyDown, a function literal at line 219, stepScroll, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyScreenSaverContext.classicyScreenSaverEventHandler (cyclomatic 31) src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaverContext.tsx:93— ClassicyScreenSaverContext.classicyScreenSaverEventHandler has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyApp.ClassicyApp (cyclomatic 31) src/SystemFolder/SystemResources/App/ClassicyApp.tsx:129— ClassicyApp.ClassicyApp has cyclomatic complexity 31 (threshold 15). Most of this is not in the body itself: 6 of the 31 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 186, 322, 287, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Finder.Finder (cyclomatic 30) src/SystemFolder/Finder/Finder.tsx:343— Finder.Finder has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 7 of the 30 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 646, 390, 619, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HyperCardEditorOverlay.HyperCardEditorOverlay (cyclomatic 30) src/SystemFolder/HyperCard/Editor/HyperCardEditorOverlay.tsx:77— HyperCardEditorOverlay.HyperCardEditorOverlay has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 3 of the 30 points are its own statements and the rest belongs to 7 function items inside it that branch (onKeyDown, rectFor, onPointerUp, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyPlacard.ClassicyPlacard (cyclomatic 30) src/SystemFolder/SystemResources/Placard/ClassicyPlacard.tsx:72— ClassicyPlacard.ClassicyPlacard has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 12 of the 30 points are its own statements and the rest belongs to 10 function items inside it that branch (handleClick, a function literal at line 103, a function literal at line 112, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyTree.ClassicyTree (cyclomatic 30) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:388— ClassicyTree.ClassicyTree has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 478, 426, 425). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyFileSystem.move (cyclomatic 29) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:820— ClassicyFileSystem.move has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicySplitView.ClassicySplitView (cyclomatic 28) src/SystemFolder/SystemResources/SplitView/ClassicySplitView.tsx:155— ClassicySplitView.ClassicySplitView has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 5 of the 28 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 234, a function literal at line 293, a function literal at line 331, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
check-pixel-literals.evaluateArithmetic (cyclomatic 27) bin/check-pixel-literals.ts:330— check-pixel-literals.evaluateArithmetic has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (evaluate::primary, evaluate::product, evaluate::sum, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PDFViewerDocument.PDFViewerDocument (cyclomatic 27) src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:56— PDFViewerDocument.PDFViewerDocument has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 123, a function literal at line 162, handleWrapperClick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyTree.ClassicyTreeNodeItem (cyclomatic 27) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:190— ClassicyTree.ClassicyTreeNodeItem has cyclomatic complexity 27 (threshold 15). Of this number, 24 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyAppManagerUtils.sanitizeStateForPersistence (cyclomatic 25) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:712— ClassicyAppManagerUtils.sanitizeStateForPersistence has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 737, list). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyDatePicker.ClassicyDatePicker (cyclomatic 25) src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:92— ClassicyDatePicker.ClassicyDatePicker has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 4 of the 25 points are its own statements and the rest belongs to 7 function items inside it that branch (handleDatePartChange, clampDate, stepDatePart, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyKeyboardEquivalentDialog.ClassicyKeyboardEquivalentDialog (cyclomatic 25) src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:78— ClassicyKeyboardEquivalentDialog.ClassicyKeyboardEquivalentDialog has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 7 of the 25 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 120, 102, 118). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HyperCardInspector.HyperCardInspector (cyclomatic 24) src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx:87— HyperCardInspector.HyperCardInspector has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 7 function items inside it that branch (renderOptionField, a function literal at line 481, a function literal at line 281, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileDragOutline.traceClassicyDragOutline (cyclomatic 24) src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:37— ClassicyFileDragOutline.traceClassicyDragOutline has cyclomatic complexity 24 (threshold 15). Of this number, 20 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
ClassicyIcon.ClassicyIcon (cyclomatic 24) src/SystemFolder/SystemResources/Icon/ClassicyIcon.tsx:147— ClassicyIcon.ClassicyIcon has cyclomatic complexity 24 (threshold 15). Most of this is not in the body itself: 9 of the 24 points are its own statements and the rest belongs to 6 function items inside it that branch (stopChangeIcon, startDrag, a function literal at line 248, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyPopUpMenu.ClassicyPopUpMenu::onButtonKeyDown (cyclomatic 23) src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:434— ClassicyPopUpMenu.ClassicyPopUpMenu::onButtonKeyDown has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (ClassicyPopUpMenu.ClassicyPopUpMenu) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassicyButton.ClassicyButton (cyclomatic 22) src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:109— ClassicyButton.ClassicyButton has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, handleKeyUp, a function literal at line 142, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
QuickTimeMovieEmbed.QuickTimeVideoEmbed (cyclomatic 22) src/SystemFolder/SystemResources/QuickTime/QuickTimeMovieEmbed.tsx:122— QuickTimeMovieEmbed.QuickTimeVideoEmbed has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
parityArgs.parseParityArgs (cyclomatic 21) bin/parity/parityArgs.ts:76— parityArgs.parseParityArgs has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicyButtonToolbar.ClassicyButtonToolbar (cyclomatic 21) src/SystemFolder/SystemResources/ButtonToolbar/ClassicyButtonToolbar.tsx:160— ClassicyButtonToolbar.ClassicyButtonToolbar has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 258, 318, 172, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyDesktopMenuWidgetTime.ClassicyDesktopMenuWidgetTime (cyclomatic 21) src/SystemFolder/SystemResources/Desktop/MenuBar/Widgets/Time/ClassicyDesktopMenuWidgetTime.tsx:43— ClassicyDesktopMenuWidgetTime.ClassicyDesktopMenuWidgetTime has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicyLink.ClassicyLink (cyclomatic 21) src/SystemFolder/SystemResources/Link/ClassicyLink.tsx:74— ClassicyLink.ClassicyLink has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 7 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (activate, handleKeyDown). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyRadioInput.ClassicyRadioInput (cyclomatic 21) src/SystemFolder/SystemResources/RadioInput/ClassicyRadioInput.tsx:108— ClassicyRadioInput.ClassicyRadioInput has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 11 function items inside it that branch (pressItem, handleOnChange, a function literal at line 144, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyAlert.ClassicyAlert (cyclomatic 20) src/SystemFolder/SystemResources/Alert/ClassicyAlert.tsx:179— ClassicyAlert.ClassicyAlert has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 327, 216, 207, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyDesktopMenuBar.ClassicyDesktopMenuBarContent (cyclomatic 20) src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx:177— ClassicyDesktopMenuBar.ClassicyDesktopMenuBarContent has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 305, 267, 223, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
classicyCssCascade.classicySelectorSpecificity (cyclomatic 19) bin/classicyCssCascade.ts:106— classicyCssCascade.classicySelectorSpecificity has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyAppManager.classicyShortcutEventHandler (cyclomatic 19) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:438— ClassicyAppManager.classicyShortcutEventHandler has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyFileBrowser.ClassicyFileBrowser (cyclomatic 19) src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx:165— ClassicyFileBrowser.ClassicyFileBrowser has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 3 function items inside it that branch (onKeyDown, onContextMenu, a function literal at line 202). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyPopUpMenu.ClassicyPopUpMenu (cyclomatic 19) src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:166— ClassicyPopUpMenu.ClassicyPopUpMenu has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (ClassicyPopUpMenu.ClassicyPopUpMenu::onButtonKeyDown) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
parity.run (cyclomatic 18) bin/parity/parity.ts:56— parity.run has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyDateAndTimeEventHandler.classicyDateTimeManagerEventHandler (cyclomatic 18) src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeEventHandler.ts:35— ClassicyDateAndTimeEventHandler.classicyDateTimeManagerEventHandler has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Parser.parsePrimary (cyclomatic 18) src/SystemFolder/HyperCard/HyperCardExpression.ts:215— Parser.parsePrimary has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyBevelButtonPopup.ClassicyBevelButtonPopup (cyclomatic 18) src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButtonPopup.tsx:75— ClassicyBevelButtonPopup.ClassicyBevelButtonPopup has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (onMenuKeyDown, a function literal at line 112, a function literal at line 121, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
classicyFontStylesheet.findClassicyFontStylesheetProblems (cyclomatic 17) bin/classicyFontStylesheet.ts:109— classicyFontStylesheet.findClassicyFontStylesheetProblems has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
HyperCardModel.validateStack (cyclomatic 17) src/SystemFolder/HyperCard/HyperCardModel.ts:195— HyperCardModel.validateStack has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MoviePlayerContext.classicyQuickTimeMoviePlayerEventHandler (cyclomatic 17) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:28— MoviePlayerContext.classicyQuickTimeMoviePlayerEventHandler has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyShortcutDispatcher.useClassicyShortcutDispatcher (cyclomatic 17) src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyShortcutDispatcher.ts:22— ClassicyShortcutDispatcher.useClassicyShortcutDispatcher has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 32). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ClassicyFileDragOutline.drawClassicyDragOutline (cyclomatic 17) src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:103— ClassicyFileDragOutline.drawClassicyDragOutline has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyFileMove.moveClassicyFileSystemItems (cyclomatic 17) src/SystemFolder/SystemResources/File/ClassicyFileMove.ts:149— ClassicyFileMove.moveClassicyFileSystemItems has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassicyThemeFontSizes.withClassicyThemeFontSizesClamped (cyclomatic 16) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts:99— ClassicyThemeFontSizes.withClassicyThemeFontSizesClamped has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PictureViewerContext.classicyQuickTimePictureViewerEventHandler (cyclomatic 16) src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx:24— PictureViewerContext.classicyQuickTimePictureViewerEventHandler has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
useClassicyBalloonHelp.useClassicyBalloonHelp (cyclomatic 16) src/SystemFolder/SystemResources/BalloonHelp/useClassicyBalloonHelp.tsx:263— useClassicyBalloonHelp.useClassicyBalloonHelp has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 321, a function literal at line 293, hide, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileBrowserViewIcons.ClassicyFileBrowserViewIcons (cyclomatic 16) src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewIcons.tsx:91— ClassicyFileBrowserViewIcons.ClassicyFileBrowserViewIcons has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 137, 230, 142, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyKeyboardShortcut.keyFromEvent (cyclomatic 16) src/SystemFolder/SystemResources/Menu/ClassicyKeyboardShortcut.ts:254— ClassicyKeyboardShortcut.keyFromEvent has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicySpinner.ClassicySpinner (cyclomatic 16) src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:89— ClassicySpinner.ClassicySpinner has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (clamp, setInputRef, handleOnChangeFunc, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
bus factor 1 — one contributor carries this repository — 3 contributor(s) have commits in this repository (automation and bot accounts excluded), but the commits of a single one of them cover most of its history — 80% of the 1736 commit(s) sampled — so the number of people who actually carry it is 1. This is not the ambient state of a solo project: there ARE other contributors, and if the one who carries the repository becomes unavailable, the knowledge behind most of its history goes with them. Spread the next changes deliberately — have a second contributor review or pair on them — and write down the parts only one person can currently change.
HyperCardEditorContext.classicyHyperCardEditorEventHandler (cognitive 214) src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:87— HyperCardEditorContext.classicyHyperCardEditorEventHandler has cognitive complexity 214 (threshold 15). Drivers by points: if/else 82 (167 pts), boolean chains 25, loops 5 (12 pts), ternaries 3 (7 pts), match/switch 2 (3 pts) (nesting depth added 97). Of this number, 125 points are the body's own statements and 89 belong to 13 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HyperCard.HyperCard (cognitive 148) src/SystemFolder/HyperCard/HyperCard.tsx:119— HyperCard.HyperCard has cognitive complexity 148 (threshold 15). Drivers by points: ternaries 39 (59 pts), if/else 33 (56 pts), boolean chains 27, loops 4, error handling 1 (2 pts) (nesting depth added 44). Of this number, 39 points are the body's own statements and 109 belong to 29 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyDesktopManager.classicyDesktopEventHandler (cognitive 135) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:223— ClassicyDesktopManager.classicyDesktopEventHandler has cognitive complexity 135 (threshold 15). Drivers by points: if/else 53 (106 pts), ternaries 4 (10 pts), loops 3 (9 pts), boolean chains 7, match/switch 2 (3 pts) (nesting depth added 66). Of this number, 130 points are the body's own statements and 5 belong to 3 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FinderContext.classicyFinderEventHandler (cognitive 109) src/SystemFolder/Finder/FinderContext.tsx:182— FinderContext.classicyFinderEventHandler has cognitive complexity 109 (threshold 15). Drivers by points: if/else 36 (77 pts), ternaries 5 (14 pts), boolean chains 10, loops 2 (4 pts), error handling 1 (3 pts), match/switch 1 (nesting depth added 54). Of this number, 101 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyDesktopIconContext.classicyDesktopIconEventHandler (cognitive 89) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:264— ClassicyDesktopIconContext.classicyDesktopIconEventHandler has cognitive complexity 89 (threshold 15). Drivers by points: ternaries 14 (41 pts), if/else 16 (38 pts), boolean chains 6, loops 1 (3 pts), match/switch 1 (nesting depth added 51). Of this number, 87 points are the body's own statements and 2 belong to one function literal inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassicyAppManager.classicyAppEventHandler (cognitive 73) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:288— ClassicyAppManager.classicyAppEventHandler has cognitive complexity 73 (threshold 15). Drivers by points: if/else 23 (57 pts), loops 2 (7 pts), ternaries 2 (5 pts), boolean chains 3, match/switch 1 (nesting depth added 42). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
check-pixel-literals.sassBindingsOf (cognitive 72) bin/check-pixel-literals.ts:460— check-pixel-literals.sassBindingsOf has cognitive complexity 72 (threshold 15). Drivers by points: ternaries 9 (26 pts), if/else 12 (25 pts), loops 8 (12 pts), boolean chains 9 (nesting depth added 34). Of this number, 23 points are the body's own statements and 49 belong to 6 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyBevelButton.ClassicyBevelButton (cognitive 72) src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:252— ClassicyBevelButton.ClassicyBevelButton has cognitive complexity 72 (threshold 15). Drivers by points: if/else 33 (36 pts), boolean chains 19, ternaries 13 (17 pts) (nesting depth added 7). Of this number, 27 points are the body's own statements and 45 belong to 14 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ClassicyDesktop.ClassicyDesktopInner (cognitive 71) src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:160— ClassicyDesktop.ClassicyDesktopInner has cognitive complexity 71 (threshold 15). Drivers by points: if/else 29 (36 pts), boolean chains 23, ternaries 9 (10 pts), loops 2 (nesting depth added 8). Most of this is not in the body itself: 12 of the 71 points are its own statements and the rest belongs to 20 function items inside it that branch (a function literal at line 364, a function literal at line 284, startSelectBox, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
check-pixel-literals.scanMultiplierLevel (cognitive 67) bin/check-pixel-literals.ts:656— check-pixel-literals.scanMultiplierLevel has cognitive complexity 67 (threshold 15). Drivers by points: if/else 28 (44 pts), boolean chains 9, ternaries 3 (8 pts), loops 4 (6 pts) (nesting depth added 23). Of this number, 63 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HyperCardContext.classicyHyperCardEventHandler (cognitive 63) src/SystemFolder/HyperCard/HyperCardContext.tsx:86— HyperCardContext.classicyHyperCardEventHandler has cognitive complexity 63 (threshold 15). Drivers by points: if/else 29 (58 pts), boolean chains 4, match/switch 1 (nesting depth added 29). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyDesktopWindowManagerContext.classicyWindowEventHandler (cognitive 61) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140— ClassicyDesktopWindowManagerContext.classicyWindowEventHandler has cognitive complexity 61 (threshold 15). Drivers by points: if/else 27 (54 pts), boolean chains 6, match/switch 1 (nesting depth added 27). Of this number, 60 points are the body's own statements and 1 belongs to one function literal inside it that branches. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassicyDesktopIcon.ClassicyDesktopIcon (cognitive 59) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx:178— ClassicyDesktopIcon.ClassicyDesktopIcon has cognitive complexity 59 (threshold 15). Drivers by points: if/else 26 (27 pts), boolean chains 18, ternaries 12 (14 pts) (nesting depth added 3). Most of this is not in the body itself: 14 of the 59 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 397, launchIcon, clickFocus, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyComboBox.ClassicyComboBox (cognitive 58) src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:105— ClassicyComboBox.ClassicyComboBox has cognitive complexity 58 (threshold 15). Drivers by points: if/else 28 (36 pts), boolean chains 16, ternaries 4, loops 1, match/switch 1 (nesting depth added 8). Most of this is not in the body itself: 12 of the 58 points are its own statements and the rest belongs to 16 function items inside it that branch (handleKeyDown, a function literal at line 159, a function literal at line 242, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyTimePicker.ClassicyTimePicker (cognitive 48) src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:108— ClassicyTimePicker.ClassicyTimePicker has cognitive complexity 48 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 10 (16 pts), boolean chains 11, match/switch 2 (nesting depth added 12). Most of this is not in the body itself: 6 of the 48 points are its own statements and the rest belongs to 7 function items inside it that branch (handleDateChange, handleTimePartChange, stepTimePart, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicySoundManagerUtils.ClassicySoundStateEventReducer (cognitive 46) src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:252— ClassicySoundManagerUtils.ClassicySoundStateEventReducer has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (22 pts), ternaries 7 (18 pts), boolean chains 5, match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyControlStrip.ClassicyControlStrip (cognitive 43) src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:251— ClassicyControlStrip.ClassicyControlStrip has cognitive complexity 43 (threshold 15). Drivers by points: if/else 23, boolean chains 13, ternaries 7. Most of this is not in the body itself: 7 of the 43 points are its own statements and the rest belongs to 19 function items inside it that branch (a function literal at line 427, a function literal at line 478, a function literal at line 450, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileBrowserViewTable.ClassicyFileBrowserViewTable (cognitive 42) src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx:106— ClassicyFileBrowserViewTable.ClassicyFileBrowserViewTable has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (20 pts), ternaries 7 (12 pts), boolean chains 9, loops 1 (nesting depth added 6). None of this is in the body itself: all 42 points belong to 15 function items inside it that branch (a function literal at line 313, a function literal at line 241, a function literal at line 409, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyListBox.ClassicyListBox (cognitive 42) src/SystemFolder/SystemResources/ListBox/ClassicyListBox.tsx:91— ClassicyListBox.ClassicyListBox has cognitive complexity 42 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 14, ternaries 5 (7 pts) (nesting depth added 8). Most of this is not in the body itself: 6 of the 42 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, applySelection, a function literal at line 242, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyMenu.ClassicyMenuItemComponent (cognitive 42) src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:258— ClassicyMenu.ClassicyMenuItemComponent has cognitive complexity 42 (threshold 15). Drivers by points: if/else 19 (21 pts), ternaries 9 (13 pts), boolean chains 8 (nesting depth added 6). Of this number, 18 points are the body's own statements and 24 belong to 11 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ClassicyApp.ClassicyApp (cognitive 40) src/SystemFolder/SystemResources/App/ClassicyApp.tsx:129— ClassicyApp.ClassicyApp has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 7 (14 pts), boolean chains 9, loops 2 (nesting depth added 9). Most of this is not in the body itself: 5 of the 40 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 186, 322, 287, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyScreenSaverContext.classicyScreenSaverEventHandler (cognitive 39) src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaverContext.tsx:93— ClassicyScreenSaverContext.classicyScreenSaverEventHandler has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (24 pts), ternaries 4 (8 pts), boolean chains 6, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SimpleText.SimpleText (cognitive 39) src/SystemFolder/SimpleText/SimpleText.tsx:77— SimpleText.SimpleText has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (21 pts), ternaries 10 (11 pts), boolean chains 5, loops 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 39 points are its own statements and the rest belongs to 17 function literals inside it that branch (lines 136, 281, 199, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicySlider.ClassicySlider (cognitive 35) src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:195— ClassicySlider.ClassicySlider has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 11, ternaries 10 (nesting depth added 1). Of this number, 19 points are the body's own statements and 16 belong to 9 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassicyThemeFontSizes.withClassicyThemeFontSizesClamped (cognitive 34) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts:99— ClassicyThemeFontSizes.withClassicyThemeFontSizesClamped has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 3 (7 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAppManagerUtils.sanitizeStateForPersistence (cognitive 33) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:712— ClassicyAppManagerUtils.sanitizeStateForPersistence has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 8, loops 4 (7 pts), ternaries 2 (nesting depth added 9). Most of this is not in the body itself: 1 of the 33 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 737, list). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyWindow.ClassicyWindow (cognitive 33) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:539— ClassicyWindow.ClassicyWindow has cognitive complexity 33 (threshold 15). Drivers by points: if/else 72 (79 pts), boolean chains 63, ternaries 19 (22 pts) (nesting depth added 10). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (ClassicyWindow.ClassicyWindow::computeStandardRect) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
HyperCardInspector.HyperCardInspector (cognitive 32) src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx:87— HyperCardInspector.HyperCardInspector has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 10 (14 pts), if/else 10 (13 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 8). Most of this is not in the body itself: 2 of the 32 points are its own statements and the rest belongs to 7 function items inside it that branch (renderOptionField, a function literal at line 309, a function literal at line 481, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyPlacard.ClassicyPlacard (cognitive 32) src/SystemFolder/SystemResources/Placard/ClassicyPlacard.tsx:72— ClassicyPlacard.ClassicyPlacard has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 12, ternaries 3 (5 pts) (nesting depth added 4). Most of this is not in the body itself: 12 of the 32 points are its own statements and the rest belongs to 10 function items inside it that branch (handleClick, a function literal at line 103, a function literal at line 112, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyTree.ClassicyTree (cognitive 32) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:388— ClassicyTree.ClassicyTree has cognitive complexity 32 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 6, ternaries 4, match/switch 1 (nesting depth added 9). Most of this is not in the body itself: 1 of the 32 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 478, 426, 425). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
check-pixel-literals.evaluateArithmetic (cognitive 31) bin/check-pixel-literals.ts:330— check-pixel-literals.evaluateArithmetic has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 5 (7 pts), boolean chains 4, loops 4 (nesting depth added 7). Most of this is not in the body itself: 11 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (evaluate::primary, evaluate::product, evaluate::sum, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileDragOutline.traceClassicyDragOutline (cognitive 31) src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:37— ClassicyFileDragOutline.traceClassicyDragOutline has cognitive complexity 31 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 5 (9 pts), boolean chains 6 (nesting depth added 15). Of this number, 30 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicySplitView.ClassicySplitView (cognitive 31) src/SystemFolder/SystemResources/SplitView/ClassicySplitView.tsx:155— ClassicySplitView.ClassicySplitView has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (18 pts), if/else 9 (10 pts), boolean chains 3 (nesting depth added 6). Most of this is not in the body itself: 4 of the 31 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 234, a function literal at line 293, axisTotal, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Finder.Finder (cognitive 30) src/SystemFolder/Finder/Finder.tsx:343— Finder.Finder has cognitive complexity 30 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 11 (12 pts), boolean chains 4, loops 2 (nesting depth added 3). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 646, 390, 619, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyTree.ClassicyTreeNodeItem (cognitive 30) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:190— ClassicyTree.ClassicyTreeNodeItem has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 6 (13 pts), boolean chains 11, if/else 3 (6 pts) (nesting depth added 10). Of this number, 24 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyFontStylesheet.findClassicyFontStylesheetProblems (cognitive 29) bin/classicyFontStylesheet.ts:109— classicyFontStylesheet.findClassicyFontStylesheetProblems has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HyperCardEditorOverlay.HyperCardEditorOverlay (cognitive 29) src/SystemFolder/HyperCard/Editor/HyperCardEditorOverlay.tsx:77— HyperCardEditorOverlay.HyperCardEditorOverlay has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15, boolean chains 9, ternaries 3 (4 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 2 of the 29 points are its own statements and the rest belongs to 7 function items inside it that branch (onKeyDown, onPointerUp, rectFor, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyTabs.ClassicyTabs (cognitive 28) src/SystemFolder/SystemResources/Tabs/ClassicyTabs.tsx:136— ClassicyTabs.ClassicyTabs has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10, ternaries 9 (10 pts), boolean chains 7, match/switch 1 (nesting depth added 1). Most of this is not in the body itself: 4 of the 28 points are its own statements and the rest belongs to 9 function items inside it that branch (stepScroll, a function literal at line 219, a function literal at line 196, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
PDFViewerDocument.PDFViewerDocument (cognitive 27) src/SystemFolder/PDFViewer/PDFViewerDocument.tsx:56— PDFViewerDocument.PDFViewerDocument has cognitive complexity 27 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 4, ternaries 4, error handling 2 (nesting depth added 1). Most of this is not in the body itself: 4 of the 27 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 123, a function literal at line 162, handleWrapperClick, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
generate-vocabulary.vocabularyShapeErrors (cognitive 26) bin/generate-vocabulary.ts:43— generate-vocabulary.vocabularyShapeErrors has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyThemeMetrics.classicyMeasurementVars (cognitive 26) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts:455— ClassicyThemeMetrics.classicyMeasurementVars has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 2 (9 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyIcon.ClassicyIcon (cognitive 26) src/SystemFolder/SystemResources/Icon/ClassicyIcon.tsx:147— ClassicyIcon.ClassicyIcon has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 9 (10 pts), boolean chains 3 (nesting depth added 4). Most of this is not in the body itself: 8 of the 26 points are its own statements and the rest belongs to 6 function items inside it that branch (startDrag, stopChangeIcon, a function literal at line 248, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileMove.moveClassicyFileSystemItems (cognitive 25) src/SystemFolder/SystemResources/File/ClassicyFileMove.ts:149— ClassicyFileMove.moveClassicyFileSystemItems has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 4 (8 pts), boolean chains 2, loops 1 (nesting depth added 9). Of this number, 19 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Parser.parsePrimary (cognitive 24) src/SystemFolder/HyperCard/HyperCardExpression.ts:215— Parser.parsePrimary has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAppManagerUtils.loadInitialState (cognitive 23) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:397— ClassicyAppManagerUtils.loadInitialState has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 3 (11 pts), if/else 4 (9 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
HyperCardEngine.execAction (cognitive 23) src/SystemFolder/HyperCard/HyperCardEngine.ts:159— HyperCardEngine.execAction has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 3 (6 pts), boolean chains 2, match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HyperCardModel.validateStack (cognitive 23) src/SystemFolder/HyperCard/HyperCardModel.ts:195— HyperCardModel.validateStack has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (19 pts), boolean chains 4 (nesting depth added 5). Most of this is not in the body itself: 10 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 210, 231). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyDesktopMenuBar.ClassicyDesktopMenuBarContent (cognitive 23) src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx:177— ClassicyDesktopMenuBar.ClassicyDesktopMenuBarContent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6, ternaries 6 (nesting depth added 3). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 305, 267, 223, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyFileDragOutline.drawClassicyDragOutline (cognitive 23) src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:103— ClassicyFileDragOutline.drawClassicyDragOutline has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 5 (6 pts), ternaries 2, boolean chains 1, error handling 1 (nesting depth added 7). Of this number, 21 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyFileSystem.move (cognitive 23) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:820— ClassicyFileSystem.move has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7, ternaries 4, loops 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
classicyBaseCss.itemEnd (cognitive 22) bin/classicyBaseCss.ts:23— classicyBaseCss.itemEnd has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.classicySelectorSpecificity (cognitive 22) bin/classicyCssCascade.ts:106— classicyCssCascade.classicySelectorSpecificity has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, ternaries 1 (3 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyDatePicker.ClassicyDatePicker (cognitive 22) src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:92— ClassicyDatePicker.ClassicyDatePicker has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, match/switch 2, ternaries 2 (nesting depth added 2). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (handleDatePartChange, clampDate, setMonthRef, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyDesktopKeyNav.nearestIconInDirection (cognitive 22) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopKeyNav.ts:24— ClassicyDesktopKeyNav.nearestIconInDirection has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (7 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyFileDialog.ClassicyFileDialog (cognitive 22) src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:155— ClassicyFileDialog.ClassicyFileDialog has cognitive complexity 22 (threshold 15). Drivers by points: if/else 35 (42 pts), boolean chains 24, ternaries 13 (14 pts), error handling 3 (nesting depth added 8). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This shape REPEATS in the file: one other method here (ClassicyFileDialog.ClassicyFileDialog::commitSave) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassicyKeyboardEquivalentDialog.ClassicyKeyboardEquivalentDialog (cognitive 22) src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:78— ClassicyKeyboardEquivalentDialog.ClassicyKeyboardEquivalentDialog has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 12, if/else 9, ternaries 1. Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 120, 102, 118). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HyperCardExpression.tokenize (cognitive 21) src/SystemFolder/HyperCard/HyperCardExpression.ts:38— HyperCardExpression.tokenize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAlert.ClassicyAlert (cognitive 21) src/SystemFolder/SystemResources/Alert/ClassicyAlert.tsx:179— ClassicyAlert.ClassicyAlert has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 7 (8 pts), boolean chains 4 (nesting depth added 3). Most of this is not in the body itself: 4 of the 21 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 327, 216, 207, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ClassicyBootManager.classicyBootEventHandler (cognitive 21) src/SystemFolder/SystemResources/Boot/ClassicyBootManager.ts:24— ClassicyBootManager.classicyBootEventHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (5 pts), boolean chains 2, match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassicyColorWheel.ClassicyColorWheel (cognitive 21) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorWheel.tsx:26— ClassicyColorWheel.ClassicyColorWheel has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (14 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). None of this is in the body itself: all 21 points belong to 4 function items inside it that branch (a function literal at line 45, hitTest, onPointerMove, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyPopUpMenu.ClassicyPopUpMenu::onButtonKeyDown (cognitive 21) src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:434— ClassicyPopUpMenu.ClassicyPopUpMenu::onButtonKeyDown has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 2, match/switch 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyPackageCss.matchingBrace (cognitive 20) bin/classicyPackageCss.ts:51— classicyPackageCss.matchingBrace has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAssetRegistry.registerClassicySystemArt (cognitive 20) src/Appearance/ClassicyAssetRegistry.ts:487— ClassicyAssetRegistry.registerClassicySystemArt has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 4, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAppManager.classicyShortcutEventHandler (cognitive 20) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:438— ClassicyAppManager.classicyShortcutEventHandler has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassicyButton.ClassicyButton (cognitive 20) src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:109— ClassicyButton.ClassicyButton has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 6, boolean chains 5 (nesting depth added 2). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 8 function items inside it that branch (handleKeyDown, handleKeyUp, a function literal at line 142, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyRadioInput.ClassicyRadioInput (cognitive 20) src/SystemFolder/SystemResources/RadioInput/ClassicyRadioInput.tsx:108— ClassicyRadioInput.ClassicyRadioInput has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8, ternaries 8, boolean chains 4. Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to 11 function items inside it that branch (pressItem, handleOnChange, a function literal at line 144, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyAssetRegistry.mergeInto (cognitive 19) src/Appearance/ClassicyAssetRegistry.ts:173— ClassicyAssetRegistry.mergeInto has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (7 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.closing (cognitive 18) bin/classicyCssCascade.ts:50— classicyCssCascade.closing has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.scanTo (cognitive 18) bin/classicyCssCascade.ts:211— classicyCssCascade.scanTo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.blockEnd (cognitive 18) bin/classicyCssCascade.ts:225— classicyCssCascade.blockEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, loops 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parityShoot.shootStories (cognitive 18) bin/parity/parityShoot.ts:109— parityShoot.shootStories has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 2 (3 pts), ternaries 2 (3 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 154, 159, 181). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
parity.run (cognitive 18) bin/parity/parity.ts:56— parity.run has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 2 (3 pts), boolean chains 2, loops 1 (2 pts), match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ClassicyAppearanceManager.Options.useOptionsTab (cognitive 18) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Options.tsx:131— ClassicyAppearanceManager.Options.useOptionsTab has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts), loops 1 (nesting depth added 7). None of this is in the body itself: all 18 points belong to 4 function literals inside it that branch (lines 140, 169, 182, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MoviePlayerContext.classicyQuickTimeMoviePlayerEventHandler (cognitive 18) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:28— MoviePlayerContext.classicyQuickTimeMoviePlayerEventHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, match/switch 1, ternaries 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyBevelButtonPopup.ClassicyBevelButtonPopup (cognitive 18) src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButtonPopup.tsx:75— ClassicyBevelButtonPopup.ClassicyBevelButtonPopup has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7, ternaries 6 (7 pts), boolean chains 4 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 6 function items inside it that branch (onMenuKeyDown, a function literal at line 112, a function literal at line 121, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileBrowser.ClassicyFileBrowser (cognitive 18) src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx:165— ClassicyFileBrowser.ClassicyFileBrowser has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 2 (3 pts) (nesting depth added 1). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (onKeyDown, onContextMenu, a function literal at line 202). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileDialog.ClassicyFileDialog::commitSave (cognitive 18) src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:397— ClassicyFileDialog.ClassicyFileDialog::commitSave has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2, error handling 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ClassicyFileDialog.ClassicyFileDialog) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ClassicyLink.ClassicyLink (cognitive 18) src/SystemFolder/SystemResources/Link/ClassicyLink.tsx:74— ClassicyLink.ClassicyLink has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (6 pts), boolean chains 3 (nesting depth added 2). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (activate, handleKeyDown). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
classicyPackageCss.bundleProblems (cognitive 17) bin/classicyPackageCss.ts:132— classicyPackageCss.bundleProblems has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 5, loops 3 (5 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.classicyCssRules::walk (cognitive 17) bin/classicyCssCascade.ts:267— classicyCssCascade.classicyCssRules::walk has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyWallpaperIndex.portableClassicyWallpaper (cognitive 17) src/Appearance/ClassicyWallpaperIndex.ts:365— ClassicyWallpaperIndex.portableClassicyWallpaper has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (4 pts), boolean chains 3, loops 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAppearance.mergeDeep (cognitive 17) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearance.ts:380— ClassicyAppearance.mergeDeep has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DriveSetupController.DriveSetupController (cognitive 17) src/SystemFolder/ControlPanels/DriveSetup/DriveSetupController.tsx:21— DriveSetupController.DriveSetupController has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (6 pts) (nesting depth added 3). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 39, confirmInitialize, a function literal at line 66, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyFileSystem.size (cognitive 17) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:671— ClassicyFileSystem.size has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 2 (4 pts), boolean chains 1, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyWindow.ClassicyWindow::computeStandardRect (cognitive 17) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1546— ClassicyWindow.ClassicyWindow::computeStandardRect has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ClassicyWindow.ClassicyWindow) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
check-pixel-literals.scanPixelLiteralsInSource (cognitive 16) bin/check-pixel-literals.ts:161— check-pixel-literals.scanPixelLiteralsInSource has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (5 pts), ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classicyCssCascade.splitClassicySelectorList (cognitive 16) bin/classicyCssCascade.ts:68— classicyCssCascade.splitClassicySelectorList has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyWallpaperIndex.exactIdentity (cognitive 16) src/Appearance/ClassicyWallpaperIndex.ts:199— ClassicyWallpaperIndex.exactIdentity has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ClassicyAppManager.classicyDesktopStateEventReducer (cognitive 16) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:517— ClassicyAppManager.classicyDesktopStateEventReducer has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppleGuideContext.classicyAppleGuideEventHandler (cognitive 16) src/SystemFolder/Extensions/AppleGuide/AppleGuideContext.tsx:91— AppleGuideContext.classicyAppleGuideEventHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HyperCardScriptBuilder.ActionField (cognitive 16) src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx:411— HyperCardScriptBuilder.ActionField has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), ternaries 5 (8 pts) (nesting depth added 4). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 3 function items inside it that branch (commitLatest, a function literal at line 424, a function literal at line 455). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ClassicyShortcutDispatcher.useClassicyShortcutDispatcher (cognitive 16) src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyShortcutDispatcher.ts:22— ClassicyShortcutDispatcher.useClassicyShortcutDispatcher has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 5, ternaries 1 (nesting depth added 2). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 32). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ClassicyFileBrowserViewIcons.ClassicyFileBrowserViewIcons (cognitive 16) src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewIcons.tsx:91— ClassicyFileBrowserViewIcons.ClassicyFileBrowserViewIcons has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 4, ternaries 4 (nesting depth added 1). None of this is in the body itself: all 16 points belong to 4 function literals inside it that branch (lines 137, 142, 230, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TooManyMethods: ClassicyFileSystem src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:155— TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Off the main sequence: @classicy/appearance-platinum — @classicy/appearance-platinum: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
Duplication concentrated across 32 sibling directories (29 clone groups) src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130— 29 duplicated blocks under src/SystemFolder/SystemResources/ have copies in at least two of the sibling directories Alert, Assistant, BalloonHelp, Button, ButtonToolbar, ComboBox (+26 more sibling(s) not listed) — 20 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 29 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 29 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 29 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (13 clone groups) src/SystemFolder/PDFViewer/PDFViewerContext.tsx:47— 13 duplicated blocks under src/SystemFolder/ have copies in at least two of the sibling directories ControlPanels, Extensions, Finder, HyperCard, PDFViewer, QuickTime (+3 more sibling(s) not listed) — 9 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 7 sibling directories (9 clone groups) src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40— 9 duplicated blocks under src/SystemFolder/ControlPanels/ have copies in at least two of the sibling directories AppManager, AppearanceManager, ControlStripManager, DateAndTimeManager, DriveSetup, ScreenSaverManager (+1 more sibling(s) not listed) — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (6 clone groups) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172— 6 of the duplicated blocks reported below have copies in at least two of the sibling directories MoviePlayer, PictureViewer under src/SystemFolder/QuickTime/. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 9 sibling directories (5 clone groups) packages/appearance/platinum/src/screenSavers/FlyingToasters/ClassicyScreenSaverFlyingToasters.tsx:115— 5 duplicated blocks under packages/appearance/platinum/src/screenSavers/ have copies in at least two of the sibling directories BouncingBall, Fish, FlyingToasters, Globe, HardRain, Messages (+3 more sibling(s) not listed) — 0 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (234 matched lines × 2 locations) · ×1
Duplicated block with local edits (234 matched lines × 2 locations) src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130— src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:130 · src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:193 — the two spans are one implementation copied and then locally edited — 1278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (208 matched lines × 2 locations) · ×1
Duplicated block with local edits (208 matched lines × 2 locations) src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:39— src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:39 · src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx:50 — the two spans are one implementation copied and then locally edited — 1204 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (79 lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:172 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:134 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (76 matched lines × 2 locations) · ×1
Duplicated block with local edits (76 matched lines × 2 locations) src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40— src/SystemFolder/ControlPanels/ControlStripManager/ClassicyControlStripManager.tsx:40 · src/SystemFolder/ControlPanels/ScreenSaverManager/ClassicyScreenSaverManager.tsx:51 — the two spans are one implementation copied and then locally edited — 339 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (69 matched lines × 2 locations) · ×1
Duplicated block with local edits (69 matched lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:36— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:36 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx:38 — the two spans are one implementation copied and then locally edited — 386 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) src/SystemFolder/SystemResources/Input/ClassicyInput.tsx:49— src/SystemFolder/SystemResources/Input/ClassicyInput.tsx:49 · src/SystemFolder/SystemResources/Spinner/ClassicySpinner.tsx:59 — the two spans are one implementation copied and then locally edited — 262 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (56 lines × 2 locations) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:62— src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:62 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHSV.tsx:62 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (52 lines × 2 locations) src/SystemFolder/SystemResources/File/ClassicyFileSystemApplications.ts:98— src/SystemFolder/SystemResources/File/ClassicyFileSystemApplications.ts:98 · src/SystemFolder/SystemResources/File/ClassicyFileSystemExtensions.ts:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (44 matched lines × 2 locations) · ×1
Duplicated block with local edits (44 matched lines × 2 locations) src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.tsx:161— src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.tsx:161 · src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:170 — the two spans are one implementation copied and then locally edited — 199 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (41 lines × 2 locations) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:12— src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHLS.tsx:12 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerHSV.tsx:12 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (38 lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:259— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:259 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:218 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (34 lines × 2 locations) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:42— src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:42 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:106 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 2 locations) src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:500— src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:500 · src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:612 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (32 lines × 2 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Colors.tsx:38— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Colors.tsx:38 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Metrics.tsx:54 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (32 matched lines × 2 locations) · ×1
Duplicated block with local edits (32 matched lines × 2 locations) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1133— src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1133 · src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1322 — the two spans are one implementation copied and then locally edited — 193 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (29 lines × 2 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:585— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:585 · src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx:129 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (28 lines × 3 locations) src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:236— src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:236 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:326 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:381 — 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 (26 lines × 2 locations) src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:127— src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:127 · src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx:89 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 4 locations) src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:176— src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:176 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:250 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:340 · src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts:395 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:448— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:448 · src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManager.tsx:84 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (25 matched lines × 2 locations) · ×1
Duplicated block with local edits (25 matched lines × 2 locations) src/SystemFolder/HyperCard/HyperCard.tsx:241— src/SystemFolder/HyperCard/HyperCard.tsx:241 · src/SystemFolder/HyperCard/HyperCard.tsx:683 — the two spans are one implementation copied and then locally edited — 128 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (22 lines × 2 locations) src/SystemFolder/PDFViewer/PDFViewer.tsx:46— src/SystemFolder/PDFViewer/PDFViewer.tsx:46 · src/SystemFolder/WebViewer/WebViewer.tsx:68 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) src/SystemFolder/PDFViewer/PDFViewerContext.tsx:17— src/SystemFolder/PDFViewer/PDFViewerContext.tsx:17 · src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx:21 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (21 matched lines × 2 locations) · ×1
Duplicated block with local edits (21 matched lines × 2 locations) src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:10— src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:10 · src/SystemFolder/SystemResources/ColorPicker/ClassicyColorPickerUtils.ts:75 — the two spans are one implementation copied and then locally edited — 179 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:161— src/SystemFolder/SystemResources/Button/ClassicyButton.tsx:161 · src/SystemFolder/SystemResources/Placard/ClassicyPlacard.tsx:129 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (19 lines × 5 locations) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:60— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:60 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:79 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:101 · src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Fonts.tsx:120 · +1 more site(s) not listed — all 5 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (18 lines × 2 locations) src/SystemFolder/PDFViewer/PDFViewer.tsx:82— src/SystemFolder/PDFViewer/PDFViewer.tsx:82 · src/SystemFolder/WebViewer/WebViewer.tsx:104 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function classicyDesktopEventHandler (cyclomatic 119, cognitive 149) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:223— classicyDesktopEventHandler has cyclomatic complexity 119 and cognitive complexity 149; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 116, cognitive 133) src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:90— (anonymous) has cyclomatic complexity 116 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classicyFinderEventHandler (cyclomatic 74, cognitive 121) src/SystemFolder/Finder/FinderContext.tsx:182— classicyFinderEventHandler has cyclomatic complexity 74 and cognitive complexity 121; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyWindow (cyclomatic 71, cognitive 64) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:539— ClassicyWindow has cyclomatic complexity 71 and cognitive complexity 64; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 61, cognitive 81) src/SystemFolder/HyperCard/HyperCardContext.tsx:89— (anonymous) has cyclomatic complexity 61 and cognitive complexity 81; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classicyDesktopIconEventHandler (cyclomatic 52, cognitive 112) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:264— classicyDesktopIconEventHandler has cyclomatic complexity 52 and cognitive complexity 112; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 50, cognitive 62) src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:255— (anonymous) has cyclomatic complexity 50 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classicyWindowEventHandler (cyclomatic 48, cognitive 65) src/SystemFolder/SystemResources/Desktop/ClassicyDesktopWindowManagerContext.tsx:140— classicyWindowEventHandler has cyclomatic complexity 48 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function execAction (cyclomatic 48, cognitive 51) src/SystemFolder/HyperCard/HyperCardEngine.ts:159— execAction has cyclomatic complexity 48 and cognitive complexity 51; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classicyAppEventHandler (cyclomatic 41, cognitive 76) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:288— classicyAppEventHandler has cyclomatic complexity 41 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleKeyDown (cyclomatic 38, cognitive 36) src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:407— handleKeyDown has cyclomatic complexity 38 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyFileDialog (cyclomatic 36, cognitive 27) src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:155— ClassicyFileDialog has cyclomatic complexity 36 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 35, cognitive 45) src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaverContext.tsx:96— (anonymous) has cyclomatic complexity 35 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyBevelButton (cyclomatic 35, cognitive 32) src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:252— ClassicyBevelButton has cyclomatic complexity 35 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function HyperCard (cyclomatic 34, cognitive 32) src/SystemFolder/HyperCard/HyperCard.tsx:119— HyperCard has cyclomatic complexity 34 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function move (cyclomatic 31, cognitive 30) src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:820— move has cyclomatic complexity 31 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function renderPart (cyclomatic 28, cognitive 15) src/SystemFolder/HyperCard/HyperCardCard.tsx:159— renderPart has cyclomatic complexity 28 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 27, cognitive 29) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:478— (anonymous) has cyclomatic complexity 27 and cognitive complexity 29; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyTreeNodeItem (cyclomatic 25, cognitive 21) src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:190— ClassicyTreeNodeItem has cyclomatic complexity 25 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 32) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:737— (anonymous) has cyclomatic complexity 24 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 10) src/Appearance/ClassicyAppearancePackageSchema.ts:109— (anonymous) has cyclomatic complexity 24 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onButtonKeyDown (cyclomatic 23, cognitive 21) src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:434— onButtonKeyDown has cyclomatic complexity 23 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function visit (cyclomatic 22, cognitive 27) src/__tests__/platinumCoreImports.test.ts:44— visit has cyclomatic complexity 22 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicySlider (cyclomatic 22, cognitive 21) src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:195— ClassicySlider has cyclomatic complexity 22 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 40) src/Appearance/ClassicyStructureWithoutPackage.test.tsx:207— (anonymous) has cyclomatic complexity 21 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyPopUpMenu (cyclomatic 21, cognitive 19) src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:166— ClassicyPopUpMenu has cyclomatic complexity 21 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function traceClassicyDragOutline (cyclomatic 20, cognitive 32) src/SystemFolder/SystemResources/File/ClassicyFileDragOutline.ts:37— traceClassicyDragOutline has cyclomatic complexity 20 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 28) src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:441— (anonymous) has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 37) src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts:101— (anonymous) has cyclomatic complexity 19 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parsePrimary (cyclomatic 19, cognitive 25) src/SystemFolder/HyperCard/HyperCardExpression.ts:215— parsePrimary has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 24) src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1549— (anonymous) has cyclomatic complexity 19 and cognitive complexity 24; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 23) src/SystemFolder/Extensions/AppleGuide/AppleGuideContext.tsx:94— (anonymous) has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 19, cognitive 18) src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyShortcutDispatcher.ts:32— handler has cyclomatic complexity 19 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ClassicyControlStrip (cyclomatic 19, cognitive 16) src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:251— ClassicyControlStrip has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 17) src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:258— (anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function classicyDateTimeManagerEventHandler (cyclomatic 18, cognitive 15) src/SystemFolder/ControlPanels/DateAndTimeManager/ClassicyDateAndTimeEventHandler.ts:35— classicyDateTimeManagerEventHandler has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onKeyDown (cyclomatic 18, cognitive 15) src/SystemFolder/SystemResources/KeyboardEquivalent/ClassicyKeyboardEquivalentDialog.tsx:120— onKeyDown has cyclomatic complexity 18 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 27) src/SystemFolder/HyperCard/HyperCard.tsx:327— (anonymous) has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function moveClassicyFileSystemItems (cyclomatic 17, cognitive 21) src/SystemFolder/SystemResources/File/ClassicyFileMove.ts:149— moveClassicyFileSystemItems has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 18) src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:364— (anonymous) has cyclomatic complexity 17 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx · ×1
src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx: 1976 lines of code src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx:1— src/SystemFolder/SystemResources/Window/ClassicyWindow.tsx has 1976 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/HyperCard/HyperCard.tsx · ×1
src/SystemFolder/HyperCard/HyperCard.tsx: 1163 lines of code src/SystemFolder/HyperCard/HyperCard.tsx:1— src/SystemFolder/HyperCard/HyperCard.tsx has 1163 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts · ×1
src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts: 1012 lines of code src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts:1— src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts has 1012 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx · ×1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx: 895 lines of code src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx:1— src/SystemFolder/SystemResources/Desktop/ClassicyDesktop.tsx has 895 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts: 830 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeDerivations.ts has 830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx · ×1
src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx: 829 lines of code src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:1— src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx has 829 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx · ×1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx: 790 lines of code src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx:1— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopManager.tsx has 790 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/Finder/Finder.tsx · ×1
src/SystemFolder/Finder/Finder.tsx: 719 lines of code src/SystemFolder/Finder/Finder.tsx:1— src/SystemFolder/Finder/Finder.tsx has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx · ×1
src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx: 687 lines of code src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx:1— src/SystemFolder/SystemResources/ControlStrip/ClassicyControlStrip.tsx has 687 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/Appearance/ClassicyAssetRegistry.ts · ×1
src/Appearance/ClassicyAssetRegistry.ts: 659 lines of code src/Appearance/ClassicyAssetRegistry.ts:1— src/Appearance/ClassicyAssetRegistry.ts has 659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts · ×1
src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts: 656 lines of code src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts:1— src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.ts has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx · ×1
src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx: 656 lines of code src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx:1— src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialog.tsx has 656 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Table/ClassicyTable.tsx · ×1
src/SystemFolder/SystemResources/Table/ClassicyTable.tsx: 648 lines of code src/SystemFolder/SystemResources/Table/ClassicyTable.tsx:1— src/SystemFolder/SystemResources/Table/ClassicyTable.tsx has 648 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx · ×1
src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx: 645 lines of code src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx:1— src/SystemFolder/SystemResources/BevelButton/ClassicyBevelButton.tsx has 645 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx · ×1
src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx: 612 lines of code src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx:1— src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx has 612 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx · ×1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx: 601 lines of code src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx:1— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIcon.tsx has 601 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx: 596 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.tsx has 596 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/Finder/FinderContext.tsx · ×1
src/SystemFolder/Finder/FinderContext.tsx: 575 lines of code src/SystemFolder/Finder/FinderContext.tsx:1— src/SystemFolder/Finder/FinderContext.tsx has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts · ×1
src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts: 561 lines of code src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts:1— src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/HyperCard/HyperCardEngine.ts · ×1
src/SystemFolder/HyperCard/HyperCardEngine.ts: 561 lines of code src/SystemFolder/HyperCard/HyperCardEngine.ts:1— src/SystemFolder/HyperCard/HyperCardEngine.ts has 561 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx · ×1
src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx: 551 lines of code src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx:1— src/SystemFolder/SystemResources/Menu/ClassicyMenu.tsx has 551 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx · ×1
src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx: 543 lines of code src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx:1— src/SystemFolder/SystemResources/Tree/ClassicyTree.tsx has 543 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx · ×1
src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx: 529 lines of code src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx:1— src/SystemFolder/SystemResources/Window/ClassicyWindow.stories.tsx has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SimpleText/SimpleText.tsx · ×1
src/SystemFolder/SimpleText/SimpleText.tsx: 522 lines of code src/SystemFolder/SimpleText/SimpleText.tsx:1— src/SystemFolder/SimpleText/SimpleText.tsx has 522 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts: 514 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyIcons.ts has 514 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx · ×1
src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx: 511 lines of code src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:1— src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx has 511 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx · ×1
src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx: 489 lines of code src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx:1— src/SystemFolder/HyperCard/Editor/HyperCardInspector.tsx has 489 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx: 483 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx · ×1
src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx: 483 lines of code src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx:1— src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.tsx has 483 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts: 479 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts has 479 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts · ×1
src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts: 474 lines of code src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts:1— src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetricTargets.ts has 474 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx · ×1
src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx: 462 lines of code src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx:1— src/SystemFolder/SystemResources/Slider/ClassicySlider.tsx has 462 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx · ×1
src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx: 461 lines of code src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx:1— src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx has 461 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx · ×1
src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx: 451 lines of code src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx:1— src/SystemFolder/HyperCard/Editor/HyperCardScriptBuilder.tsx has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx · ×1
src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx: 426 lines of code src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx:1— src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/Appearance/ClassicyWallpaperIndex.ts · ×1
src/Appearance/ClassicyWallpaperIndex.ts: 424 lines of code src/Appearance/ClassicyWallpaperIndex.ts:1— src/Appearance/ClassicyWallpaperIndex.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx · ×1
src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx: 411 lines of code src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx:1— src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx has 411 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts · ×1
src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts: 410 lines of code src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts:1— src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
X2 · Cancellation propagation· Async function without AbortSignal · ×1
Async function without AbortSignal: readHyperCardStackFileText src/SystemFolder/HyperCard/HyperCardStackFile.ts:14— `readHyperCardStackFileText` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Mock-dominated test: clicks and keys each control box to its handler src/SystemFolder/SystemResources/Window/ClassicyWindowTitleBar.test.tsx:117— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: does not toggle the branch when its leaf button is clicked src/SystemFolder/SystemResources/Tree/ClassicyTree.test.tsx:134— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: commits the final sizes once when a drag gesture ends src/SystemFolder/SystemResources/SplitView/ClassicySplitView.test.tsx:288— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: routes error-level entries to onError in addition to onLog src/SystemFolder/SystemResources/Log/ClassicyLog.test.ts:48— This test sets up 4 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: cancels via the Cancel button src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.test.tsx:54— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: Return confirms and Escape cancels src/SystemFolder/SystemResources/InputDialog/ClassicyInputDialog.test.tsx:62— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: double-clicking a top-level row opens its full path src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.test.tsx:401— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: double-clicking a disclosed child opens its real path, not one rebuilt from the table root src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.test.tsx:412— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: opens a disclosed child's real path on Enter too src/SystemFolder/SystemResources/File/ClassicyFileBrowserViewTable.test.tsx:423— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: treats a press that barely moves as a click src/SystemFolder/SystemResources/File/ClassicyFileDrag.test.ts:160— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: reports nothing for a press that never crosses the threshold src/SystemFolder/SystemResources/File/ClassicyFileDrag.test.ts:249— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ends once, not dropped, on a release over nothing src/SystemFolder/SystemResources/File/ClassicyFileDrag.test.ts:293— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ignores Escape before the drag starts src/SystemFolder/SystemResources/File/ClassicyFileDrag.test.ts:325— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: reports nothing when a press is abandoned before it drags src/SystemFolder/SystemResources/File/ClassicyFileDrag.test.ts:352— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: leaves a mouseup with no press behind it to the control src/SystemFolder/SystemResources/File/ClassicyPointerStreamLost.test.tsx:211— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: keeps a press through a pointercancel src/SystemFolder/SystemResources/File/ClassicyPointerStreamLost.test.tsx:377— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: ends every key held, each once src/SystemFolder/SystemResources/File/ClassicyPointerStreamLost.test.tsx:415— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: forwards path and title to the instance without prefixing the path src/SystemFolder/SystemResources/Analytics/useClassicyAnalytics.test.tsx:71— This test sets up 14 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: resumes only what it paused when reduced motion is turned off src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaver.test.tsx:227— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: forgets a paused animation once its element leaves the document src/SystemFolder/Extensions/ScreenSaver/ClassicyScreenSaver.test.tsx:258— This test sets up 5 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Duplicated predicate src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx:159— `!appOpen || hasCheckedInitialLoadRef.current` appears character-identically in 2 files — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayer.tsx, src/SystemFolder/QuickTime/PictureViewer/PictureViewer.tsx. 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/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyAppSwitcherUtils.ts:118— `!item.menuChildren || item.menuChildren.length === 0` appears character-identically in 2 files — src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyAppSwitcherUtils.ts, src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx. 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/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx:593— `activeTheme === appearance.activeTheme && availableThemes === appearance.availableThemes && customThemes === appearance.customThemes` appears character-identically in 2 files — src/SystemFolder/ControlPanels/AppManager/ClassicyAppManagerUtils.tsx, src/SystemFolder/ControlPanels/AppManager/ClassicyStateMigrations.ts. 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/SystemFolder/PDFViewer/PDFViewerUtils.tsx:20— `d !== null && typeof d === "object" && "openFiles" in d && Array.isArray(d.openFiles)` appears character-identically in 3 files — src/SystemFolder/PDFViewer/PDFViewerUtils.tsx, src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerUtils.tsx, src/SystemFolder/QuickTime/PictureViewer/PictureViewerUtils.tsx. 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/SystemFolder/SystemResources/Keyboard/useListNavigation.ts:109— `e.key.length === 1 && e.key !== " " && !e.metaKey && !e.ctrlKey && !e.altKey` appears character-identically in 2 files — src/SystemFolder/SystemResources/Keyboard/useListNavigation.ts, src/SystemFolder/SystemResources/Table/ClassicyTable.tsx. 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/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:493— `grouped && "classicyPopUpMenuListItemGrouped"` appears character-identically in 2 files — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx, src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx. 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/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx:77— `item.menuChildren && item.menuChildren.length > 0` appears character-identically in 2 files — src/SystemFolder/SystemResources/Desktop/MenuBar/ClassicyDesktopMenuBar.tsx, src/SystemFolder/SystemResources/Menu/ClassicyKeyboardShortcut.ts. 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/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:170— `maxValue !== undefined && date.getTime() >= maxValue.getTime()` appears character-identically in 2 files — src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx, src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx. 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/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx:168— `minValue !== undefined && date.getTime() < minValue.getTime()` appears character-identically in 2 files — src/SystemFolder/SystemResources/DatePicker/ClassicyDatePicker.tsx, src/SystemFolder/SystemResources/TimePicker/ClassicyTimePicker.tsx. 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/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:445— `placement?.above && "classicyPopUpMenuListAbove"` appears character-identically in 2 files — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx, src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx. 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/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceKeyGuards.internal.ts:29— `proto === Object.prototype || proto === null` appears character-identically in 2 files — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceKeyGuards.internal.ts, src/SystemFolder/SystemResources/Utils/deepMerge.ts. 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/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx:283— `target instanceof Node && listRef.current?.contains(target)` appears character-identically in 2 files — src/SystemFolder/SystemResources/ComboBox/ClassicyComboBox.tsx, src/SystemFolder/SystemResources/PopUpMenu/ClassicyPopUpMenu.tsx. 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/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx:87— `typeof p === "string" || p.url !== action.document?.url` appears character-identically in 2 files — src/SystemFolder/QuickTime/MoviePlayer/MoviePlayerContext.tsx, src/SystemFolder/QuickTime/PictureViewer/PictureViewerContext.tsx. 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/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts:41— `typeof v === "object" && v !== null && !Array.isArray(v)` appears character-identically in 2 files — src/SystemFolder/ControlPanels/AppManager/ClassicyActionPredicates.ts, src/SystemFolder/HyperCard/HyperCardModel.ts. 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/SystemFolder/ControlPanels/AppManager/ClassicyAppWindows.ts:177— `typeof value !== "object" || value === null` appears character-identically in 3 files — src/SystemFolder/ControlPanels/AppManager/ClassicyAppWindows.ts, src/SystemFolder/SystemResources/Desktop/ClassicyDesktopIconContext.tsx, src/SystemFolder/SystemResources/Utils/deepMerge.ts. 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/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceKeyGuards.internal.ts:26— `typeof value !== "object" || value === null || Array.isArray(value)` appears character-identically in 2 files — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceKeyGuards.internal.ts, src/SystemFolder/SystemResources/File/ClassicyFileSystemValidation.ts. 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/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts:81— `typeof value === "number" && Number.isFinite(value)` appears character-identically in 3 files — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts, src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeMetrics.ts, src/SystemFolder/ControlPanels/SoundManager/ClassicySoundManagerUtils.tsx. 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/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFile.ts:178— `typeof value === "object" && value !== null && !Array.isArray(value)` appears character-identically in 3 files — src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFile.ts, src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts, src/SystemFolder/SystemResources/Utils/deepMerge.ts. 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/SystemFolder/SystemResources/SchemaForm/ClassicySchemaForm.tsx:81— `value !== null && typeof value === "object"` appears character-identically in 2 files — src/SystemFolder/SystemResources/SchemaForm/ClassicySchemaForm.tsx, src/SystemFolder/SystemResources/Utils/deepMerge.ts. 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.
Deprecated: @types/dompurify pnpm-lock.yaml:3065— @types/dompurify 3.2.0 is resolved in pnpm-lock.yaml and is marked deprecated by its publisher: "This is a stub types definition. dompurify provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob pnpm-lock.yaml:4059— glob 6.0.4 is resolved in pnpm-lock.yaml and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight pnpm-lock.yaml:4160— inflight 1.0.6 is resolved in pnpm-lock.yaml and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: intersection-observer pnpm-lock.yaml:4167— intersection-observer 0.10.0 is resolved in pnpm-lock.yaml and is marked deprecated by its publisher: "The Intersection Observer polyfill is no longer needed and can safely be removed. Intersection Observer has been Baseline since 2019.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
redundant comment src/Appearance/ClassicyPackageExports.test.ts:270— "Platinum's are @classicy/appearance-platinum/scss/* (its own test)." repeats the code it sits on: 4 of its 5 words (platinum, classicy, appearance, scss) are already in `it("no longer serves Platinum's SCSS", () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.test.ts:676— "Finder.app is the previously focused app (focusedAppId = "Finder.app")" repeats the code it sits on: 4 of its 5 words (finder, app, focused, id) are already in `ds.System.Manager.Applications.apps["Finder.app"].windows = windowsRecord({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment src/SystemFolder/ControlPanels/AppManager/ClassicyAppManager.test.ts:743— "Finder.app is the focused app" repeats the code it sits on: 3 of its 3 words (finder, app, focused) are already in `ds.System.Manager.Applications.apps["Finder.app"].focused = true;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
IC1 · Incompleteness & stubs· Empty method body · ×2
Empty method body src/SystemFolder/SystemResources/Analytics/useClassicyAnalytics.ts:17— `dispatch` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body src/SystemFolder/SystemResources/File/ClassicyFileBrowser.tsx:128— `defaultFileOnClick` has an empty body — confirm it's an intentional no-op and not an unfinished method.
ADR Consequences section is empty docs/stories/0148-wf3-bugs-host-defaultstate-theme-tweaks-do-not-persist.md:62— docs/stories/0148-wf3-bugs-host-defaultstate-theme-tweaks-do-not-persist.md:62 heads a Consequences section with nothing under it but a placeholder. A decision record states the context that forced it, the decision and its consequences; write what this one's consequences are.
D21 · Naming Consistency· `setBackgroundURL` spells `URL` where 22 names in the project spell it `Url` · ×1
`setBackgroundURL` spells `URL` where 22 names in the project spell it `Url` src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.Desktop.tsx:53— 22 of 23 names in project @classicy/classicy spell the token `Url` (22 of 23; unit: names in project @classicy/classicy containing `Url`). Peers: classicyScssSource.isUrlAt (bin/classicyScssSource.ts:58); classicyScssSource.blankClassicyScssUrlPayloads (bin/classicyScssSource.ts:101); parityApp.fresh(baseUrl) (bin/parity/parityApp.ts:30); parityStories.storyUrl (bin/parity/parityStories.ts:27); parityStories.storyUrl(baseUrl) (bin/parity/parityStories.ts:27). Rename to `setBackgroundUrl`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion package.json:1— `(repository root)` (59805 LoC, 477 module-visible types across 89 directories) overshoots its size bounds. 1 of 3 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 3.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No SAST .github/workflows/ci.yml:19— No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 4 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.
R7 · Dead Code· Unused module-local declaration '_EveryAssetKindListed' · ×1
Unused module-local declaration '_EveryAssetKindListed' src/Appearance/ClassicyAppearancePackageSchema.ts:44— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '_ClassicyAppearancePackageSchemaMatchesType' · ×1
Unused module-local declaration '_ClassicyAppearancePackageSchemaMatchesType' src/Appearance/ClassicyAppearancePackageSchema.ts:261— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 1/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) override strict null checking — ~0.1 `!` null assertions per 1k TypeScript source lines — 4 assertion(s) across the 66395 source line(s) of the 343 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: src/SystemFolder/HyperCard/Editor/HyperCardEditorContext.ts (3), src/SystemFolder/SystemResources/File/ClassicyFileSystem.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Silent fallback default in catch bin/check-dist-imports.mjs:350— `injectedText` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated (npm): @noble/hashes — @noble/hashes is pinned at 2.2.0; registry.npmjs.org publishes 2.4.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tanstack/react-table — @tanstack/react-table is pinned at 8.21.3; registry.npmjs.org publishes 9.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dompurify — dompurify is pinned at 3.4.17; registry.npmjs.org publishes 3.4.18 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): he — he is pinned at 1.2.0; registry.npmjs.org publishes 2.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): immer — immer is pinned at 11.1.8; registry.npmjs.org publishes 11.2.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react — react is pinned at 19.2.7; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-dom — react-dom is pinned at 19.2.7; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-json-tree — react-json-tree is pinned at 0.20.0; registry.npmjs.org publishes 0.20.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zod — zod is pinned at 4.6.6; registry.npmjs.org publishes 4.6.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): zustand — zustand is pinned at 5.0.14; registry.npmjs.org publishes 5.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
doc comments repeat the names packages/appearance/platinum/src/index.ts:88— 0 of 0 documented parameters and 1 of 93 summaries in `@classicy/appearance-platinum` only repeat the member or parameter name (e.g. "The Platinum package's id." for `PLATINUM_APPEARANCE_PACKAGE_ID`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names src/SystemFolder/SystemResources/FileDialog/ClassicyFileDialogVolume.ts:25— 0 of 0 documented parameters and 5 of 2422 summaries in `@classicy/classicy` only repeat the member or parameter name (e.g. "Options for ." for `ClassicyFileWriteOptions`). Delete the restating tags, or add what the name does not say.
doc comments repeat the names storybook/.storybook/MirroredPackage.ts:18— 0 of 0 documented parameters and 3 of 24 summaries in `classicy-storybook` only repeat the member or parameter name (e.g. "The mirrored package's id." for `MIRRORED_APPEARANCE_PACKAGE_ID`). Delete the restating tags, or add what the name does not say.
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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 74 file(s) — `packages/appearance/platinum/src/screenSavers/platinumScreenSavers.stories.tsx`, `src/Appearance/ClassicyAppearancePackageSchema.ts`, `src/Appearance/ClassicyAssetRegistry.ts`, `src/SystemFolder/ControlPanels/AppearanceManager/ClassicyAppearanceManager.stories.tsx`, `src/SystemFolder/ControlPanels/AppearanceManager/ClassicyThemeFontSizes.ts`, … (+69 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1e612-f473-7c6a-b920-9041888bf98e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 23 · Warnings: 458 · Recommendations: 63 · Info: 13 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 20:36 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.