Public report of NickvisionApps/Parabolic, published 12 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.3). 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, 12 November 2026, 01:56 UTC · Survey ID cd_04dfb4aa111743309b9779edfc01035d
NickvisionApps/Parabolic
Measured 12 November 2026, 01:55 UTC, at code version 1118e6a
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 10,885 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 22
Findings by how serious they are
30 critical191 serious73 minor
3 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
12 November 2026, 01:55 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 ▸
66of 66 dimensions measured by tools.
271of 294 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
66dimensions across 6 lenses, read from 10,885 lines of product code in 3 projects.
NickvisionApps/Parabolic falls short of our standard for production because the project has no automated tests and we found no automated security scanning of the code, its secrets or its dependencies. It scores 37 out of 100 and is rated Weak, and 19 of its 30 critical findings are security problems in the build pipeline.
Production Readiness, at 22, is the weakest lens and counts most in the score. The best first step for the work it takes is removing the unread values, worth about 5 points. Adding automated tests would lift Production Readiness itself, worth about 14 points. Raising Production Readiness to 70 would lift the score to about 50.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four secrets can leak from the build pipeline, and eight errors are caught and ignored, so failures can go unnoticed. Pinning each tool to an exact version, limiting each secret to its own step and handling or logging the ignored errors would close these risks. The two pipeline steps that run downloads without checking them need each download checked against a known checksum first. The data field that is written but never read needs removing.
The product code is 10,885 lines, about €64,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.
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 92 findings
These 92 critical or serious findings were in the previous survey, on 23 October 2026, and are gone from this one.
Cancellation propagation · Async method without CancellationToken: Present Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs
Cancellation propagation · Async method without CancellationToken: Present Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs
Cancellation propagation · Async method without CancellationToken: AuthenticationCredentialRow_OnNotify Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs
Cancellation propagation · Async method without CancellationToken: Present Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs
Cancellation propagation · Async method without CancellationToken: Credentials_CollectionChanged Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs
Cancellation propagation · Async method without CancellationToken: EditConfirmCredentialButton_OnClicked Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs
Cancellation propagation · Async method without CancellationToken: Window_OnShow Nickvision.Parabolic.GNOME/Views/MainWindow.cs
Cancellation propagation · Async method without CancellationToken: DownloadRow_StopRequested Nickvision.Parabolic.GNOME/Views/MainWindow.cs
Cancellation propagation · Async method without CancellationToken: AddDownload Nickvision.Parabolic.GNOME/Views/MainWindow.cs
Cancellation propagation · Async method without CancellationToken: Keyring Nickvision.Parabolic.GNOME/Views/MainWindow.cs
Cancellation propagation · Async method without CancellationToken: EditConfirmPostprocessingArgumentButton_OnClicked Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs
Cancellation propagation · Async method without CancellationToken: AddAsync Nickvision.Parabolic.Shared/Controllers/KeyringViewController.cs
Cancellation propagation · Async method without CancellationToken: ClearRecoverableDownloadsAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs
Cancellation propagation · Async method without CancellationToken: RetryDownloadAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs
Cancellation propagation · Async method without CancellationToken: StopDownloadAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs
Cancellation propagation · Async method without CancellationToken: AddAsync Nickvision.Parabolic.Shared/Services/DownloadService.cs
Cancellation propagation · Async method without CancellationToken: RetryAsync Nickvision.Parabolic.Shared/Services/DownloadService.cs
Cancellation propagation · Async method without CancellationToken: StopAsync Nickvision.Parabolic.Shared/Services/DownloadService.cs
Cancellation propagation · Async method without CancellationToken: Download_Completed Nickvision.Parabolic.Shared/Services/DownloadService.cs
Cancellation propagation · Async method without CancellationToken: AddAsync Nickvision.Parabolic.Shared/Services/HistoryService.cs
Cancellation propagation · Async method without CancellationToken: ClearAsync Nickvision.Parabolic.Shared/Services/HistoryService.cs
Cancellation propagation · Async method without CancellationToken: RemoveAsync Nickvision.Parabolic.Shared/Services/HistoryService.cs
Cancellation propagation · Async method without CancellationToken: RemoveAsync Nickvision.Parabolic.Shared/Services/HistoryService.cs
Cancellation propagation · Async method without CancellationToken: UpdateAsync Nickvision.Parabolic.Shared/Services/HistoryService.cs
Cancellation propagation · Async method without CancellationToken: AddAsync Nickvision.Parabolic.Shared/Services/RecoveryService.cs
Cancellation propagation · Async method without CancellationToken: ClearAsync Nickvision.Parabolic.Shared/Services/RecoveryService.cs
Cancellation propagation · Async method without CancellationToken: RemoveAsync Nickvision.Parabolic.Shared/Services/RecoveryService.cs
Cancellation propagation · Async method without CancellationToken: RemoveAsync Nickvision.Parabolic.Shared/Services/RecoveryService.cs
Cancellation propagation · Async method without CancellationToken: ShowAsync Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: ShowAsync Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: Dialog_Loaded Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: TglSort_Click Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: Remove Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: LoadDownloadsAsync Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: ShowAsync Nickvision.Parabolic.WinUI/Views/KeyringDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: Dialog_Loaded Nickvision.Parabolic.WinUI/Views/KeyringDialog.xaml.cs
Cancellation propagation · Async method without CancellationToken: Window_Loaded Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: Window_Closing Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: Controller_DownloadAdded Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: DownloadRow_RetryRequested Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: DownloadRow_StopRequested Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: About Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: AddDownload Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: Keyring Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: History Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: CheckForUpdates Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: DenoUpdate Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: Discussions Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: GitHubRepo Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: ReportABug Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: RetryAllFailed Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: StopAllRemaining Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: WindowsUpdate Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: YtdlpUpdate Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: AddDownloadAsync Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs
Cancellation propagation · Async method without CancellationToken: AddPostprocessingArgument Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: ClearCookiesFile Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: DeletePostprocessingArgument Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: EditPostprocessingArgument Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: SelectCookiesFile Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: Cmb_SelectionChanged Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: Num_ValueChanged Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: Tgl_Toggled Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Cancellation propagation · Async method without CancellationToken: Txt_TextChanged Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs
Rebuild cost: about €64,000 · Estimate
Cost to rebuild
€21,000 to €110,000, for 344 to 1,130 hours of work, about 0.4 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 37. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Small: 10,885 lines of product code
Comment lines
The estimate prices 10,837 lines. Comment lines count towards the size of 10,885 lines but aren't priced as work.
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
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.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RecoveryService.cs.
Raises the score by about 5 points · Low effort · Explicit Debt
2
Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with AddDownloadDialog.cs (6), PreferencesDialog.cs, Download.cs.
Raises the score by about 5 points · Low effort · Explicit Debt
3
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 14 points · High effort · Code Coverage
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 €64,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 22 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 1 Explicit Debt findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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.
17 modules, with 27 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.
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.
Nickvision.Parabolic.Shared.Services uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.Shared.Services, while a change to Nickvision.Parabolic.Shared.Services can't break Nickvision.Parabolic.Shared.Models.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→11 Nickvision.Parabolic.Shared.Services uses Nickvision.Parabolic.Shared.Eventspart of a loop✕
Connections
18 pairs of types, where a type in Nickvision.Parabolic.Shared.Services uses a type in Nickvision.Parabolic.Shared.Events.
Nickvision.Parabolic.Shared.Services uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.Shared.Services, while a change to Nickvision.Parabolic.Shared.Services can't break Nickvision.Parabolic.Shared.Events.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Nickvision.Parabolic.Shared.Models uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.Shared.Models, while a change to Nickvision.Parabolic.Shared.Models can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.Shared.Models uses a module listed above it, which is the healthy direction.
9→11 Nickvision.Parabolic.Shared.Models uses Nickvision.Parabolic.Shared.Eventspart of a loop✕
Connections
2 pairs of types, where a type in Nickvision.Parabolic.Shared.Models uses a type in Nickvision.Parabolic.Shared.Events.
Nickvision.Parabolic.Shared.Models uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.Shared.Models, while a change to Nickvision.Parabolic.Shared.Models can't break Nickvision.Parabolic.Shared.Events.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
Nickvision.Parabolic.Shared.Controllers uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.Shared.Controllers, while a change to Nickvision.Parabolic.Shared.Controllers can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.Shared.Controllers uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.Shared.Controllers uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.Shared.Controllers, while a change to Nickvision.Parabolic.Shared.Controllers can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.Shared.Controllers uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.Shared.Events uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.Shared.Events, while a change to Nickvision.Parabolic.Shared.Events can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.Shared.Events uses a module listed above it, which is the healthy direction.
28 pairs of types, where a type in Nickvision.Parabolic.Shared.Helpers uses a type in Nickvision.Parabolic.Shared.Models. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Nickvision.Parabolic.Shared.Helpers uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.Shared.Helpers, while a change to Nickvision.Parabolic.Shared.Helpers can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.Shared.Helpers uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Helpers uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.WinUI.Helpers, while a change to Nickvision.Parabolic.WinUI.Helpers can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Helpers uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Controls uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.GNOME.Controls, while a change to Nickvision.Parabolic.GNOME.Controls can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Controls uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.GNOME.Controls, while a change to Nickvision.Parabolic.GNOME.Controls can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Controls uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.GNOME.Controls, while a change to Nickvision.Parabolic.GNOME.Controls can't break Nickvision.Parabolic.Shared.Events.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Controls uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.WinUI.Controls, while a change to Nickvision.Parabolic.WinUI.Controls can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Controls uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.WinUI.Controls, while a change to Nickvision.Parabolic.WinUI.Controls can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Controls uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.WinUI.Controls, while a change to Nickvision.Parabolic.WinUI.Controls can't break Nickvision.Parabolic.Shared.Events.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Controls uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.GNOME.Helpers, so a change to Nickvision.Parabolic.GNOME.Helpers can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.GNOME.Helpers.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.Shared.Controllers, so a change to Nickvision.Parabolic.Shared.Controllers can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.Shared.Controllers.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.Shared.Events.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.GNOME.Views uses Nickvision.Parabolic.GNOME.Controls, so a change to Nickvision.Parabolic.GNOME.Controls can break Nickvision.Parabolic.GNOME.Views, while a change to Nickvision.Parabolic.GNOME.Views can't break Nickvision.Parabolic.GNOME.Controls.
Position
Below the diagonal: Nickvision.Parabolic.GNOME.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.Shared.Services, so a change to Nickvision.Parabolic.Shared.Services can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.Shared.Services.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.Shared.Models, so a change to Nickvision.Parabolic.Shared.Models can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.Shared.Models.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.Shared.Controllers, so a change to Nickvision.Parabolic.Shared.Controllers can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.Shared.Controllers.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.Shared.Events, so a change to Nickvision.Parabolic.Shared.Events can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.Shared.Events.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.WinUI.Helpers, so a change to Nickvision.Parabolic.WinUI.Helpers can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.WinUI.Helpers.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
Nickvision.Parabolic.WinUI.Views uses Nickvision.Parabolic.WinUI.Controls, so a change to Nickvision.Parabolic.WinUI.Controls can break Nickvision.Parabolic.WinUI.Views, while a change to Nickvision.Parabolic.WinUI.Views can't break Nickvision.Parabolic.WinUI.Controls.
Position
Below the diagonal: Nickvision.Parabolic.WinUI.Views uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 34% · Weak · gated by R1, X1, X4 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
19
High / Critical
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RecoveryService.cs; Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with AddDownloadDialog.cs (6), PreferencesDialog.cs, Download.cs.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RecoveryService.cs.
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
God Classes: MethodTooLong: SettingsPage.SettingsPage(…)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 30
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 — 191
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 — 73
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 3
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 66 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 — 66 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, 271 of 294 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.
D17 Explicit Debt — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The C# workspace loaded this repository's projects but reported a load failure, and the dead-code reference search is unreliable over a graph that did not load cleanly, so it was skipped. The other debt markers on this row were read; dead symbols were not, and their absence from the score is not a finding that the code has none. First load diagnostic: Failure: Msbuild failed when processing the file 'Nickvision.Parabolic.WinUI/Nickvision.Parabolic.WinUI.csproj' with message: The command ""/tmp/nuget-packages/microsoft.windows.cswinrt/2.2.0/cswinrt.exe" @"Nickvision.Parabolic.WinUI/obj/Debug/net10.0-windows10.0.19041.0/Generated Files/CsWinR….
D18 Solution Shape — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `dotnet build` reported 2 error(s), and the diagnostics it printed were: MSB3073: The command "xgettext --from-code=utf-8 --language=C# --force-po --output="resources/po/parabolic.pot" --keyword=_ --keyword=_n:1,2 --keyword=_p:1c,2 --keyword=_pn:1c,2,3 --keyword=C_:1c,2 --width=80 "Nickvision.Parabolic.GNOME/Blueprints/AddDownloadDialog.blp" "Nickvision.Parabolic.GNOME/Blueprints/DownloadRow.blp" "Nickvision.Parabolic.GNOME/Blueprints/HistoryDialog.blp" "Nickvision.Parabolic.GNOME/Blueprints/KeyringDialog.blp" "Nickvision.Parabolic.GNOME/Blueprints/LoadingDialog.blp" "Nickvision.Parabolic.GNOME/Blueprints/MainWindow.blp" "Nickvision.Parabolic.GNOME/Blueprints/PreferencesDialog.blp" "Nickvision.Parabolic.GNOME/Blueprints/ShortcutsDialog.blp" "Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs" "Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs" "Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs" "Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs" "Nickvision.Parabolic.GNOME/Views/MainWindow.cs" "Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs" "Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs" "Nickvision.Parabolic.Shared/Controllers/KeyringViewController.cs" "Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs" "Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs" "Nickvision.Parabolic.Shared/Models/Download.cs" "Nickvision.Parabolic.Shared/Models/Format.cs" "Nickvision.Parabolic.Shared/Models/MediaSelectionItem.cs" "Nickvision.Parabolic.Shared/Models/SubtitleLanguage.cs" "Nickvision.Parabolic.Shared/Models/VideoResolution.cs" "Nickvision.Parabolic.WinUI/Controls/AboutDialog.xaml.cs" "Nickvision.Parabolic.WinUI/Controls/DownloadRow.xaml.cs" "Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs" "Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs" "Nickvision.Parabolic.WinUI/Views/KeyringDialog.xaml.cs" "Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs" "Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs"" exited with code 127.; MSB3073: The command ""/tmp/nuget-packages/microsoft.windowsappsdk.winui/2.0.12/buildTransitive/../tools/net6.0/../net472/XamlCompiler.exe" "obj/ARM64/Debug/net10.0-windows10.0.19041.0/input.json" "obj/ARM64/Debug/net10.0-windows10.0.19041.0/output.json"" exited with code 126.. None of them is a .NET compiler diagnostic, which is the only signal this check reads as "the code does not compile", so the failure is recorded as a build-environment gap rather than a code defect. The usual causes are a project that targets a platform this run cannot build (a Windows-only target framework on a Linux worker) or a build step that shells out to a tool the image does not carry. Solution Shape is scored on structure and is NOT capped. Semantic analysis is independent of this build and covers every project that loaded — but a project whose restore did not complete has no resolved references, so treat its results as absent rather than clean. ★ The reach of that test, stated so this classification can be checked rather than taken on trust: it reads the C# (CS), Visual Basic (BC) and F# (FS) compiler series, and treats SDK, NuGet-restore and MSBuild codes (NETSDK, NU, MSB) as evidence that the build did not run rather than that the code is broken — read the diagnostics named above and judge for yourself. You can widen what we reach: if this build is meant to run off its own platform, without host tooling we do not carry, the diagnostics named above are what stopped it. If it is deliberately platform-bound — a Windows-only desktop product, say — there is nothing to do here: the note records our reach, not a defect in your build.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
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. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
D22 Internal API Consistency — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. The loaded project set declares no packable project and no `.Contracts` project, so there is no intentionally-exposed surface for API consistency to be judged over.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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. `Nickvision.Parabolic.Shared/Helpers/IConfigurationServiceExtensions.cs`, `Nickvision.Parabolic.Shared/Helpers/MediaFileTypeExtensions.cs`, `Nickvision.Parabolic.Shared/Helpers/StringExtensions.cs`, `Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs` 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.
AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
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.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
X1 Async correctness — 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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
X2 Cancellation propagation — 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. 14 further occurrence(s) are not listed individually; the score already reflects all 54.
X4 Structured logging — 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. 71 further occurrence(s) are not listed individually; the score already reflects all 111.
Repo exclusion declarations: 1 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D18 Solution Shape: Build integrity reflects whether the solution compiled in this environment — a build that needs a private feed, a specific SDK, or a generated file absent from the repo can read as broken when it is merely unreproducible here.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
12 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was YtdlpExecutableService.GetDownloadProcess at 128. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being PostProcessorArgument.ToString at 28 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Nickvision.Parabolic.Shared/Models/PostProcessorArgument.cs (PostProcessorArgument.ToString at 28). 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.
+ 7 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with YtdlpExecutableService.GetDownloadProcess (cyclomatic 128), Media.Media.ctor (cyclomatic 102). — 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 6.8 to about 7.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; 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.
+ 12 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with Media.Media.ctor (cognitive 177), YtdlpExecutableService.GetDownloadProcess (cognitive 132), Download.Process_Exited (cognitive 65). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.1 to about 7.2/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 Classes8.4 / 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 3 MethodTooLong finding(s) in God Classes — start with REDACTED, SettingsPage.xaml.cs, AddDownloadDialog.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 TooManyMethods finding(s) in God Classes — start with MainWindow.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with AddDownloadDialog.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
14 duplicated block group(s) detected. A further 23 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
Edited copy of a member (20 corresponding lines) · ×4Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:282
Edited copy of a member (11 corresponding lines) · ×2Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:493
Edited copy of a member (13 corresponding lines) · ×2Nickvision.Parabolic.Shared/Services/DownloadService.cs:145
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Edited copy of a member (20 corresponding lines) finding(s) in Code Duplication — start with AddDownloadDialog.cs, HistoryDialog.xaml.cs, HistoryService.cs. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with MainWindow.cs, PreferencesViewController.cs, KeyringDialog.cs. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with MainWindow.cs (2), DownloadService.cs. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
What it measures: Whether 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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with AddDownloadDialog.xaml.cs. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D8 · Code Coverage0.0 / 10Critical✓ Tool-verified
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
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.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 224 packages use a banned license. ★ DEPTH: this repository's MSBuild projects declare 13 direct `PackageReference`(s), and 211 further package(s) were reached beyond them by closing the graph over nuget.org's own nuspec dependency graph — so a banned licence pulled in only by a dependency's OWN dependencies is inside this verdict. A package whose licence nuget.org could not be asked for is not graded, and version ranges are taken at their lower bound, so this is the closure as that graph states it rather than a restored consumer's exact resolution.
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.
Top hotspots: REDACTED (5×128=640); Nickvision.Parabolic.Shared/Models/Media.cs (3×102=306); Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs (3×28=84)
Hotspot: REDACTED · ×4REDACTED:125
What to do
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED, Media.cs, AddDownloadDialogController.cs. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor2.0 / 10Critical✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
31 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs. Counted over 38 of the 92 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
What to do
Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
9 deducted debt markers + unmeasured dead symbols across 10404 LoC in the .NET projects (0.7/KLoC) → score 8.5. Dead code not measured: the solution did not load cleanly, so the reference search was skipped.
Resolve the 8 EmptyCatchBlock finding(s) in Explicit Debt — start with AddDownloadDialog.cs (6), PreferencesDialog.cs, Download.cs. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 1 WriteOnlyPrivateField finding(s) in Explicit Debt — start with RecoveryService.cs. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the solution is laid out in a sensible, conventional structure.
Method: Solution structure: project count, decomposition, shell-project detection, build success (confirmed failures cap the score); traced to actual .sln files and binaries. Deterministic.
3 projects, 94 source files, 10404 hand-written lines of code (10404 production / 0 test — the split is derived per file: test is what its project, its own path, or a compile-guarded region marks as test, and a file carrying no test signal counts as production), 2 inter-project edges (build NOT measured — `dotnet build` did not complete in the analyzer, so the build half of this dimension is unmeasured rather than failed: the score above rests on structure alone and is not capped. The diagnostics that stopped it are named under Limitations.)
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.
2 of 2 documentation facets pass in full. 4 document(s) read across 4 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: 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.
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.
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.
Resolve the 3 redundant comment finding(s) in Comment Value — start with utils.js (2), MainWindow.cs. — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
0 of 3 projects flagged as possibly oversized/incoherent.
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md.
Do you agree with this assessment?
D27 · Navigability8.5 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
92 % of calls cross a namespace and 15 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: medium — clean/modular boundaries expected.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
19 finding(s): 0 critical, 19 high, 0 medium, 0 low. 12 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 5 file(s) — `Nickvision.Parabolic.Shared/Helpers/IConfigurationServiceExtensions.cs` (line 245, line 369), `Nickvision.Parabolic.Shared/Helpers/MediaFileTypeExtensions.cs` (lines 8–9, line 72), `Nickvision.Parabolic.Shared/Helpers/StringExtensions.cs` (lines 26–27, line 161), `Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs` (lines 201–202), `resources/macos/publish-and-package.sh` (line 323, lines 338–371) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 2 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 12 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (12 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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 38 of the 92 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.
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
`DownloadService` is a singleton (one shared instance) but mutates instance state outside any lock (_downloading, _queued, _completed; e.g. `_downloading` at line 90). — Nickvision.Parabolic.Shared/Services/DownloadService.cs:15
`HistoryService` is a singleton (one shared instance) but mutates instance state outside any lock (_tableEnsured; e.g. `_tableEnsured` at line 237). — Nickvision.Parabolic.Shared/Services/HistoryService.cs:11
`RecoveryService` is a singleton (one shared instance) but mutates instance state outside any lock (_tableEnsured; e.g. `_tableEnsured` at line 186). — Nickvision.Parabolic.Shared/Services/RecoveryService.cs:11
`ThumbnailService` is a singleton (one shared instance) but mutates instance state outside any lock (_cache, _mediaMap; e.g. `_cache` at line 71). — Nickvision.Parabolic.Shared/Services/ThumbnailService.cs:12
`MainWindowController` is a singleton (one shared instance) but mutates instance state outside any lock (_latestAppVersion, _latestYtdlpVersion, _latestDenoVersion; e.g. `_latestAppVersion` at line 131). — Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:19
`MainWindow` is a singleton (one shared instance) but mutates instance state outside any lock (_notificationClickHandler, _downloadRows; e.g. `_notificationClickHandler` at line 230). This type is a UI view, so it is thread-CONFINED rather than locked: if every one of those mutations is reached only from the UI thread — directly, or marshalled back through the dispatcher — the confinement IS the synchronisation and there is nothing to add (do not take a lock on a view; that is how the UI thread deadlocks). Check the ones that are not: a handler for a background event that mutates before it marshals is a real race. — Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:23
`Download` is not registered, but the singleton `DownloadService` creates it and keeps it in `_downloading`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Status, _removeSourceData, _process, FilePath, _progressSkipCounter; e.g. `Status` at line 75). — Nickvision.Parabolic.Shared/Models/Download.cs:17
`AddDownloadDialogController` is registered per request (scoped/transient), so each caller expects its own instance — but it keeps mutable `static` state that every instance in the process shares, and mutates it outside any lock (_shownTeachTypeFlag; e.g. `_shownTeachTypeFlag` at line 422). The per-request lifetime buys nothing here: the field outlives every request and concurrent requests race on it. — Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:18
What to do
Keep singletons stateless or back their state with thread-safe types (Concurrent*/Immutable*); otherwise concurrent callers race.
Mutable `static` state in a per-request component is shared by the whole process: inject it as a registered singleton (so its sharing is visible and testable) or make it thread-safe.
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.
The namespaces Nickvision.Parabolic.Shared.Events ↔ Nickvision.Parabolic.Shared.Models ↔ Nickvision.Parabolic.Shared.Services depend on each other. The lightest dependency in the cycle is Nickvision.Parabolic.Shared.Models → Nickvision.Parabolic.Shared.Services (Nickvision.Parabolic.Shared.Models.Download → Nickvision.Parabolic.Shared.Services.IYtdlpExecutableService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface. — Nickvision.Parabolic.Shared/Models/Download.cs:7
What to do
Break namespace cycles inside a project by moving the shared type to a namespace both sides can use, or by inverting the back edge behind an interface.
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 the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
`IDownloadService` declares 22 members: `DownloadAdded`, `DownloadCompleted`, `DownloadProgressChanged`, `DownloadRetired`, `DownloadStartedFromQueue`, `DownloadStopped`, `DownloadingCount`, `QueuedCount`, `CompletedCount`, `FailedCount`, `RemainingCount`, `AddAsync`, `AddAsync`, `ClearCompleted`, `ClearQueued`, `Pause`, `RecoverAllAsync`, `Resume`, `RetryAsync`, `RetryFailedAsync`, `StopAsync`, `StopAllAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Nickvision.Parabolic.Shared/Services/IDownloadService.cs:9
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Other · Code Health — Unreviewed-generation residue: shipped members still throwing NotImplementedException, and placeholder string literals left in non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords: members that only throw a "not implemented" exception, methods that take inputs and return a constant, async methods that never await, dead `if (false)` / `#if false` branches, and skeleton types most of whose members are holes. A real, objective slice of technical debt.
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.
`SingleRevertToTitleButton_OnClicked` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:506
`Dialog_OnClosed` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:177
`AddPostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:362
`DeletePostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:382
`UpdatePostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:393
`ClearAll` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs:119
`ApplyChangesAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:331
What to do
Remove the dead code that looks live: delete dead if(false) / #if false branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async methods, which promise work they never wait for.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Describe the projects a newcomer cannot place from the root README: 3 of 3 have no README of their own, in their folder or in their family's project (`Nickvision.Parabolic.GNOME`, `Nickvision.Parabolic.Shared`, `Nickvision.Parabolic.WinUI`).
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
What to do
Start a test surface where your build system looks for one (tests/, test/, spec/, or your ecosystem's test source set) — the separation follows from putting the first tests in the right place.
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.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`dotnet test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P2 · Observability6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
What to do
Extend structured logging across the projects you operate, and give the library ones a diagnostics seam instead — an `EventSource`/`ActivitySource` the host can subscribe to, or an optional logger on your options object — rather than taking a logging dependency on your consumers' behalf.
Consider OpenTelemetry tracing/metrics and a health-check endpoint for operability.
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 csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) 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. — REDACTED:4
`Nickvision.Parabolic.GNOME/Nickvision.Parabolic.GNOME.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — Nickvision.Parabolic.GNOME/Nickvision.Parabolic.GNOME.csproj:17
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's csharp pack, or a .NET security analyzer package — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
What to do
Add `AddStandardResilienceHandler()` (or Polly policies) to your HttpClient registrations so a flaky dependency can't take the app down.
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.
1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
`.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one). — Nickvision.Parabolic.GNOME/Views/MainWindow.cs:122
What to do
Make the call chain async end-to-end and await it — never block on a Task with .Wait()/.GetAwaiter().GetResult().
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ 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.
0 typed · 6 plain JS — the untyped files are extension/chrome/background.js, extension/chrome/options.js, extension/chrome/utils.js, extension/firefox/background.js, extension/firefox/options.js, extension/firefox/utils.js.
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.
extension/chrome/background.js:5 · extension/firefox/background.js:2 — 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. — extension/chrome/background.js:5
extension/chrome/options.js:3 · extension/firefox/options.js:3 — 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. — extension/chrome/options.js:3
extension/chrome/utils.js:17 · extension/firefox/utils.js:17 — 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. — extension/chrome/utils.js:17
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 · 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.
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files10.0 / 10Exemplary✓ 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.
Do you agree with this assessment?
R4 · Test Coverage0.0 / 10Critical✓ 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.
0% of 6 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R7 · Dead Code10.0 / 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.
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.
Do you agree with this assessment?
X1 · Async correctness3.7 / 10Weak✓ Tool-verified
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.
`async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained. (×39) — Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:224, Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:242, Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:281, …
Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process. — Nickvision.Parabolic.GNOME/Views/MainWindow.cs:122
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. 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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`Download` declares a finalizer (line 58), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Nickvision.Parabolic.Shared/Models/Download.cs:58
`DownloadService` declares a finalizer (line 51), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization. — Nickvision.Parabolic.Shared/Services/DownloadService.cs:51
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether async methods accept a CancellationToken so work can be cancelled (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 6/59 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
No CancellationToken parameter — this work can't be stopped early once started. (×38) — Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:86, Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:228, Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:246, …
No CancellationToken parameter — the body observes an ambient token instead (a field or a context object), so the work does stop on cancellation, but a caller cannot cancel this call independently of the owner that created that token. — Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:329
What to do
Thread a CancellationToken through async methods so work stops promptly on cancellation.
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 the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
`LogDebug` at line 75 is called with an argument built by `JsonSerializer.Serialize(options, ApplicationJsonContext.Default.DownloadOptions)` (line 75), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — Nickvision.Parabolic.Shared/Services/DownloadService.cs:75
`LogDebug` at line 110 is called with an argument built by `JsonSerializer.Serialize(option, ApplicationJsonContext.Default.DownloadOptions)` (line 110), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region. — Nickvision.Parabolic.Shared/Services/DownloadService.cs:110
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is C#'s evaluation order, not a guess — then put the construction behind the same level check the sink applies: `if (logger.IsEnabled(LogLevel.Trace))` for Microsoft.Extensions.Logging, the repository's own debug flag where it has one, or a message template whose ARGUMENTS the logging framework only formats when the level is on. Moving the call is not the fix: it is the join/projection in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `foreach` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is enumerating invalidates the enumerator it is holding, so the next `MoveNext` throws `InvalidOperationException` and the remaining items are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
`catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch. — Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:97
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. (×8) — Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:224, Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:300, Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:363, …
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it. (×40) — Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:168, Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:243, Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:260, …
Other · Code Health — Whether nullable reference types are enabled and not undermined by heavy `!` suppression.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~7.8 `!` suppressions per 1k syntax nodes — 384 suppression(s) across the 49019 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. 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
Enable <Nullable>enable</Nullable> across all projects and resolve warnings rather than suppressing with `!`.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — 7 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 evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 55 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC2 Forms & labels — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC3 Page structure — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC4 Keyboard semantics — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC5 ARIA correctness — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AC6 Visual & motion safety — No user-facing web UI (the repo is a library/CLI/worker/headless service) — accessibility is not applicable.
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
C1 Data Protection — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C2 Access Controls — No access-control surface detected in the analyzed source — no web/app surface to authorize (no HTTP API or web-UI project) and no authorization code at all (no [Authorize]/policies, no imperative guard methods). Access control is therefore N/A here — this is a library/CLI, which is authorized by its CALLER, not by itself. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
C3 Audit Trail — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C4 Data Retention — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
C5 Data-Subject Rights — No personal data detected in the analyzed source — no PII-typed entity/column names (Email, FirstName, DateOfBirth, …), no ASP.NET Identity / user-account model, and no stored user credentials. GDPR data-protection controls are therefore N/A here. If this is intentional, record the no-PII posture in an ADR; if the app does process personal data, name those fields conventionally so this dimension activates.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D22 Internal API Consistency — No intentionally-exposed public API to evaluate for consistency.
D23 Boundary Type-Coupling — small single-context codebase (10,404 production LoC in the .NET projects) — bounded contexts are not needed at this size No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 4 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs and no dependency cycles — architectural integrity not assessed
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit))
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
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no EF Core usage detected
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Cobertura — `dotnet test --collect:"XPlat Code Coverage"` with a `coverlet.collector` PackageReference) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found by the two searches this check runs — a BenchmarkDotNet package reference in any project file (loaded, or on disk), and a script whose name contains `benchmark` that this repository's CI runs. Neither can see a suite in another ecosystem's idiom, so this is not a verdict that the repository has none. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted, and nothing is asked of a repository that has none.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
S1 Web-Security Posture — No web surface detected in the analyzed source — no HTTP API or web-UI project (no controllers/minimal-API endpoints, no Razor/Blazor views) and no web middleware (HTTPS redirection, HSTS, security headers, cookies). Transport security, security headers, secure cookies, CSRF/input-validation and middleware-order controls are therefore N/A here — this is a library/CLI/worker, not a web app. Crypto hygiene was still checked and found nothing to flag. If this codebase becomes web-facing, the dimension reactivates automatically.
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
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:224— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:300— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:363— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:402— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:520— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:572— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:284— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
EmptyCatchBlock Nickvision.Parabolic.Shared/Models/Download.cs:219— empty catch block — the error is discarded with nothing recorded, so a failure here leaves no trace anywhere. Record it through whatever this codebase already uses to report problems, or let it propagate. Where swallowing one specific failure really is correct — as it often is on a teardown/dispose path where throwing would mask the original failure — catch exactly that exception type and write down WHY in a comment on the catch. Both are needed: a comment on a catch-all still swallows every failure nobody anticipated, and a note that only restates the swallow ("ignored", "do nothing") is read as no explanation at all.
Namespace dependency cycle Nickvision.Parabolic.Shared/Models/Download.cs:7— The namespaces Nickvision.Parabolic.Shared.Events ↔ Nickvision.Parabolic.Shared.Models ↔ Nickvision.Parabolic.Shared.Services depend on each other. The lightest dependency in the cycle is Nickvision.Parabolic.Shared.Models → Nickvision.Parabolic.Shared.Services (Nickvision.Parabolic.Shared.Models.Download → Nickvision.Parabolic.Shared.Services.IYtdlpExecutableService, 1 type pair(s)); cut that one first, e.g. by moving the shared type to a namespace both can use or inverting it behind an interface.
WriteOnlyPrivateField Nickvision.Parabolic.Shared/Services/RecoveryService.cs:16— private IConfigurationService _configurationService — assigned 1 time(s), read never — this field is written and never read anywhere its type can be reached from, so the state it keeps answers no question: every assignment to it computes a value that nothing observes, on every instance, for the lifetime of each one. It reads as a flag the code branches on, and nothing branches on it. Delete the field and its assignments — or, if the value was MEANT to be consulted, the missing read is the defect this row is pointing at, and the branch that should have depended on it is not there.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (xUnit, NUnit or MSTest), and run it in CI so the gap cannot reopen.
async void method: OpenFolderButton_OnClicked Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:224— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PlayButton_OnClicked Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:242— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SelectBathFileRow_OnActivated Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:281— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AuthenticationCredentialRow_OnNotify Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:303— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: DiscoverUrlButton_OnClicked Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:329— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SingleRevertToTitleButton_OnClicked Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:506— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SingleSelectSaveFolderButton_OnClicked Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:508— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: PlaylistSelectSaveFolderButton_OnClicked Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:560— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SortGroup_OnNotify Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:61— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SaveLengthRow_OnNotify Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:70— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Credentials_CollectionChanged Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:65— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: EditConfirmCredentialButton_OnClicked Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:115— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Window_OnShow Nickvision.Parabolic.GNOME/Views/MainWindow.cs:187— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Controller_DownloadAdded Nickvision.Parabolic.GNOME/Views/MainWindow.cs:326— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: DownloadRow_RetryRequested Nickvision.Parabolic.GNOME/Views/MainWindow.cs:399— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: DownloadRow_StopRequested Nickvision.Parabolic.GNOME/Views/MainWindow.cs:401— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: About Nickvision.Parabolic.GNOME/Views/MainWindow.cs:433— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: AddDownload Nickvision.Parabolic.GNOME/Views/MainWindow.cs:469— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Keyring Nickvision.Parabolic.GNOME/Views/MainWindow.cs:471— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: History Nickvision.Parabolic.GNOME/Views/MainWindow.cs:473— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: StopAllRemaining Nickvision.Parabolic.GNOME/Views/MainWindow.cs:475— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: RetryAllFailed Nickvision.Parabolic.GNOME/Views/MainWindow.cs:477— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: Dialog_OnClosed Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:177— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: SelectCookiesFileButton_OnClicked Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:265— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
async void method: EditConfirmPostprocessingArgumentButton_OnClicked Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:301— `async void` can't be awaited and its exceptions crash the process instead of propagating. Return `Task` — or, where the delegate contract requires void (timer/event/callback registrations), make this a thin void shim that awaits a Task-returning inner method inside try/catch so exceptions are contained.
+ 14 more in this group — see findings.md.
X2 · Cancellation propagation· Async method without CancellationToken · ×38
Async method without CancellationToken: TriggerAddedStateAsync Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:86— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DownloadSingleAsync Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:228— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DownloadPlaylistAsync Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:246— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Present Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:55— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SortGroup_OnNotify Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:61— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: SaveLengthRow_OnNotify Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:70— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: LoadDownloadsAsync Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:98— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RemoveAsync Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:153— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Controller_DownloadAdded Nickvision.Parabolic.GNOME/Views/MainWindow.cs:326— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: DownloadRow_RetryRequested Nickvision.Parabolic.GNOME/Views/MainWindow.cs:399— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: About Nickvision.Parabolic.GNOME/Views/MainWindow.cs:433— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: History Nickvision.Parabolic.GNOME/Views/MainWindow.cs:473— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StopAllRemaining Nickvision.Parabolic.GNOME/Views/MainWindow.cs:475— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RetryAllFailed Nickvision.Parabolic.GNOME/Views/MainWindow.cs:477— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddPlaylistDownloadsAsync Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:69— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddSingleDownloadAsync Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:178— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetAllAsync Nickvision.Parabolic.Shared/Controllers/HistoryViewController.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: GetDebugInformationAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:257— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RecoverAllDownloadsAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:291— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: RetryFailedDownloadsAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:326— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: StopAllDownloadsAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:361— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: ExecuteAsync Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:422— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: Process_OutputDataReceived Nickvision.Parabolic.Shared/Models/Download.cs:233— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: WriteAsync Nickvision.Parabolic.Shared/Models/M3UFile.cs:52— No CancellationToken parameter — this work can't be stopped early once started.
Async method without CancellationToken: AddAsync Nickvision.Parabolic.Shared/Services/DownloadService.cs:102— No CancellationToken parameter — this work can't be stopped early once started.
Swallowed exception (empty catch) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:224— 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) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:300— 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) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:363— 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) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:402— 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) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:520— 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) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:572— 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) Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:284— 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) Nickvision.Parabolic.Shared/Models/Download.cs:219— 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.
Fake-async — async method never awaits Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:506— `SingleRevertToTitleButton_OnClicked` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:177— `Dialog_OnClosed` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:362— `AddPostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:382— `DeletePostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:393— `UpdatePostprocessingArgumentAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs:119— `ClearAll` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:331— `ApplyChangesAsync` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Stateful singleton: DownloadService Nickvision.Parabolic.Shared/Services/DownloadService.cs:15— `DownloadService` is a singleton (one shared instance) but mutates instance state outside any lock (_downloading, _queued, _completed; e.g. `_downloading` at line 90).
Stateful singleton: HistoryService Nickvision.Parabolic.Shared/Services/HistoryService.cs:11— `HistoryService` is a singleton (one shared instance) but mutates instance state outside any lock (_tableEnsured; e.g. `_tableEnsured` at line 237).
Stateful singleton: RecoveryService Nickvision.Parabolic.Shared/Services/RecoveryService.cs:11— `RecoveryService` is a singleton (one shared instance) but mutates instance state outside any lock (_tableEnsured; e.g. `_tableEnsured` at line 186).
Stateful singleton: ThumbnailService Nickvision.Parabolic.Shared/Services/ThumbnailService.cs:12— `ThumbnailService` is a singleton (one shared instance) but mutates instance state outside any lock (_cache, _mediaMap; e.g. `_cache` at line 71).
Stateful singleton: MainWindowController Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:19— `MainWindowController` is a singleton (one shared instance) but mutates instance state outside any lock (_latestAppVersion, _latestYtdlpVersion, _latestDenoVersion; e.g. `_latestAppVersion` at line 131).
Stateful singleton: MainWindow Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:23— `MainWindow` is a singleton (one shared instance) but mutates instance state outside any lock (_notificationClickHandler, _downloadRows; e.g. `_notificationClickHandler` at line 230). This type is a UI view, so it is thread-CONFINED rather than locked: if every one of those mutations is reached only from the UI thread — directly, or marshalled back through the dispatcher — the confinement IS the synchronisation and there is nothing to add (do not take a lock on a view; that is how the UI thread deadlocks). Check the ones that are not: a handler for a background event that mutates before it marshals is a real race.
Hotspot: REDACTED REDACTED:125— REDACTED changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 128 in YtdlpExecutableService.GetDownloadProcess at line 125. 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-03-30..2026-06-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-30 23:59:31 -04:00' --until='2026-06-28 23:59:31 -04: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.
Hotspot: Nickvision.Parabolic.Shared/Models/Media.cs Nickvision.Parabolic.Shared/Models/Media.cs:38— Nickvision.Parabolic.Shared/Models/Media.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 102 in Media.Media.ctor at line 38. 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-03-30..2026-06-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-30 23:59:31 -04:00' --until='2026-06-28 23:59:31 -04:00' --full-history --no-merges -- Nickvision.Parabolic.Shared/Models/Media.cs`: 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: Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:69— Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in AddDownloadDialogController.AddPlaylistDownloadsAsync at line 69. 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-03-30..2026-06-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-30 23:59:31 -04:00' --until='2026-06-28 23:59:31 -04:00' --full-history --no-merges -- Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs`: 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: Nickvision.Parabolic.Shared/Models/DiscoveryResult.cs Nickvision.Parabolic.Shared/Models/DiscoveryResult.cs:36— Nickvision.Parabolic.Shared/Models/DiscoveryResult.cs changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 15 in DiscoveryResult.DiscoveryResult.ctor at line 36. 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-03-30..2026-06-28, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-03-30 23:59:31 -04:00' --until='2026-06-28 23:59:31 -04:00' --full-history --no-merges -- Nickvision.Parabolic.Shared/Models/DiscoveryResult.cs`: 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.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×4
Edited copy of a member (20 corresponding lines) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:282— Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:282-301 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:266-285 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs:92— Nickvision.Parabolic.WinUI/Views/HistoryDialog.xaml.cs:92-111 | Nickvision.Parabolic.WinUI/Views/KeyringDialog.xaml.cs:173-193 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Nickvision.Parabolic.Shared/Services/HistoryService.cs:48— Nickvision.Parabolic.Shared/Services/HistoryService.cs:48-74 | Nickvision.Parabolic.Shared/Services/HistoryService.cs:209-228 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:395— Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:395-414 | Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:440-459 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
MethodTooLong: YtdlpExecutableService.GetDownloadProcess REDACTED:125— MethodTooLong — GetDownloadProcess runs 274 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsPage.SettingsPage(…) Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:25— MethodTooLong — SettingsPage(…) runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: AddDownloadDialog.DiscoverUrlButton_OnClicked Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:329— MethodTooLong — DiscoverUrlButton_OnClicked 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.
Duplicated block (9 lines × 2) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:281— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:281-289 | Nickvision.Parabolic.GNOME/Views/MainWindow.cs:296-304 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.GNOME/Views/MainWindow.cs:281` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:368— Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:368-376 | Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:400-408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:368` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:165— Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:165-173 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:358-366 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:165` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Nickvision.Parabolic.Shared/Services/DownloadService.cs:87— Nickvision.Parabolic.Shared/Services/DownloadService.cs:87-91 | Nickvision.Parabolic.Shared/Services/DownloadService.cs:122-126 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.Shared/Services/DownloadService.cs:87` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:385— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:385-389 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:375-379 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (5 lines × 2) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:393— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:393-397 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:383-387 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:493— Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:493-503 | Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:506-516 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:327— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:327-337 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:316-327 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) Nickvision.Parabolic.Shared/Services/DownloadService.cs:145— Nickvision.Parabolic.Shared/Services/DownloadService.cs:145-157 | Nickvision.Parabolic.Shared/Services/DownloadService.cs:160-172 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:509— Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:509-521 | Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:561-573 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:375— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:375-381 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:365-371 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:340— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:340-346 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:330-336 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:384— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:384-389 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:374-379 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:392— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:392-397 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:382-387 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) Nickvision.Parabolic.Shared/Models/Format.cs:275— Nickvision.Parabolic.Shared/Models/Format.cs:275-287 | Nickvision.Parabolic.Shared/Models/Format.cs:308-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:133— Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:133-145 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:319-331 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:133` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:285— Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:285-296 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:269-280 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:285` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:49— Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:49-60 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:294-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:341— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:341-346 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:331-336 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (6 lines × 2) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:376— Nickvision.Parabolic.GNOME/Views/MainWindow.cs:376-381 | Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:366-371 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Sync-over-async blocking — 1 blocking call(s) on async work (.Wait()/.GetAwaiter().GetResult()) — these waste a thread and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Sync-over-async blocking Nickvision.Parabolic.GNOME/Views/MainWindow.cs:122— `.GetAwaiter().GetResult()` blocks this thread until the async work completes — it wastes a thread-pool thread for as long as the work runs and can deadlock wherever a synchronization context is in play (a UI thread, or a caller that has one).
Duplicated block (15 lines × 2 locations) extension/chrome/options.js:3— extension/chrome/options.js:3 · extension/firefox/options.js:3 — 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 (15 lines × 2 locations) extension/chrome/utils.js:17— extension/chrome/utils.js:17 · extension/firefox/utils.js:17 — 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.
X18 · Disposal-pattern correctness· Finalizer on a type that owns no unmanaged resource · ×2
Finalizer on a type that owns no unmanaged resource Nickvision.Parabolic.Shared/Models/Download.cs:58— `Download` declares a finalizer (line 58), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Finalizer on a type that owns no unmanaged resource Nickvision.Parabolic.Shared/Services/DownloadService.cs:51— `DownloadService` declares a finalizer (line 51), but nothing in the type is unmanaged: no `IntPtr`/`UIntPtr` or pointer field, no `SafeHandle`, no `HandleRef`, no `extern`/`DllImport` member and no `Marshal`/`GCHandle`/`NativeMemory` use. A finalizer can only release what the garbage collector cannot, so on a purely-managed type it releases nothing and costs something: every instance is put on the finalizer queue, survives at least one extra collection, and is then finalized on a thread that is NOT the disposing one — where the managed objects it touches may already have been finalized themselves. Delete the finalizer (and the `GC.SuppressFinalize` that exists to defuse it); if a handle is added later, wrap it in a `SafeHandle`, which brings its own correct finalization.
Stateful shared instance: Download Nickvision.Parabolic.Shared/Models/Download.cs:17— `Download` is not registered, but the singleton `DownloadService` creates it and keeps it in `_downloading`, so one instance outlives every request and is shared by every caller that reaches it — and it mutates instance state outside any lock (Status, _removeSourceData, _process, FilePath, _progressSkipCounter; e.g. `Status` at line 75).
AX2 · Stateful singletons· Process-global static state · ×1
Process-global static state: AddDownloadDialogController Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:18— `AddDownloadDialogController` is registered per request (scoped/transient), so each caller expects its own instance — but it keeps mutable `static` state that every instance in the process shares, and mutates it outside any lock (_shownTeachTypeFlag; e.g. `_shownTeachTypeFlag` at line 422). The per-request lifetime buys nothing here: the field outlives every request and concurrent requests race on it.
YtdlpExecutableService.GetDownloadProcess (cyclomatic 128) REDACTED:125— YtdlpExecutableService.GetDownloadProcess has cyclomatic complexity 128 (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.
Media.Media.ctor (cyclomatic 102) Nickvision.Parabolic.Shared/Models/Media.cs:38— Media.Media.ctor has cyclomatic complexity 102 (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.
Format.Format.ctor (cyclomatic 53) Nickvision.Parabolic.Shared/Models/Format.cs:59— Format.Format.ctor has cyclomatic complexity 53 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function, or replace a long branch ladder over a single value with a data-driven lookup or dispatch table.
Format.ToString (cyclomatic 53) Nickvision.Parabolic.Shared/Models/Format.cs:224— Format.ToString has cyclomatic complexity 53 (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.
Download.Process_OutputDataReceived (cyclomatic 30) Nickvision.Parabolic.Shared/Models/Download.cs:233— Download.Process_OutputDataReceived has cyclomatic complexity 30 (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.
AddDownloadDialogController.DiscoverAsync (cyclomatic 29) Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:253— AddDownloadDialogController.DiscoverAsync has cyclomatic complexity 29 (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.
AddDownloadDialogController.AddPlaylistDownloadsAsync (cyclomatic 28) Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:69— AddDownloadDialogController.AddPlaylistDownloadsAsync has cyclomatic complexity 28 (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.
Download.Process_Exited (cyclomatic 24) Nickvision.Parabolic.Shared/Models/Download.cs:141— Download.Process_Exited has cyclomatic complexity 24 (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.
DiscoveryService.GetForUrlAsync (cyclomatic 17) Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:64— DiscoveryService.GetForUrlAsync 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.
MainWindow.UpdateDownloadsList (cyclomatic 17) Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs:550— MainWindow.UpdateDownloadsList has cyclomatic complexity 17 (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.
AddDownloadDialog.DiscoverUrlButton_OnClicked (cyclomatic 16) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:329— AddDownloadDialog.DiscoverUrlButton_OnClicked has cyclomatic complexity 16 (threshold 15). Of this number, 14 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.
MainWindowController.CheckForUpdatesAsync (cyclomatic 16) Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:123— MainWindowController.CheckForUpdatesAsync 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.
Prerelease dependency: CommunityToolkit.Labs.WinUI.Controls.TokenView — CommunityToolkit.Labs.WinUI.Controls.TokenView resolves to 0.1.251217-build.2433, a prerelease build. Prerelease packages carry no support policy, may change breaking between previews and can be unlisted — pin a stable release before shipping, or record the reason this preview is required.
Media.Media.ctor (cognitive 177) Nickvision.Parabolic.Shared/Models/Media.cs:38— Media.Media.ctor has cognitive complexity 177 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
YtdlpExecutableService.GetDownloadProcess (cognitive 132) REDACTED:125— YtdlpExecutableService.GetDownloadProcess has cognitive complexity 132 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
Download.Process_Exited (cognitive 65) Nickvision.Parabolic.Shared/Models/Download.cs:141— Download.Process_Exited has cognitive complexity 65 (threshold 15). To reduce it, flatten the nesting: invert conditions into early returns or guard clauses so the happy path stays at one level, and lift the deepest nested block into its own named function.
AddDownloadDialogController.DiscoverAsync (cognitive 47) Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:253— AddDownloadDialogController.DiscoverAsync has cognitive complexity 47 (threshold 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.
Download.Process_OutputDataReceived (cognitive 45) Nickvision.Parabolic.Shared/Models/Download.cs:233— Download.Process_OutputDataReceived has cognitive complexity 45 (threshold 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.
AddDownloadDialogController.AddPlaylistDownloadsAsync (cognitive 44) Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:69— AddDownloadDialogController.AddPlaylistDownloadsAsync has cognitive complexity 44 (threshold 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.
Format.ToString (cognitive 38) Nickvision.Parabolic.Shared/Models/Format.cs:224— Format.ToString has cognitive complexity 38 (threshold 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.
Format.Format.ctor (cognitive 34) Nickvision.Parabolic.Shared/Models/Format.cs:59— Format.Format.ctor has cognitive complexity 34 (threshold 15). 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.
KeyringDialog.ShowAsync (cognitive 33) Nickvision.Parabolic.WinUI/Views/KeyringDialog.xaml.cs:58— KeyringDialog.ShowAsync has cognitive complexity 33 (threshold 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.
AddDownloadDialog.DiscoverUrlButton_OnClicked (cognitive 31) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:329— AddDownloadDialog.DiscoverUrlButton_OnClicked has cognitive complexity 31 (threshold 15). Of this number, 24 points are the body's own statements and 7 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.
DiscoveryService.ParseBatchFileAsync (cognitive 29) Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:117— DiscoveryService.ParseBatchFileAsync has cognitive complexity 29 (threshold 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.
srt_fix.dedupe_yt_srt (cognitive 29) resources/yt-dlp-plugins/srt_fix/yt_dlp_plugins/postprocessor/srt_fix.py:136— srt_fix.dedupe_yt_srt has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 2, loops 1 (nesting depth added 14). 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.
DiscoveryService.GetForUrlAsync (cognitive 24) Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:64— DiscoveryService.GetForUrlAsync has cognitive complexity 24 (threshold 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.
DiscoveryResult.DiscoveryResult.ctor (cognitive 22) Nickvision.Parabolic.Shared/Models/DiscoveryResult.cs:36— DiscoveryResult.DiscoveryResult.ctor has cognitive complexity 22 (threshold 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.
MainWindowController.CheckForUpdatesAsync (cognitive 20) Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:123— MainWindowController.CheckForUpdatesAsync has cognitive complexity 20 (threshold 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.
Format.CompareTo (cognitive 18) Nickvision.Parabolic.Shared/Models/Format.cs:168— Format.CompareTo has cognitive complexity 18 (threshold 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.
AddDownloadDialog.DiscoverMediaAsync (cognitive 16) Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:204— AddDownloadDialog.DiscoverMediaAsync has cognitive complexity 16 (threshold 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.
TooManyMethods: MainWindow Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs— TooManyMethods — 359 significant lines (blank, comment-only and punctuation-only lines excluded), 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.
ClassTooLong: AddDownloadDialog Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 22 methods. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×1
Edited copy of a member (35 corresponding lines) Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:66— Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:66-101 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:215-249 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) Nickvision.Parabolic.WinUI/Helpers/SelectionItemListExtensions.cs:26— Nickvision.Parabolic.WinUI/Helpers/SelectionItemListExtensions.cs:26-65 | Nickvision.Parabolic.WinUI/Helpers/SelectionItemListExtensions.cs:76-115 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) Nickvision.Parabolic.Shared/Services/DownloadService.cs:73— Nickvision.Parabolic.Shared/Services/DownloadService.cs:73-100 | Nickvision.Parabolic.Shared/Services/DownloadService.cs:103-142 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (33 corresponding lines) · ×1
Edited copy of a member (33 corresponding lines) Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:116— Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:116-148 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:302-334 — These two members are one piece of code written twice and then edited apart: 33 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:80— Nickvision.Parabolic.GNOME/Views/HistoryDialog.cs:80-96 | Nickvision.Parabolic.GNOME/Views/KeyringDialog.cs:163-178 | Nickvision.Parabolic.GNOME/Views/PreferencesDialog.cs:356-371 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:363— Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:363-380 | Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs:394-412 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:538— Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:538-545 | Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs:576-583 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:245— Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:245-255 | Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:397-407 | Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:410-420 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) Nickvision.Parabolic.WinUI/Helpers/IServiceCollectionExtensions.cs:12— Nickvision.Parabolic.WinUI/Helpers/IServiceCollectionExtensions.cs:12-21 | Nickvision.Parabolic.GNOME/Helpers/IServiceCollectionExtensions.cs:12-20 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×1
Edited copy of a member (12 corresponding lines) Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:342— Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:342-353 | Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:303-315 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:231— Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:231-240 | Nickvision.Parabolic.WinUI/Controls/DownloadRow.xaml.cs:207-216 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:219— Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:219-237 | Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:282-300 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs:219` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) Nickvision.Parabolic.Shared/Services/DownloadService.cs:299— Nickvision.Parabolic.Shared/Services/DownloadService.cs:299-306 | Nickvision.Parabolic.Shared/Services/DownloadService.cs:309-316 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Low cohesion: AddDownloadDialog (LCOM4 7) Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs:24— AddDownloadDialog's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Outbound HTTP without resilience — The app makes outbound HTTP calls but no resilience handler was detected (Polly / AddStandardResilienceHandler / circuit-breaker). A slow or failing dependency will cascade — add timeouts, retries with back-off, and a circuit breaker.
Duplicated block (61 lines × 2 locations) extension/chrome/background.js:5— extension/chrome/background.js:5 · extension/firefox/background.js:2 — 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.
Test Coverage — 0% of 6 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
SC1 · Supply-chain hygiene· NuGet dependencies are not locked · ×1
NuGet dependencies are not locked — No packages.lock.json and no central package management — restores aren't reproducible or pinned (SSDF PW.4.4). Enable <RestorePackagesWithLockFile>true</RestorePackagesWithLockFile> (commit the lockfile) or adopt Directory.Packages.props. Advisory — never scored.
Sync-over-async (deadlock risk) Nickvision.Parabolic.GNOME/Views/MainWindow.cs:122— Blocking on a Task with `.Wait()`/`.GetAwaiter().GetResult()` can deadlock (and wastes a thread). Prefer awaiting it: make the caller `async` and `await` instead. Where a synchronous entry point must stay — a public sync API you cannot break, or a process entry point that must not return until the work finishes — the block belongs in ONE documented bridge and never inside code that is already async; and where it already is that bridge, give the wait a TIMEOUT so a hung task fails the call instead of hanging the process.
Swallowed exception (caught, then discarded) Nickvision.Parabolic.GNOME/Controls/DownloadRow.cs:97— `catch` does nothing with the exception it caught — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch. Log it through whatever this codebase already uses to report problems, or let it propagate; if one specific failure genuinely cannot matter, catch exactly that exception type and say why in a comment on the catch.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:168— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:243— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:260— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs:379— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:57— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:158— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:167— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:175— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:199— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:217— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:234— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:281— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:299— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:316— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:334— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:351— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:369— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs:386— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/ConfigurationMigrationService.cs:43— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/ConfigurationMigrationService.cs:45— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/ConfigurationMigrationService.cs:51— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/ConfigurationMigrationService.cs:53— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:66— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:70— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Interpolated log message defeats structured logging Nickvision.Parabolic.Shared/Services/DiscoveryService.cs:77— Logging an interpolated string (`$"..."`) collapses the event to plain text — you lose the named, queryable properties structured logging exists for. Use a message template with placeholders: `LogInformation("User {UserId} did {Action}", id, action)`. If these calls go through a logging wrapper that only accepts a pre-formatted string, give the wrapper a template+args overload that forwards to the underlying logger, then migrate call sites to it.
Duplicated predicate Nickvision.Parabolic.GNOME/Views/MainWindow.cs:385— `_controller.PauseDownload(id) && _downloadRows.TryGetValue(id, out var row)` appears character-identically in 2 files — Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs. 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 Nickvision.Parabolic.GNOME/Views/MainWindow.cs:393— `_controller.ResumeDownload(id) && _downloadRows.TryGetValue(id, out var row)` appears character-identically in 2 files — Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs. 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 Nickvision.Parabolic.GNOME/Views/MainWindow.cs:309— `e.Notification.Action == "error" && !string.IsNullOrEmpty(e.Notification.ActionParam)` appears character-identically in 2 files — Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs. 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 extension/chrome/options.js:8— `(result && result.trimPlaylist) || false` appears character-identically in 2 files — extension/chrome/options.js, extension/firefox/options.js. 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 extension/chrome/utils.js:8— `host === 'youtube.com' || host === 'www.youtube.com' || host === 'm.youtube.com' || host === 'music.youtube.com' || host === 'youtu.be' || h…` appears character-identically in 2 files — extension/chrome/utils.js, extension/firefox/utils.js. 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 Nickvision.Parabolic.GNOME/Views/MainWindow.cs:504— `row.Status == DownloadStatus.Running || row.Status == DownloadStatus.Paused` appears character-identically in 2 files — Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs. 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 Nickvision.Parabolic.GNOME/Views/MainWindow.cs:506— `row.Status == DownloadStatus.Success || row.Status == DownloadStatus.Error || row.Status == DownloadStatus.Stopped` appears character-identically in 2 files — Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs. 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.
redundant comment Nickvision.Parabolic.GNOME/Views/MainWindow.cs:136— 6 comments in this file only repeat the code they sit on (lines 136, 146, 161, 166, 171, 175), for example "Keyboard shortcuts action". Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment extension/chrome/utils.js:20— "Check if it's a YouTube URL" repeats the code it sits on: 3 of its 3 words (check, tube, url) are already in `if (isYouTubeHost(urlObj.hostname))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment extension/firefox/utils.js:20— "Check if it's a YouTube URL" repeats the code it sits on: 3 of its 3 words (check, tube, url) are already in `if (isYouTubeHost(urlObj.hostname))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×2
Diagnostic log message is built whether or not it is wanted Nickvision.Parabolic.Shared/Services/DownloadService.cs:75— `LogDebug` at line 75 is called with an argument built by `JsonSerializer.Serialize(options, ApplicationJsonContext.Default.DownloadOptions)` (line 75), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Diagnostic log message is built whether or not it is wanted Nickvision.Parabolic.Shared/Services/DownloadService.cs:110— `LogDebug` at line 110 is called with an argument built by `JsonSerializer.Serialize(option, ApplicationJsonContext.Default.DownloadOptions)` (line 110), whose cost grows with the collection it walks. C# evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because LogDebug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `IsEnabled` test, no debug flag, no conditional-compilation region.
Fat interface: IDownloadService (22 members) Nickvision.Parabolic.Shared/Services/IDownloadService.cs:9— `IDownloadService` declares 22 members: `DownloadAdded`, `DownloadCompleted`, `DownloadProgressChanged`, `DownloadRetired`, `DownloadStartedFromQueue`, `DownloadStopped`, `DownloadingCount`, `QueuedCount`, `CompletedCount`, `FailedCount`, `RemainingCount`, `AddAsync`, `AddAsync`, `ClearCompleted`, `ClearQueued`, `Pause`, `RecoverAllAsync`, `Resume`, `RetryAsync`, `RetryFailedAsync`, `StopAsync`, `StopAllAsync`. Counted as the author wrote them — a property is ONE member and its get/set accessors are not counted separately, and an event counts once. Those 22 declarations carry 21 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 21 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 31 significant file(s) lose their only recent owner: Nickvision.Parabolic.GNOME/Views/AddDownloadDialog.cs, Nickvision.Parabolic.WinUI/Views/AddDownloadDialog.xaml.cs, Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs, Nickvision.Parabolic.Shared/Controllers/AddDownloadDialogController.cs, Nickvision.Parabolic.WinUI/Views/SettingsPage.xaml.cs, Nickvision.Parabolic.GNOME/Views/MainWindow.cs, Nickvision.Parabolic.Shared/Controllers/MainWindowController.cs, Nickvision.Parabolic.Shared/Controllers/PreferencesViewController.cs (+23 more). Pair on, review, or document these before any departure.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
Logging is not universal — Only 2/3 service-like projects use logging (pure contract/DTO projects are excluded — they have nothing to log). Of those 3, 2 ship a process this repository operates; the rest are libraries their consumer hosts, where the logging decision belongs to the host.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add CodeQL's csharp pack, or a .NET security analyzer package (or `semgrep --config=auto`, which runs on any language) 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.
No dependency-update automation Nickvision.Parabolic.GNOME/Nickvision.Parabolic.GNOME.csproj:17— `Nickvision.Parabolic.GNOME/Nickvision.Parabolic.GNOME.csproj` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all async methods take a CancellationToken · ×1
Not all async methods take a CancellationToken — Only 6/59 async methods accept a CancellationToken, so in-flight work can't be stopped early when the caller gives up — whatever ends it in your host (shutdown signal, timeout, abandoned request, user cancel). Thread a token through the call chain and honour it at each await and loop; where a method genuinely cannot be interrupted, omitting it is a deliberate choice — judge against your hosting model.
Null-forgiving operator (`!`) suppressions override nullable warnings — ~7.8 `!` suppressions per 1k syntax nodes — 384 suppression(s) across the 49019 syntax node(s) in code where nullable warnings are ENABLED, which is the only code a `!` can suppress anything in (a `!` under `#nullable disable` is inert and is not counted, and its file's nodes are not in the denominator). Each one tells the compiler to trust you about null, suppressing the very safety NRTs provide. 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 Nickvision.Parabolic.Shared/Models/TimeFrame.cs:54— `Parse` swallows every exception into `return null;` — a data error becomes a silent behavior change with no trail. Log the failure or let validation throw.
Off the main sequence: Nickvision.Parabolic.Shared Nickvision.Parabolic.Shared/Nickvision.Parabolic.Shared.csproj:1— Nickvision.Parabolic.Shared: abstractness 0.16, instability 0.00, distance 0.84 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
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.
nuget: not applicable — nuget: the solution did not restore on the analyzer's .NET SDK (an SDK/target-framework/restore mismatch, common for an older codebase), so there was no restored dependency graph to scan
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 4 file(s) — `Nickvision.Parabolic.Shared/Helpers/IConfigurationServiceExtensions.cs`, `Nickvision.Parabolic.Shared/Helpers/MediaFileTypeExtensions.cs`, `Nickvision.Parabolic.Shared/Helpers/StringExtensions.cs`, `Nickvision.Parabolic.WinUI/Views/MainWindow.xaml.cs` — 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 01a1cd77-fa29-7dfb-90ae-e220fb4edd62 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 30 · Warnings: 191 · Recommendations: 65 · Info: 8 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 12-11-2026 @ 01:55 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.